Amistio guides
Browse the product manual, project-brain explainers, AI workflow articles, local runner setup, MCP/tooling notes, and troubleshooting references from one place.
Library shape
Start here
Pick the path that matches why you came.
The docs hub now behaves like a library: choose a setup path, a concept guide, or the open-source template path first.
Featured
The highest-signal guides first.
These are the pages most likely to answer what Amistio is, how the brain works, and how AI tooling fits the local-runner boundary.
Collections
Docs, articles, and references by intent.
The page is no longer one long manual. It is organized around what a visitor is trying to understand or do.
Project brain
How Amistio remembers work
Deep dives for the files that make agent work inspectable: memory, ADRs, plans, prompts, workflows, context, and instructions.
Learning
Blog-style guides and explainers
Readable background pieces for visitors learning the vocabulary around agents, harnesses, templates, and AI history.
Tools
MCP, local tools, and sessions
Practical guidance for the tool layer around Amistio's local runner and project-brain workflow.
Operations
Setup, runner, and support
Reference material for pairing, sync, CLI commands, runner execution, status, and troubleshooting.
Setup reference
From app project to paired local runner.
The setup content stays on this page, but it is compact now so the hub can support both docs and learning articles.
Pairing and sync
Link non-secret hosted repository metadata in the app, then pair or import from a local checkout. Approved brain records sync into `docs/` folders; local changes can be pushed back for review, and concurrent edits create visible conflicts.
CLI reference
Commands you need after choosing a path.
Keep this section nearby for setup, runner work, bounded retries, and local-tool execution limits.
npm install -g @amistio/cliInstall the stable Amistio CLI runner.
amistio --helpConfirm the runner command is available.
amistio toolsCheck supported local AI tools detected on this machine.
amistio initCreate control-plane folders for a new project.
amistio onboardInspect or prepare an existing repository for Amistio.
amistio bootstrap --repo-url <cloneUrl> --target <path> --account <accountId> --project <projectId> --repository-link <repositoryLinkId> --pairing-code <code>Clone, prepare, and pair a linked repository locally.
amistio import <code>Pair an existing checkout and import accepted legacy Markdown/MDX docs.
amistio pair --account <accountId> --project <projectId> --pairing-code <code>Pair a local checkout with a web project.
amistio sync statusShow brain file state, pending docs, dirty edits, and conflicts.
amistio sync pullMaterialize approved web brain artifacts into docs/ folders.
amistio sync pushPush local synced brain changes back to the app for review.
amistio run --watchClaim queued brain-generation and approved implementation work.
amistio run --watch --max-preflight-attempts 3 --tool-timeout-seconds 1800Use explicit bounded setup retry and local-tool timeout limits.
amistio run --watch --backgroundStart a detached background runner for the paired checkout.
amistio runner statusCheck detached runner state, heartbeat, and bounded resource sample.
amistio runner stopStop the detached background runner.
amistio runner service installInstall a user-level startup service where available.
amistio runner service statusShow startup service state and descriptor location.
amistio runner service removeUnload and remove the user-level startup service.
Local runner
Execution stays on your machine.
The web app coordinates wishes, generated brain artifacts, approvals, queues, heartbeats, status, and bounded runner resource samples.
Brain generation and approved implementation work run through the local `amistio` CLI runner from a paired repository with a local machine credential and a usable local AI tool. Runner lifecycle actions such as update, restart, and remove are limited to the paired runner owner or an organization admin. Git worktree preflight retries, local-tool timeouts, lease renewal, and status milestones are recorded as safe summaries. Source code, secrets, process lists, environment variables, command lines, credentials, and arbitrary local paths are not uploaded as public status data.
Troubleshooting
When the path gets stuck.
Use these checks when setup, pairing, local tools, sync, or runner claiming does not behave as expected.
Open the status page from the same origin and confirm the web app, server routes, and local port checks are healthy.
Create a pairing code, then run `amistio import <code>` from an existing checkout, or use bootstrap for first-time clone setup.
Confirm local Git can clone the repository with your SSH key, credential helper, provider CLI, or keychain.
Install and authenticate one supported tool, then run `amistio tools` or refresh the runner panel.
Confirm the repository link is active, the work item is approved, and `amistio run --watch` is running from the paired repository.
The runner retries preflight setup up to `--max-preflight-attempts`, then fails the work item with the last safe error summary.
Resolve the conflict intentionally before syncing over either the web record or the repo copy.