AstraCode CLI
AstraCode, in your terminal.
Have a conversation with it, the way you would in the editor. Or hand it one task from a script or a CI job and let it exit. The same agent, the same model routing, on the same account.
curl -fsSL https://astracode.io/install | shmacOS and Linux, arm64 and x64. One binary, Node built in, nothing else to install.
- Homebrew:
brew install astracode-io/tap/astracode-agent - npm, with Node 20+:
npm install -g astracode-agent
╭─────────────────────────────────────╮ │ ▄▖ █ ▗▄ ✦ │ │ ▐▌▄▄▄▟█▙▄▄▄▐▌ │ │ ▟▘▝▜█████▛▘▝▙ │ │ ▐▌ ▟███▙ ▐▌ │ │ ▝▙▖▗▛▀ ▀▜▖▗▟▘ │ │ │ │ ✻ Welcome to AstraCode │ ╰─────────────────────────────────────╯ > fix the failing login test ⏺ Search(signin) ⏺ Read(accounts/tests.py) ⏺ Update(accounts/tests.py) ⏺ Bash(pytest accounts/tests.py -k login) ⎿ 3 passed in 0.41s ⏺ Fixed. The test posted to /signin/, which now redirects to /signin/method/. The login tests pass. ⏵⏵ auto mode on ✻ AstraOne · 23% context
- macOS and Linux, arm64 and x64
- The same agent as the editor
- Signs in through your browser
- Free to start, no card
Talk to it. Approve as it goes.
Run astracode-agent in a project and ask for what you want. Before it edits a file or runs a command it asks, and one key changes how much it asks.
- Shift-Tab cycles ask, auto and plan
- Esc stops it and keeps what it has done
- /rewind takes a turn back, edits included
One task in. An exit code you can trust out.
With -p it runs one task and exits, for a script or a pipeline. It is read-only until you say otherwise, and a run that did not finish exits 1 and fails the job.
- read-only, auto or full, decided up front
- Plain text, one JSON result, or a stream of events
- Every refused action listed, so a log says why
A review before you open the pull request.
astracode-agent review reads your branch against its base and reports only the problems it can show will break: the input, and the wrong result that follows.
- At most eight findings, most serious first
- Read-only, so it is safe to run anywhere
- JSON output for a script to act on
Your editor. Our agent.
astracode-agent acp speaks the Agent Client Protocol, so Zed and the JetBrains IDEs can run AstraCode as their agent, with their own diffs and approvals.
- A few lines of settings, then pick AstraCode
- Signs in the same way as the command line
- Risky commands are asked about every time
In the conversation
Every edit as a diff
Colours chosen for your terminal's background, including colour-blind friendly themes.
@ mentions a file
Point it at the file you mean instead of describing where to look.
! runs your shell
Run a command yourself and its output goes with your next message.
It knows your project
# remembers a note
Tell it something about the project once, and the next conversation starts knowing it.
/init writes AGENTS.md
A starting file of the project's conventions, for it and for every agent after it.
Your MCP servers
Servers in your own settings connect when it starts, and your commands and skills appear in the / menu.
Wherever it runs
--continue picks it up
Come back to this folder's last conversation, or choose an earlier one with --resume.
status for CI
Says who is signed in, and exits 1 when nobody is, so a job checks before it spends a step.
AstraOne picks the model
/model chooses balanced, most capable or lowest cost, and it routes each step from there.
Language-server lookups, live diagnostics and the code index need the editor, in every way of running the CLI. Get the editor
One line to install. Then ask it for something.
Free to start, no card. Signs in through your browser the first time.
curl -fsSL https://astracode.io/install | sh