Skip to main content

Abacus AI CLI Installation

The Abacus AI CLI brings the full power of the AI coding agent directly into your favorite terminal.

Installation​

Run one of these in your terminal:

curl -fsSL https://static.abacus.ai/cli/install.sh | bash

Works on macOS (Intel & Apple Silicon), Linux (Ubuntu, Debian, Fedora, Arch, etc.), and WSL.

tip

After installation, restart your terminal to ensure the abacusai command is available on your PATH.

Getting Started​

In your terminal, launch the Abacus AI CLI:

abacusai

At the abacusai prompt, log in on first use:

/login [email]
tip

Run abacusai --help in your terminal to see the command-line options. Inside the CLI, use /help.

Setting Your API Key​

You can also authenticate by setting your API key as an environment variable. Run this in your terminal, before you start the CLI:

export ABACUS_API_KEY=YOUR_API_KEY_HERE

With ABACUS_API_KEY set, you are signed in without running /login. Other environment variables are listed under Settings.

Coming from Claude Code​

If you already use Claude Code on this machine, run /import in a session and the CLI brings your setup across:

WhatBecomes
CLAUDE.md in the folder you run from and the folders below itAGENTS.md beside each. Where an AGENTS.md with other text is already there, it is skipped for you to merge by hand.
.claude/CLAUDE.md and ~/.claude/CLAUDE.mdAn @ reference to it, in AGENTS.md for the project's and in ~/.abacusai/AGENTS.md for yours, so the original stays where it is
CLAUDE.local.mdAGENTS.local.md
Rules in .claude/rules and ~/.claude/rules@ references to them, in AGENTS.md for the project's and in ~/.abacusai/AGENTS.md for yours. A rule limited to some paths with paths:, or whose path has a space, is skipped and reported.
MCP serversYour MCP configuration
Permission rulesYour allow, ask and deny lists
Default permission modeYour permissionMode
HooksYour hooks
Skills and commandsYour skills
Enabled pluginsCopied whole into .abacusai/plugins/, or ~/.abacusai/plugins/ for one enabled for every project. Their skills, commands, hooks and MCP servers load from there, and their skills and commands are named after the plugin, such as /<plugin>:<skill>. A project plugin's hooks and MCP servers wait until you trust the folder. Subagents, LSP servers and output styles in a plugin are reported and not used.
MemoryYour memory

Run /import --dry-run first to see what it would do without writing anything. In VS Code, Import from other agents under Agent & permissions in Abacus Settings runs the same import.

Two machine-level fixes are worth running once on a new install: /setup configures your terminal and editor, and /doctor diagnoses an install that is misbehaving. Both are covered under built-in skills.

Shell commands on Windows​

The CLI runs shell commands through a bundled POSIX shell, so the agent can write ordinary sh scripts on Windows without WSL or a container. Native Windows programs still run normally, and your PATH is never reordered.

If you have Git for Windows installed, the CLI also picks up its GNU tools, so real Bash scripts and sed, grep -P, awk, date, diff and patch behave as they do on macOS and Linux. Installing it is the single best thing you can do for the agent's success rate on Windows. Run /doctor shell to check whether the CLI found Git's tools.

To use a Windows shell instead, set CODELLM_SHELL to powershell, pwsh or cmd.

Terminal tab title in VS Code​

The CLI sets the terminal title to the current chat. Most terminals show it as is. VS Code and editors built on it (Cursor, Windsurf, Antigravity) show only the process name unless the tab title setting includes ${sequence}. Add this to your VS Code settings:

"terminal.integrated.tabs.title": "${sequence}"

For more on features and usage, see the Abacus AI Desktop introduction. To configure the CLI, see Settings.