Changelog

​

Model catalogs and provider authentication

• Dynamic provider catalogs stay current. The model picker renders its cached snapshot immediately and reports concise success, partial-failure, or timeout status. Run atomic update --models to force-refresh authenticated dynamic provider catalogs.
• Complete authentication reaches provider requests. API keys, provider headers, and credential-specific enterprise endpoints are preserved across normal chat and SDK requests.
• Interaction reliability improved. Adjacent thinking blocks render as one section, Windows startup restores Atomic’s terminal title after package checks, standalone Bun binaries include every interactive OAuth adapter, and early clone/fork attempts explain that the first assistant response must save the session.

​

Pi 0.80.6 compatibility

• Synced through upstream Pi 0.80.6. Atomic and its bundled extensions now use the 0.80.6 Pi runtime packages, including signed empty Anthropic thinking preservation, request-wide GPT-5.4/5.5 long-context pricing, and corrected GPT-5.6 catalog/backend metadata.
• Model controls are current. Atomic accepts max wherever the active model advertises it, applies models.json overrides to matching extension-registered models and built-ins, and loads legacy .pi plus primary .atomic layers during normal CLI startup. Disjoint override IDs survive, exact primary entries replace complete legacy entries, and removed catalog IDs fall back instead of being synthesized on resume. See Models.
• Custom pricing tiers are preserved. Custom models.json entries and extension providers can declare complete request-wide cost.tiers; matching modelOverrides can update scalar rates without losing inherited tiers or replace/clear the tier array explicitly. See Models and Custom Providers.
• Safer session and tool behavior. Invalid explicit bash timeouts fail instead of being clamped; missing exact session IDs warn before creation; lax null or omitted message content is normalized; auth writes surface persistence failures; Windows context traversal terminates at drive roots; and duplicate fork selections are ignored. See Tools and Usage.
• More reliable streaming and binaries. Visible custom messages stay before the live assistant row, standalone Linux clipboard reads can fall back to xclip with correctly packaged native bindings, caller-relative TMPDIR paths work from external directories, and --skip-deps tolerates a missing optional clipboard wrapper.

​

Dependency refresh

• Synced with upstream Pi 0.80.5. Atomic’s coding-agent package and bundled extensions now depend on @earendil-works/pi-ai, @earendil-works/pi-agent-core, and @earendil-works/pi-tui through ^0.80.5.
• Refreshed runtime dependencies. The consolidated dependency update also moves lru-cache to 11.5.2, optional @dbos-inc/dbos-sdk to 4.23.6, and native Cargo dependencies napi, napi-derive, and tree-sitter to their latest stable releases.

​

Upstream Pi sync

• Synced with upstream Pi 0.80.2. Atomic’s coding-agent fork and bundled extensions are now aligned with upstream Pi through ^0.80.2 for @earendil-works/pi-ai, @earendil-works/pi-agent-core, and @earendil-works/pi-tui. The 0.80.x line is dominated by upstream’s “Models runtime migration,” which made the @earendil-works/pi-ai root entrypoint core-only and moved the legacy global provider/model API (stream, complete, registerApiProvider, getEnvApiKey, …) onto a temporary @earendil-works/pi-ai/compat entrypoint.
• Extensions keep working unchanged. Atomic’s extension loader now aliases the @earendil-works/pi-ai root specifiers to the /compat entrypoint at runtime, so first-party bundled extensions and user-installed extensions that import from the root continue to resolve transparently — no extension code changes required.
• Atomic-first compatibility migration. Atomic’s own runtime, tools, tests, and extension examples were retargeted to the /compat entrypoint so they resolve the legacy provider/model API at both type-check and runtime, preserving the public extension and SDK surface Atomic’s downstream users depend on.
• Toolchain and native dependency refresh. Bundled @napi-rs/cli, @j178/prek, actions/checkout, and transitive Cargo crates (rustls, napi, bytes, webpki-roots) were refreshed to current releases, including the latest Mozilla-aligned webpki trust store.

