Skip to content

Upgrade Atomic to 0.10.3 - #977

Merged
lavaman131 merged 1 commit into
mainfrom
atomic-0.10.3
Nov 21, 2026
Merged

lavaman131 merged 1 commit into
mainfrom
atomic-0.10.3

Conversation

@lavaman131

Copy link
Copy Markdown
Collaborator

Moves Chopin to Atomic 0.10.3, the release after #973's 0.10.2.

What changes

  • package.json harness catalog and bun.lock: @bastani/atomic and @bastani/atomic-storage-postgres go to 0.10.3. Only Atomic's own packages move in the lockfile.
  • packages/protocol/agents.ts: the Atomic agent's image packages, which the NVX sandbox installs in the guest, go to @bastani/atomic@0.10.3. @bastani/atomic-acp stays 0.0.18, still its latest release.
  • README.md and docs/chopin-cli.md (the agent tables agents-docs.test.ts checks against agents.ts), docs/nvx-sandbox.md and docs/self-hosting.md name 0.10.3.

Atomic 0.10.3 for Chopin

It lists no breaking change. What reaches Chopin:

  • A turn that adds 20 or more content blocks, such as many parallel tool calls, no longer misses Claude's prompt cache on its next request. A resume near the context window compacts once instead of lowering the thinking budget and losing the cache.
  • A model request or PostgreSQL connection refused for its TLS certificate fails at once, naming the reason and NODE_EXTRA_CA_CERTS, instead of retrying as a network error.
  • session.dispose() waits for the notice lines it is still saving.

Its interface changes (the NoticeLine and ToolBlock marks, ← in a subagent's chat, the queued-message display) touch nothing Chopin draws or reads. The SDK adds AgentSession.prompt({ startTurnOnly }), which Chopin doesn't use.

Verification (head on f6ed3a03)

  • bun run fix (no changes), bun run ci and bun run types pass.
  • GIT_CONFIG_GLOBAL=/dev/null bun test apps/web/src/experiments packages/protocol apps/server/src/harness apps/server/src/agent apps/server/src/conversation-plan: 2166 pass, 3 skip, 0 fail.
  • bun run build passes. @bastani/atomic and @bastani/atomic-storage-postgres import from apps/server and report 0.10.3.
  • apps/connector on the previous base: 473 pass, 4 fail. All four (two connect CLI tests at their 5-second timeout, two sandbox tests) fail the same way on an unchanged main checkout on the same machine, which failed 19 connector tests in the same run, so they come from that machine's sandbox and load, not this change. CI runs them on a clean runner.
  • The Docker image build is in CI below.

HARNESS=atomic now runs Atomic 0.10.3, and the PostgreSQL session store
adapter moves with it (the `harness` catalog in package.json and
bun.lock). The Atomic agent's guest image installs 0.10.3 too (its
`image` packages in packages/protocol/agents.ts, which the NVX sandbox
installs), with `@bastani/atomic-acp` still 0.0.18, its latest; the
agent tables in README.md and docs/chopin-cli.md and docs/nvx-sandbox.md
name the new pin.

For Chopin this release brings:

- A turn that adds 20 or more content blocks, such as many parallel
  tool calls, no longer misses Claude's prompt cache on its next request,
  and a resume near the context window compacts once instead of
  lowering the thinking budget and losing the cache.
- A model request or PostgreSQL connection refused for its TLS
  certificate fails at once, naming the reason and NODE_EXTRA_CA_CERTS,
  instead of retrying as a network error.
- `session.dispose()` waits for the notice lines it is still saving.

It lists no breaking change. Its changed `NoticeLine` and `ToolBlock`
marks, the subagent chat's ← key and the queued-message display are
interface details nothing in Chopin draws or reads. The SDK adds
`AgentSession.prompt({ startTurnOnly })`, which Chopin doesn't use yet.

Co-authored-by: Alex Lavaee <lavaman131@github.com>
@lavaman131
lavaman131 merged commit 6f7a699 into main Nov 21, 2026
26 checks passed
@lavaman131
lavaman131 deleted the atomic-0.10.3 branch November 21, 2026 12:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant