Daily AI Zine
Thursday, August 6, 2026
Issue No. 022 · Tokyo · full edition

✦ Today's Big Thing

Agent access is becoming the real control layer

The useful shift today is not smarter agents. It is narrower permissions, mediated identity, and reviewable work units.

5 min read · 7 sections

In Brief
  1. Cloudflare’s Agent Access Model points to task-scoped agent identity rather than broad tool permission.
  2. Anthropic’s containment work reinforces the same pattern: cap the blast radius before adding autonomy.
  3. Runway is positioning Gen-4.5 around better motion quality, visual fidelity, and following the written brief.
  4. OpenAI Presence gives voice and chat agents a clearer enterprise packaging story.
  5. The practical build is an access manifest for one agent task, not another open-ended agent experiment.

Today's Big Thing

The one thing that matters

Test it

Agent access becomes the control layer

Cloudflare’s Agent Access Model is the clearest development today. It proposes task-scoped agents secured through identity brokering, continuous mediation, and stateful trust. In plain English: an agent should not just hold a permanent key. It should prove what job it is doing, get only the access needed for that job, and be checked while it acts. Anthropic’s containment work points in the same direction, framing the engineering problem as capping Claude’s potential blast radius across products. The practical takeaway is immediate. Any agent that touches files, repos, client material, payments, or production systems needs a job-specific access rule before it gets more autonomy. Verdict: test one narrow agent with mediated access before expanding the pattern.

My AI Ecosystem

Your actual stack

Test it

Claude model lanes need separate jobs

Anthropic’s current model positioning is now clearer: Opus 5 is framed for long-running agents, coding, and professional work, while Sonnet 5 is framed for coding, agents, and professional work at scale. Treat that as a routing problem, not a model loyalty question. Use the heavier lane for work that must persist, reason, and recover. Use the scale lane for repeatable throughput.

Test it

Hot signal: Runway aims at better video follow-through

Runway is presenting Gen-4.5 as a video model focused on motion quality, visual fidelity, and prompt adherence, meaning how closely the output follows the written brief. The reason to pay attention is not the ranking claim. It is whether tighter brief-following reduces the number of unusable takes in short concept films, pitch visuals, and client mood tests.

Watch it

Google’s agent course shows mainstream pull

Google says Kaggle’s AI Agents Intensive reached 353,000 learners in a no-cost course about building and deploying AI agents. The useful signal is demand, not curriculum detail. Agent literacy is moving from specialist circles into the general builder market, which means client teams will increasingly expect practical demos, not abstract AI strategy decks.

CoWork Corner

Claude CoWork, day to day

CoWork should inherit the containment mindset

Claude CoWork is the workspace Adrian uses for persistent projects, operational records, and AI-assisted workflows. No verified CoWork-only product change surfaced today, but Anthropic’s containment note is directly relevant to any Claude workspace connected to files, tools, or operating records. MCP, the protocol that lets Claude reach external tools, should stay boring here: each project lane gets only the connectors it needs, and any broader tool access gets moved to a separate test lane. The revisited workflow is simple: before starting a new persistent project, write one sentence that defines what Claude may touch, what it may summarize, and what it may never alter.

GPT Desk

OpenAI, ChatGPT, Codex

Test it

OpenAI Presence is a packaged agent lane

OpenAI introduced Presence as an enterprise AI agent platform for trusted voice and chat agents across customer and internal workflows. Adrian should care because Goodsense, SET, and Grey Group OS all have repeatable inquiry, briefing, and follow-up moments that can be turned into a narrow agent rather than a custom app. Do this today: draft one two-path Presence demo, inbound client question to qualified brief, and internal status question to project answer.

Small Money Systems

Small, repeatable, real

Test it

Small system: bilingual inquiry triage desk

System: build a bilingual voice and chat triage desk for new inquiries, missed replies, and basic qualification. Customer: small production companies, boutique agencies, or Japan-market service firms that lose time on first-response admin. Offer: a working intake flow, scripted questions, summary output, and handoff note. Price: JPY 49,000 setup plus JPY 19,000 per month. Existing assets: Grey Group OS, Goodsense proposal patterns, production planning language, and Japan-English workflow knowledge. AI workflow: OpenAI Presence handles the agent lane, with ChatGPT producing summaries and Codex helping wire forms or logs. First action: write the five intake questions in English and Japanese. Repeatability: the same script becomes a template for each client. Effort: half day. Expected value: recurring support revenue and fewer wasted qualification calls.

Test it

Small system: fast event recap proof pack

System: sell a same-week AI-assisted recap proof pack for small events and activations. Customer: sponsors, agencies, venues, and local brands that need a quick visual proof of what happened. Offer: a short written recap, selected stills, and a few AI-assisted concept clips for mood or future campaign framing. Price: JPY 35,000 per event, with a JPY 15,000 add-on for a bilingual sponsor version. Existing assets: Street Attack Japan formats, Grey Group production judgment, existing deck templates, and shoot-planning habits. AI workflow: Claude drafts the recap, Codex prepares the template, and Runway Gen-4.5 is tested for brief-following video concepts. First action: make one sample recap from an old event. Repeatability: each event reuses the same intake and output pack. Effort: half day. Expected value: small repeat revenue and stronger sponsor follow-up.

Build Next

Deployable now

Use it

Build a task-scoped agent access manifest

What to build: a small repo file that lists each agent task, allowed tools, allowed files, required approval points, and logging requirements. Why now: Cloudflare’s Agent Access Model pushes strict identity brokering and continuous mediation, while its Agent Development Lifecycle note says agents can now write code faster than teams can review, deploy, and maintain it. Effort: one hour. Expected impact: fewer unsafe agent runs and cleaner handoff before code or content changes. Dependencies: one active repo, one agent workflow, and a place where logs or review notes are already stored.

Try This Today

One action, right now

Pick one agent task you already run. Write three lines: what it may access, what it must ask before changing, and where it must leave evidence. Use that as the first row of the access manifest.