​

Fixes

• Inherits upstream 0.80.0–0.80.2 fixes from the external Pi packages (pi-ai, pi-agent-core, pi-tui) that Atomic consumes as dependency bumps. This includes provider-side handling of malformed all-zero usage in OpenAI Responses context/compaction estimates, request-scoped apiKey/env participation in provider auth resolution, the restored pi-ai/compat legacy per-API stream aliases and detectCompat fallback, the ApiKeyCredential auth.json-compatible discriminator, and the renamed ShellExecOptions agent-core type.
• Note that coding-agent forked-source fixes (for example session-name newline normalization and threaded session-tree ordering) are NOT inherited automatically; they require intentional source porting and are tracked separately. Atomic retains its existing compaction guard for all-zero usage, which already aligns with the upstream fix.

​

Stable release

• 0.8.14 is the stable promotion of the 0.8.14 prerelease. It keeps the upstream Pi sync, bundled workflow documentation refresh, and bundled subagent guidance updates from the prerelease.
• Synced with upstream Pi patches. Atomic’s coding-agent fork is now aligned with upstream Pi patches since v0.75.4 and bundles Pi libraries at 0.75.5.
• Bundled workflow docs are current. The docs now describe Ralph’s final PR-preparation phase, deep-research report artifacts, and newer workflow inspection/control actions such as stages, stage, transcript, send, pause, and reload. See Workflows.
• Bundled subagent guidance is easier to find. Atomic now documents how to use bundled subagents for delegation, background work, nested fanout boundaries, model fallbacks, and custom agent guardrails. See Subagents.

​

Fixes

• Managed extension installs, git package ref reconciliation, async file tools, export HTML escaping, OpenCode session headers, OAuth device-code login, footer path abbreviation, clipboard native loading, and collapsed read output rendering received upstream fixes.
• The built-in header model label now refreshes when you change models, matching the footer below the chat box.

​

Stable release

• 0.8.13 is the stable promotion of the 0.8.13 prerelease. It keeps the workflow discovery and async subagent widget fixes from the prerelease while updating Atomic agent guidance.

​

Fixes

• Packaged workflow discovery loads reliably. Package-authored workflow resources load through jiti, so SDK imports such as @bastani/workflows resolve consistently from the Bun-packaged binary. See Workflows.
• Workflow diagnostics are preserved. Invalid default exports and supported SDK import diagnostics remain visible when workflows are discovered from packaged resources.
• Async subagent widget spacing is stable. Background subagent widgets preserve spacing before the prompt box. See Subagents.

​

New features

• Configurable HTTP idle timeout. Tune how long Atomic keeps idle HTTP connections open, with presets from 30 seconds through 30 minutes and an option to disable the timeout. See Settings.
• Workflow documentation and navigation. Atomic added the Workflows docs page so users can discover built-in workflows, authoring patterns, package setup, and run control from the docs site. See Workflows.

​

Updates

• Model reasoning level in the system prompt. Atomic now includes the active model’s reasoning level in generated system prompts and project context markup. See Models.
• Runtime and extension compatibility. Internal runtime, tool, TUI, tests, and extension example imports moved to explicit .ts specifiers for better raw-TypeScript extension compatibility.
• Atomic docs refresh. Package usage, customization, workflows, and release guidance were refreshed for Atomic branding.

​

Fixes

• Better Windows self-update behavior. Package-manager installs now handle native dependency cleanup, quarantine cases, and unavailable updates more clearly. See Windows.
• Smoother subagent rendering. Live subagent result rendering, async render updates, transient child-error recovery, and live widget animations are more stable. See Subagents.
• Workflow stages settle cleanly. Completed stages detach from run-control tracking, and the empty workflow graph waiting state is centered. See Workflows.
• Consistent duration display. Elapsed times across bash, subagent, and workflow output are shown as whole seconds and never go negative.