From empty repo to agent-run board.

1 · Install

curl -fsSL https://raw.githubusercontent.com/myrrazor/atlas-tasker/main/scripts/install.sh | sh

The one-line installer is the normal path for the latest published release. It needs curl, tar, and GitHub CLI (gh). It fetches the latest published release, checks its SHA-256 checksum, verifies the GitHub build attestation with a local bundle (no GitHub login), and installs tracker. Workspace initialization is a separate, explicit step. An interactive terminal may offer tracker init for the displayed current directory; it defaults to No. Unattended installs never prompt or initialize. Optional Go install: go install github.com/myrrazor/atlas-tasker/cmd/tracker@latest. Details: getting started.

2 · Initialize, restart, ask

In the project you want tracked, ask your coding agent Initialize Atlas Tasker in this project. That is tracker init in the current directory. Detected agents are configured without a picker. Then tracker opens Home on 127.0.0.1:7432. Restart the coding agent so it loads Atlas MCP; a written config is pending_client_restart until the client connects. Grok also needs you to trust this project in its own UI. Then ask: What's the current status of this project? The Grok demonstration reads Atlas through MCP and shows the result in Grok’s terminal interface.

In a directory named app, init's default project key is APP. Extra projects are tracker project create AUTH "Auth".

tracker ticket create --project APP --title "Ship first feature" --type task --actor human:owner --reason "first ticket" creates the first ticket. Mutation commands resolve identity from --actor, TRACKER_ACTOR, or actor.default and fail before writing if none is set. Include a reason so agents and reviewers can understand why the change happened.

tracker ticket move APP-1 ready --actor human:owner --reason "groomed", then tracker board for a polished table, tracker tui for the full-screen one, or tracker for Atlas Home.

3 · Hand work to agents

tracker agent create builder-1 --name "Builder" --provider claude --capability go --actor human:owner --reason "register" registers an agent, and tracker ticket assign APP-2 agent:builder-1 --actor human:owner --reason "agent work" hands a ticket over. Or skip the assembly and apply a preset: tracker team apply pair --actor human:owner --reason "team setup". The full loop is in agents and dispatch.

tracker setup --plan remains as an advanced one-pass. --yes is not backup consent. Follow the Connect your agent journey or the detailed MCP setup guide. The installer places the binary; run tracker init in each workspace and restart detected agents.

4 · Optional Atlas backup

Your tickets already live in Git. Init starts local Atlas checkpoints. A remote is a second, isolated Git repository you name — not a silent copy of origin. A push is not verified until Atlas fetches the remote commit. Init and setup never install a machine scheduler. Uninstall with tracker uninstall; boards stay.

5 · Keep it honest

Statuses move backlog to ready to in progress to in review to done, with blocked as the exception lane. Review and completion run gates, evidence attaches to runs, and everything lands in an append-only event log in your repo. The mechanics are in tickets and workflow, and the storage story is told straight in the FAQ.