pari. CLI
Install →

First session

First session

Sign in, open the repository you want changed, and ask PARI to do the work.

Sign in

From any directory:

pari-cli login

The menu asks for a provider, then an API key or an account token. DeepSeek accepts an API key only. You can also pass the credential without the menu:

pari-cli login deepseek --api-key sk-...

The secret is written to ~/.pari/auth.json and is not copied into the sandbox. See Models for every provider.

Open a workspace

PARI edits the directory you start it in. Move there first, or pass --workspace.

cd ~/projects/my-app
pari-cli --dry-run

On Linux, a good dry run looks like this:

PARI v0.1.7 — Terminal Coding Agent (https://pari-cli.in)
Workspace: /home/you/projects/my-app
Sandbox: auto
Model: deepseek-chat
Self-check passed.

If the workspace path is wrong, stop and start again in the right directory. Files outside that directory cannot be pinned or edited.

Start a conversation

pari-cli

At the prompt, describe the outcome you want. For example:

Fix the failing test in tests/test_api.py and update the README.

PARI searches, edits, and, on Linux, runs commands such as the test runner. When it finishes a step, look at what changed before you ask for the next thing.

Review the change

At the promptWhat it does
/diffShow the uncommitted diff in the workspace.
/undoRevert files changed by the latest turn.
/add README.mdPin a file so the next turn keeps it in context.
/costShow token and cost totals for this session.
/exitLeave the session. The project log stays on disk.

The rest of the slash commands are on the Commands page.

Run it again

Next time, the same two commands are enough if you are still signed in:

cd ~/projects/my-app
pari-cli

Next

  • Commands →

    Flags, search subcommands, and every slash command.

  • Sandbox →

    What those shell commands are allowed to touch.