Start

Home and workspaces

One command opens Atlas Home. Workspaces stay in your repositories; the machine registry only stores pointers.

Open Home

from anywhere
tracker

No arguments. Atlas starts or reuses one loopback service on 127.0.0.1:7432, opens Home in a terminal, and prints a URL or JSON otherwise. You do not need to be inside a repository. If another app owns that port, the command fails instead of hopping.

Home clears its one-time URL fragment before sending the claim to POST /session/claim, which establishes an HttpOnly cookie. The claim is absent from request URLs. tracker web serve still uses ?token=.

Routes

  • / Home
  • /attention, /search
  • /w/<id>, /w/<id>/projects/<key>, /w/<id>/activity, /w/<id>/backup
  • /settings, /settings/agents, /settings/workspaces

The browser never posts a raw filesystem path as the init target. Initialize board creates under Atlas boards (default) or an authorized discovery root. For an existing directory outside those roots, preview the exact path and purpose, then confirm; that mints a one-time grant and does not initialize until you confirm. CLI grants remain: tracker workspaces grant /absolute/path/to/project --purpose init --json. Register and repair use their matching purposes; grants expire and work once. Home init does not write client MCP files.

On the project Kanban you can create, edit, assign, claim, review, cancel, and delete tickets. Delete ticket uses tracker ticket delete (ticket archive is an alias). There is no restore. Show archived work with ?archived=1. Errors keep typed values; stale edits conflict.

Workspaces

One repository root, one stable workspace_id. Canonical tickets stay in that tree. The machine registry stores pointers only. Health includes available, unavailable, moved, copied_identity_conflict, and related states. Unavailable workspaces keep a stale summary and do not block the others. Atlas-managed agent entries are named atlas-tasker and use mcp serve --global --tool-profile workflow; restart the client after init. A written file is not a live connection.

machine + workspace checks
tracker doctor --json
tracker doctor --repair

Outside a workspace, doctor reports current_workspace: none and does not create .tracker. Repair can update a moved path, fork a copied tree, hide a pointer, or remove a pointer without deleting board files. Details: the source guide.