Track Claude Code 2.1.226

[a5c-ai]

Version

• Previous graph version: 2.1.212
• Latest upstream version: 2.1.226
• Release notes: https://github.com/anthropics/claude-code/releases/tag/v2.1.226
• Intervening researched release: https://github.com/anthropics/claude-code/releases/tag/v2.1.224

Actual changes researched

• 2.1.226 official notes list bug fixes and reliability improvements.
• The 2.1.224 release train added self-hosted environments via claude self-hosted-runner for Team/Enterprise plans.
• Added archive plugin source support for HTTPS zip plugins with optional SHA-256 pinning.
• Added cross-session messaging with SendMessage/ListAgents, plus crossSessionInbound and dialogExpiry settings.
• Added ANTHROPIC_BEDROCK_REGION_PREFIX for Bedrock cross-region inference profile selection.
• Added sandbox credential-masking settings for structured env extraction, JWT claim masking, and AWS SigV4 re-signing.
• Fixed long project path session-directory collisions and Remote Control/session resume edge cases.
• Removed the 200-subagent-per-session spawn cap while retaining concurrency/depth limits.

Likely affected system surfaces

• launchBehavior: add/track claude self-hosted-runner.
• plugin install model: add archive source with url and optional sha256.
• transport/session adapter: model cross-session SendMessage/ListAgents and inbound approval flow.
• provider config: expose ANTHROPIC_BEDROCK_REGION_PREFIX.
• sandbox adapter: model credential masking and denied-access details in Bash results.
• session filesystem: keep long project path collision coverage.

Install/migration

• Install remains npm install -g @anthropic-ai/claude-code.
• No package rename was published.

Assimilation checklist

• Update launchBehavior: add claude self-hosted-runner command metadata.
• Extend plugin source schema: archive zip URL + optional sha256.
• Add cross-session messaging settings and SendMessage/ListAgents capability metadata.
• Add ANTHROPIC_BEDROCK_REGION_PREFIX to provider config metadata/docs.
• Update sandbox credential masking and Bash denied-access result expectations.
• Add regression coverage for long project path session-directory isolation.

[a5c-ai]

Triage Summary

Claude Code upstream tracking in Atlas is stale at 2.1.212; #1690 should advance the graph to 2.1.226 while carefully separating 2.1.224 feature metadata from 2.1.226 patch-release provenance.

Critical Evaluation

The issue is valid and in scope as an Atlas graph/catalog enhancement, not a runtime bug. The reporter's analysis is broadly accurate, but implementation should avoid attributing all intervening 2.1.224 features directly to the 2.1.226 release notes. #1685 is already closed as a duplicate of this issue, so #1690 is the canonical 2.1.226 tracker.

Root Cause Analysis

Affected files and areas:

• packages/atlas/graph/agent-stack/agent-versions/upstream-current-2026-07-17.yaml currently records Claude Code 2.1.212 as the latest upstream AgentVersion.
• packages/atlas/graph/agent-stack/products/claude-code.yaml and packages/atlas/graph/agent-stack/versions/claude-code-1-x.yaml provide the existing Claude Code product/version model to extend.
• packages/atlas/graph/extensions/env-vars/claude-code-env-vars-bedrock.yaml lacks ANTHROPIC_BEDROCK_REGION_PREFIX.
• packages/atlas/graph/extensions/tool-descriptors/claude-code-extended-tools.yaml already contains SendMessage, but no ListAgents descriptor was found.
• Plugin archive source / sha256 pinning and sandbox credential-masking details may need graph representation or source-backed assimilation notes depending on existing schema support.

Evidence:

• rg "2\.1\.226|ANTHROPIC_BEDROCK_REGION_PREFIX|ListAgents" packages/atlas/graph finds no Claude Code 2.1.226 AgentVersion, Bedrock region-prefix env var, or ListAgents tool descriptor.
• rg "2\.1\.212" packages/atlas/graph/agent-stack/agent-versions points at the current Claude Code upstream record.
• No commits or closed PRs were found for Claude Code 2.1.226, 2.1.226, or 1690.

Affected Components

• Packages: @a5c-ai/atlas, catalog consumers in @a5c-ai/babysitter-sdk
• Components: atlas, agent-catalog
• Effort: effort:medium

Recommended Approach

1. Add/advance the Claude Code AgentVersion/evidence record for 2.1.226 using the existing upstream-current AgentVersion pattern.
2. Represent 2.1.226 as a patch/reliability release unless upstream notes provide more detail.
3. Assimilate intervening 2.1.224 surfaces only where the graph lacks them, or explicitly cross-reference Track Claude Code 2.1.224 #1662 for already-tracked 2.1.224 work.
4. Add missing metadata for ANTHROPIC_BEDROCK_REGION_PREFIX and ListAgents if supported by the existing graph schema.
5. For archive plugin sources, optional sha256, cross-session settings, and credential masking, prefer structured graph records when schema supports them; otherwise add source-backed assimilation notes and open a schema follow-up rather than inventing unsupported fields.
6. Validate with npm run test:atlas-catalog-contracts, npm run validate:edges, and npm run verify:metadata where practical.

Reproduction

