Skip to main content
Atomic is built on six TypeScript libraries. Each one is published on npm at Atomic’s version with every release, and each works on its own outside Atomic.

Install

Install a library on its own with npm:
Inside an Atomic extension, import the libraries without installing them: the running Atomic provides them, so your extension shares its instances. If you publish an Atomic package that imports them, list them in peerDependencies with a "*" range. To build on Atomic’s sessions, tools and extensions rather than the bare libraries, use the SDK instead. For custom extension UI, start with TUI components.

Older package names

These libraries began as forks of pi’s packages. Extensions written for pi keep working in Atomic: imports of @earendil-works/pi-ai, @earendil-works/pi-tui, @earendil-works/pi-agent-core, @earendil-works/pi-codemode, @earendil-works/pi-schema, @earendil-works/pi-telemetry, their @mariozechner/pi-* equivalents, and @bastani/pi-ai, including their subpaths, resolve to the matching @bastani/atomic-* package. Use the @bastani/atomic-* names in new code. The old names only resolve inside Atomic; outside it, install the @bastani/atomic-* packages.