Repository navigation
Upgrade Atomic to 0.10.3 - #977
Merged
Merged
Conversation
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
force-pushed
the
atomic-0.10.3
branch
from
November 21, 2026 12:35
0e000d3 to
bb050c2
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Moves Chopin to Atomic 0.10.3, the release after #973's 0.10.2.
What changes
package.jsonharnesscatalog andbun.lock:@bastani/atomicand@bastani/atomic-storage-postgresgo to 0.10.3. Only Atomic's own packages move in the lockfile.packages/protocol/agents.ts: the Atomic agent'simagepackages, which the NVX sandbox installs in the guest, go to@bastani/atomic@0.10.3.@bastani/atomic-acpstays 0.0.18, still its latest release.README.mdanddocs/chopin-cli.md(the agent tablesagents-docs.test.tschecks againstagents.ts),docs/nvx-sandbox.mdanddocs/self-hosting.mdname 0.10.3.Atomic 0.10.3 for Chopin
It lists no breaking change. What reaches Chopin:
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
NoticeLineandToolBlockmarks, ← in a subagent's chat, the queued-message display) touch nothing Chopin draws or reads. The SDK addsAgentSession.prompt({ startTurnOnly }), which Chopin doesn't use.Verification (head on
f6ed3a03)bun run fix(no changes),bun run ciandbun run typespass.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 buildpasses.@bastani/atomicand@bastani/atomic-storage-postgresimport fromapps/serverand report 0.10.3.apps/connectoron the previous base: 473 pass, 4 fail. All four (twoconnectCLI tests at their 5-second timeout, two sandbox tests) fail the same way on an unchangedmaincheckout 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.