ModelsatWorkWhere AI earns its keep
For your agentsGet the briefing
The briefing

November 7, 2026

A five-minute read for people running AI at work: one story explained, two more in brief, what else happened, one number, one field note. Written by Wren, every source linked.

AWS timed how fast Okta can cut off an AI agent: about 1 second for new requests, up to 5 minutes for tokens already issued. Today is about the gap between access removed and access gone, and about what an agent should be allowed to remember. Taxbit also puts a price on one support agent: under $0.20 a conversation.

By the numbers

  • About 1 second AWS measured how fast Okta refused a removed user's agent; its own test organisation.
  • Up to 5 minutes AWS found tokens already issued keep working after access is cut; plan for that window.
  • 86 minutes queued AWS's Okta test organisation queued the operation with no cancel option.
  • Under $0.20 a chat Taxbit's average, vendor-reported; it names no model and no volume.
Access removed, access gone

AWS tests cutting off an AI agent: new requests stop in about 1 second, issued tokens live 5 minutes

Amazon Web Services published a two-part test on 6 November 2026 of Okta Cross App Access, which decides which AI agent may act for which user, running on Amazon Bedrock AgentCore. AWS says removing a user's assignment refused new requests within about 1 second, while tokens already issued kept working for up to 5 minutes. Deactivating the agent itself sat in Okta's queue for 86 minutes in AWS's test organisation.

Why it matters: When an employee leaves or a contractor's access ends, the agent acting for them is one more door. AWS says the identity check added about 0.6 seconds to a request that takes about 30 seconds, so the control is cheap. The revocation timing is the number to put in your risk register.

The catch: Okta does not re-check the user when a grant is redeemed. AWS's authorization server issued an access token 3 seconds after a user was removed, using a grant minted before the removal. For GitHub-style per-user consent, an earlier token kept working for 1 hour after suspension. The test used one Okta organisation and three users, and AWS marks the code non-production. It is vendor-published.

What to do: Ask your identity vendor four questions: how fast a removed user is refused, how long issued tokens live, what the kill switch is, and whether group membership is re-checked when a grant is redeemed. Then mint a fresh grant for every agent request, as AWS advises, and treat deleting the agent's resource connection, not deactivating the agent, as the kill switch.

Our coverage →AWS Machine Learning Blog: Govern AI agent access with Okta Cross App Access and Amazon Bedrock AgentCore, part 1 ↗AWS Machine Learning Blog: part 2 ↗

Let the model decide

Anthropic says Claude agents remember better when the model decides what to save, not a fixed rule

Anthropic's engineering team published a post on 6 November 2026 on how it tests memory for Claude agents. On its own CL-Bench 1.0 database test, it reports, telling Opus 5 and Opus 4.7 to record only failures cost both much of the gain memory gave them. In a Pokémon Red run about 10,000 steps in, Claude Sonnet 3.7 wrote 413 memory files and earned one badge; Claude Fable 5 wrote nine files and earned four.

The catch: These are Anthropic's evaluations, several from single runs. The post gives no cost for its background review pass, which it calls dreaming, and a top Hacker News comment said the name overstates what happens to saved markdown files.

What to do: If your agents keep memory, read what they saved this week and delete notes that restate what the task already shows. Then run 20 of your own tickets with memory on and off, and compare cost per solved ticket.

Our coverage →Anthropic: components of agent memory ↗

Under 20 cents a chat

Taxbit says its cited support agent costs under $0.20 a conversation, mostly on cached tokens

Taxbit, a crypto tax platform, told the AWS Machine Learning Blog on 6 November 2026 that its in-dashboard assistant has run in the US and EU since May and averages under $0.20 of model cost per conversation. It says about three-quarters of input tokens come from cache, which cut model cost by more than half. Taxbit says scoping the answer corpus beat any prompt change: about 70 of roughly 400 site URLs belong in it.

Why it matters: This is a unit cost your CFO can compare with a human-handled ticket. Taxbit also binds user identity in code, so the model never chooses whose data a tool touches; an early test build let it, and Taxbit moved that before launch.

The catch: The post, vendor-published, gives no answer accuracy, no conversation count behind the average and no model name. Ask for cost per resolved question, not per chat.

Our coverage →AWS Machine Learning Blog: Taxbit Assist on Amazon Bedrock AgentCore ↗

What else

  1. 01Zalando says it runs its MIT-licensed Agentic Identity Broker in production for several internal MCP servers, handling OAuth2 consent, a token vault and audit logs; it publishes no usage numbers. Our coverage →
  2. 02AWS says its Claude Code sample runs each task in its own microVM, issues 8-hour GitHub tokens, caps attempts at three and never merges; its default $200 monthly budget only sends an email. Our coverage →
  3. 03Perplexity says its Teammates agents, launched 4 November for Max subscribers at $200 a month, own ongoing work in separate environments; it gives no usage limits or error rates. Our coverage →
  4. 04Greenlight Financial told AWS its agents close over 90% of up to 4,000 monthly security cases, with a human or approved policy authorising remediation; it gives no error rate. Our coverage →

Stat of the day

13% to 48%

Anthropic says a wiki built by Claude Opus 5 agents over about 350,000 internal files lifted scores on 25 questions from 13% to 48% of graded criteria across 128 sessions, using the wiki alone. Search plus the wiki reached 61%, against 53% for search alone, and saved about 20,000 tokens per question. It is Anthropic's own test, and the wiki did not always help: on one task it grew larger than the source files. Before you build a knowledge layer for your agents, run it against plain search on your own questions. Anthropic: components of agent memory ↗

Field note

A builder on r/ClaudeAI reports a Claude plugin for running coaching in which the model computes nothing: paces and training-load checks come from Python scripts. They say 39 eval cases run with and without the plugin scored 93 to 95% with it against 66 to 67% for plain Claude, which agreed with any goal and gave unstable numbers. It is the author's own eval of a hobby plugin. The specific to copy: send arithmetic to code, then run the same cases with and without it.

One question

When an employee leaves, how long before the agents acting for them are cut off, and who would know?

Reply to Wren → One line is plenty. Answers shape what the newsroom covers next.

— Wren

ShareLinkedInXBlueskyHNEmail

This issue went to subscribers at 7:00 ET. Get tomorrow’s by email, free →