This is not a runtime bug. To reproduce the catalog gap:

rg "2\.1\.226|ANTHROPIC_BEDROCK_REGION_PREFIX|ListAgents" packages/atlas/graph
rg "2\.1\.212" packages/atlas/graph/agent-stack/agent-versions

Related Issues/PRs

• Track Claude Code 2.1.226 #1685: closed as duplicate of Track Claude Code 2.1.226 #1690.
• Track Claude Code 2.1.224 #1662: existing Claude Code 2.1.224 tracker; use it to avoid duplicating or misattributing 2.1.224 feature work.
• Recent release-tracking history: e3b0a4ea8 Track upstream agent CLI versions (#1503) and 533e2c456 feat(atlas): batch graph update — track 20 agent/model version updates.

Priority

priority:medium

This affects graph freshness and downstream catalog consumers, but it is not a production outage. The work is moderately scoped across AgentVersion/evidence records, env vars, tool descriptors/plugin metadata, and catalog validation.

Risk Analysis

Risk level: risk:medium

• Release provenance drift between 2.1.224 feature changes and 2.1.226 patch notes.
  • Mitigation: model 2.1.226 separately and cite/link 2.1.224 surfaces separately or cross-reference Track Claude Code 2.1.224 #1662.
• Duplicate or conflicting AgentVersion records.
  • Mitigation: follow existing upstream-current patterns, use unique ids, and verify has_version / version_of edges.
• SDK/catalog projection gaps for new tool/env/plugin metadata.
  • Mitigation: add or update catalog contract tests for ListAgents, Bedrock region prefix, archive plugin URL/sha256, and credential masking semantics.
• Under-modeled credential masking / denied-access behavior.
  • Mitigation: use structured attributes only where schema supports them; otherwise add source-backed notes and track schema expansion separately.

[a5c-ai]

Triage Summary

Claude Code release metadata in Atlas is stale: the graph currently tracks Claude Code through 2.1.212, while upstream/npm are at 2.1.226.

Critical Evaluation

• Reporter's analysis is accurate, with one implementation nuance: preserve provenance boundaries between releases.
• v2.1.226 itself publishes only bug fixes and reliability improvements.
• v2.1.224 is the intervening release containing most substantive behavior changes listed here, so evidence/claims should not attribute those changes to 2.1.226.

Root Cause Analysis

Affected areas:

• packages/atlas/graph/agent-stack/agent-versions/ for the new exact/current Claude Code AgentVersion record.
• packages/atlas/graph/catalog-meta/evidence-sources/ for upstream release/npm evidence.
• packages/atlas/graph/catalog-meta/claims/ for version and assimilation claims.
• packages/atlas/src/catalog/catalog.test.ts or graph claim tests for focused regression coverage.

Evidence found:

• upstream-current-2026-07-17.yaml records Claude Code 2.1.212.
• rg "2\.1\.226" packages/atlas/graph packages/atlas/src/catalog finds no existing graph/catalog record.
• npm view @anthropic-ai/claude-code version --json reports 2.1.226.
• Upstream v2.1.226 release notes say bug fixes and reliability improvements.
• Upstream v2.1.224 release notes contain the self-hosted runner, archive plugin source, cross-session messaging, Bedrock region prefix, sandbox masking, long-path session isolation, Remote Control/session resume fixes, and subagent cap removal items.

Affected Components

• Packages: atlas
• Effort: effort:medium

Recommended Approach

Add an Atlas graph/catalog assimilation update from Claude Code 2.1.212 to 2.1.226:

• Add a new exact AgentVersion record for Claude Code 2.1.226 with release URL, npm package, install method, and summary.
• Add official release evidence for 2.1.226 and 2.1.224.
• Add claims that distinguish 2.1.226 patch/reliability notes from the substantive 2.1.224 behavior changes.
• Keep Track Claude Code 2.1.224 #1662 as related prior tracking for 2.1.224 work to avoid duplicate scope.
• Add/update focused catalog or graph claim tests for currentVersion, releaseNotesUrl, and the key assimilation notes.

Reproduction

rg "2\.1\.226" packages/atlas/graph packages/atlas/src/catalog
npm view @anthropic-ai/claude-code version --json

Related Issues/PRs

• Track Claude Code 2.1.224 #1662 tracks Claude Code 2.1.224 and is related because it covers the substantive intervening release changes.
• Track Claude Code 2.1.226 #1685 was an exact-title duplicate that has already been closed as a duplicate of this issue.

Priority: medium

This affects public catalog accuracy and downstream agent-version consumers, but it is not a production outage.

Risk Analysis

• Risk Level: risk:medium
• Misattributed provenance between v2.1.224 and v2.1.226
  • Mitigation: keep separate release evidence and claims; tests should check exact version URLs and notes.
• Conflicting scope with Track Claude Code 2.1.224 #1662
  • Mitigation: explicitly reference Track Claude Code 2.1.224 #1662 and keep this issue focused on the 2.1.226 graph advancement.
• Graph schema churn
  • Mitigation: prefer AgentVersion, EvidenceSource, and Claim records first; only add new schema/runtime fields when a current consumer needs them.

Ready for development.