Skip to content
Agent Fleet

v0.34.1

ECS deployments can now turn on the /mcp endpoint and MCP sign-in (OAuth) that 0.34.0 shipped. 0.34.0’s template had no way to set them.

Improved

Section titled “Improved”
  • ECS: /mcp and MCP sign-in have stack parameters. McpEnabled, McpOAuth and McpOAuthTrustedHosts on the 30-ingress stack set the matching Control Plane variables. All three are off by default, so upgrading changes nothing until you set them. (#2595)
  • ECS: three more Control Plane settings are reachable from 30-ingress: SessionTtl, GithubAllowedEmails and KmsDataKeyCacheTtl. They are empty by default, which keeps today’s behaviour. (#2595)

Fixed

Section titled “Fixed”
  • Uncommenting AF_MCP_ENABLED=1 in the compose .env.example left /mcp off, because the Control Plane only accepts true. The example now shows true, next to the MCP sign-in settings. The native runtime and the local development script now pass the MCP sign-in variables through. (#2595)

Upgrade notes

Section titled “Upgrade notes”
  • ECS deployments: run update.sh as usual. If you skipped 0.34.0, also follow its upgrade notes: apply the 20-platform and 40-ec2-pool stacks. update.sh does both. To turn on /mcp with MCP sign-in, deploy 30-ingress once more with --parameter-overrides McpEnabled=on McpOAuth=on. Every other parameter keeps its value. The ECS README has the full command. Without McpEnabled=on, /mcp stays off, Personal Access Tokens included.

Agent CLI pins: Claude Code 2.1.309, Codex 0.163.0, Copilot 1.0.103, Antigravity 1.4.5, Cursor 2026.10.22-27dcf5f, Kiro 2.33.1, OpenCode 2.1.3 and Muse Code 1.4.12-R6909.1.