// sync

Show what actually ran

Publish the sessions, models, tokens, and cost behind your stack, straight from your own machine.

Your prompts, responses, code, and file paths never leave your machine. aistack publishes only statistics: counts, models, and the names of tools you use.

$npx @use-aistack/cli sync

Prints everything first. Nothing sends until you pick Publish.

what it reads+

aistack reads files your agents already wrote on this machine. That is all it reads. Claude Code, Codex, Grok Build, opencode and Pi write those files.

On the first run it opens your browser to link this machine. You name the machine and can revoke it any time.

what publishes+

· models and their token shares
· sessions, active days, cache hits
· cost at API prices (optional)
· the rolling 30-day window
· tool and skill names you have approved

Nothing sensitive is shown in public.

what never leaves your machine+

· prompts and responses
· your code
· file paths and repo names
· anything, when you cancel

Cancel sends nothing, and you keep the reading you just saw. The exact bytes you approved go on the wire.

publish on a schedule+

Auto-sync publishes your stack on a schedule, when a session starts on a machine you have linked.

The switch is on your own stack page, above the numbers it keeps current. It is the one place this is decided, so you can turn it off from any browser, and the machines stop publishing even when their triggers keep firing.

find your stack

manage linked machines