Tools #AI agents Nov 17, 2026 · Originally published Nov 16

Amazon WorkSpaces adds agent governance: OIDC sign-in, on-behalf-of sign-in as the user, and session replay stored in your own S3

WorkSpaces applies the identity, policy and audit of cloud desktops to agents. How setup works, whose identity an agent acts under and what record it leaves, for teams that want agents operating existing systems such as ERP.

Primary source AWS What's New · aws.amazon.com Read the original ↗

// Key points

  • You can describe an agent's needs to a coding assistant such as Claude Code, Codex or Kiro, which builds the WorkSpace from adjustable defaults guided by AWS MCP skills; agents built on Bedrock AgentCore connect with AWS credentials and no agent code. New tools let an agent carry out a series of actions in one call and use the computer-use actions its model already knows.
  • Agents can now sign in through any OIDC identity provider in addition to SAML. With on-behalf-of sign-in, an agent works as the signed-in user, with that user's directory identity, permissions and Group Policies.
  • Session replay turns session screenshots into a video paired with a plain-language transcript of the agent's actions, stored in your own S3 bucket and encrypted with your own keys, for security review and audit evidence.

Builder's takeHaving an agent act as the user, within that user's existing permissions, and leave a replayable record is the minimum you need before security and compliance teams will sign off. Our own back-office automation should follow the same order: identity and replay first, more permissions later.

// Background · from #AI agents

Full timeline →
  1. Nov 17 Google models GKE costs for agent sessions: parking idle sandboxes with Agent Substrate saves 40% of the node bill for 100 coding agents at 2 prompts an hour
  2. Nov 17 Google Threat Intelligence: attackers now use autonomous LLM frameworks to scan software updates, work out the patched flaw and build an attack without human involvement
  3. Nov 16 Anthropic breaks down the architecture of always-on agents into five primitives: event inbox, timers, memory, permissions and outbox

Every Monday, the week in AI in one email

Every Monday morning: the 6 AI stories that mattered most in the past seven days, with my take, in your inbox.

Your email is only used to send the weekly and is never shared. Every email has a one-click unsubscribe link. See the latest issue →