Terminal ticketing · Atlas Home · Built for AI agents
Ask your coding agent for a project update. Atlas keeps tickets, blockers, and review history in your repository, with a table in the terminal and Kanban in the browser.
Get started
Install Atlas once. Let your coding agent set up the project, then ask about the work in your own words.
curl -fsSL https://raw.githubusercontent.com/myrrazor/atlas-tasker/main/scripts/install.sh | sh
One small CLI. Needs curl, tar, and gh. Checksum plus a local attestation bundle; no GitHub login.
In the project you want tracked, ask your coding agent:
Initialize Atlas Tasker in this project.
That is tracker init: board, local checkpoints, and integrations for agents already on this machine. No picker. Restart the agent. Grok also needs you to trust this project before local skills appear.
What's the current status of this project?
Get current tickets, the work in progress, and anything that needs your attention. Your agent reads the same board you do.
The installer places the binary only. Run tracker init in each workspace, then restart detected coding agents so they load Atlas MCP. A written config is not a live connection. Open tracker to create a board or manage tickets in the browser.
Ask for status, add a high-priority task, and see it on the refreshed board. Grok reads eight tickets through Atlas MCP, creates APP-9, then confirms all nine. Download video · Read the transcript.
Same board, many agents
Assign each coding agent its own tickets. They read the same Markdown board, claim with leases, and hand work to a reviewer without a second tracker.
The actual product
Same tickets, same rules, same audit trail. Use whichever front end fits the moment and switch whenever you like.
--style kanban selects optional cards.
And a third surface for your AI agents. A stable JSON CLI and local stdio MCP server let agents inspect queues, work tickets, attach evidence, and hand off context.
Connect your agentOne tracked loop
APP-42
Define the work and its dependencies.
agent:builder-1
A lease keeps another agent from taking it.
run evidence
Attach test output, diffs, logs, and screenshots.
review required
Completion waits for the approvals you chose.
Built around the repository
Built for AI agents
Agents see exactly what is ready and why the rest is blocked, with stable reason codes instead of guesswork. Tracked writes record an actor, reasons are required for tracked MCP writes and protected operations, review gates guard completion, and the MCP server exposes typed tools behind escalating permission profiles.
Meet the agent surface
Lightweight by design
Tickets live under projects/ as plain files you can open in any editor. Changes land in an append-only event log, a small local index keeps queries instant and rebuilds itself from the files if it ever goes missing, and tracker doctor --repair rebuilds it whenever you want.
CLI + TUI + web board + MCP
Script with the CLI, work keyboard-first in the TUI, or open Atlas Home with tracker. Home is one loopback service on 127.0.0.1:7432. There is no hosted mode and no login system. One binary does all of it.
tracker board --project APPtracker tuitrackertracker mcp serve --global --tool-profile workflowInstall
The one-line installer is the normal path. It fetches the latest published release, checks its SHA-256 checksum, verifies the GitHub build attestation, and installs tracker. Workspace initialization is a separate, explicit step. After install, run tracker init in each workspace and restart those agents. See verification results on the GitHub release page.
Requires curl, tar, and GitHub CLI (gh) for attestation verification. gh does not need a GitHub login for the local bundle check. Unstamped source builds report version: "dev".
FAQ
Atlas Tasker is a local-first issue tracker and orchestration layer that lives in your code repository. Humans plan on the web board or in the terminal, and AI coding agents work the same tickets through the CLI and MCP, with dependencies, evidence, review gates, and audit history.
Nothing. Atlas Tasker is MIT licensed, with no hosted service, account, or paid tier required.
Tickets are Markdown files in your repository, and changes are recorded in an append-only local event log. A small disposable index keeps queries fast and can be rebuilt at any time. Atlas Tasker has no hosted mode, account system, or telemetry service.
The release installer supports macOS and Linux on arm64 and amd64. Building from source requires Go 1.26.6 or newer.
tracker init writes Atlas-managed MCP entries named atlas-tasker pointing at tracker mcp serve --global --tool-profile workflow. Restart the client. A written file is not a live connection. Agents can also drive the CLI with JSON output and stable exit codes. The For agents page covers global serve, pinned --workspace, and the six skill targets.
No. The installer only places the binary; it does not initialize a repo or register agents. After install, tracker init detects Claude Code, Codex, Cursor (including cursor-agent), OpenClaw, and Grok and writes Atlas-managed MCP entries plus the worker skill unless you pass --no-agents. Restart the client. Grok needs its own project-trust prompt before local skills appear. Atlas does not start those agents. Open the repo and ask for the board. There is no second Atlas install inside the client.
Open a GitHub issue for bugs, setup trouble, documentation problems, and feature requests. Security reports should follow the private reporting instructions in SECURITY.md.
Run tracker update --check, then tracker update --yes to verify checksums/attestations and replace the binary. Update replaces the binary only; re-run tracker init in each workspace to refresh managed skills. Use --version to pin a release, or re-run the curl installer.
Use Atlas Tasker when work should travel with a codebase and coding agents need a tool-native workflow. Jira is still a better fit when your organization needs a hosted, cross-team system with centralized administration.
Run tracker uninstall to preview Atlas-owned software, then tracker uninstall --yes to apply. Boards, history, backups, and registry pointers stay. Removing the binary by hand also leaves repository data in place.
Delete the Atlas Tasker files from your repository. If Git tracks them, they can remain in repository history until you rewrite that history. The marketing site has no account or hosted copy of your project data to delete.
Open source, no account
Atlas Tasker is free and MIT licensed. A star helps other terminal people find it. Issues and practical pull requests are welcome too.