Use the Flixa CLI

The Flixa CLI runs the Flixa coding agent in your terminal. It reads your project, edits files, and runs commands, asking for your OK first. You can use it with your Deni AI account or with your own API key from another provider (BYOK).

To point Claude Code or Codex at Flixa instead, see Use Flixa with external coding tools.

InstallCopy Anchor Link

npm install -g @deniai/flixa

With pnpm:

pnpm install -g @deniai/flixa

Sign inCopy Anchor Link

flixa login

Pick a provider from the list. The provider you sign in to becomes your default.

With your Deni AI accountCopy Anchor Link

Choose Flixa. Then choose how to open the authorization page:

• Open browser automatically: your browser opens the page.
• Show URL (open manually): for SSH sessions and other machines without a browser.

The terminal shows a code and a URL. Open the URL, check that the code matches, and click Approve. The CLI saves the key for you. Guest accounts can't approve; sign in with a permanent account first.

With your own API key (BYOK)Copy Anchor Link

Built-in providers are flixa, openai, anthropic, google, openrouter, and custom-openai. More providers come from a bundled catalog.

flixa login --provider anthropic

Enter the provider's API key when asked. Requests then go to that provider with your key. For your own OpenAI-compatible endpoint, pass its base URL:

flixa login --provider custom-openai --base-url http://localhost:1234/v1

To see every provider and which ones are set up:

flixa providers list

To switch the default provider later:

flixa providers set-default anthropic

To pick a default model for the current provider:

flixa model

Chat with the agentCopy Anchor Link

Run this in your project folder:

flixa chat

Type what you want and press Enter. Flixa asks before it edits files or runs shell commands. Use ←→ and Enter to approve, or Esc to deny.

To pick up where you left off:

ModesCopy Anchor Link

Press Shift+Tab to cycle through the modes. You can also start in one with --accept-edits, --plan, --auto, or --yolo-mode.

An ask permission rule (see below) still asks in accept edits and auto modes.

In-chat featuresCopy Anchor Link

Long conversations are also compacted automatically once they pass about 240,000 characters. Set FLIXA_AUTO_COMPACT_CHARS to change the limit, or 0 to turn it off.

Flixa reads CLAUDE.md, AGENTS.md, and .claude/CLAUDE.md from your project as instructions.

What the agent can do on its ownCopy Anchor Link

• Run long commands in the background and check their output later.
• Hand work to sub-agents. general-purpose and a read-only explore agent are built in.
• Load skills when a task needs them.
• Keep a task list, and read public web pages (it asks first and can't reach private or local addresses).

/agents, /skills, /permissions, and /hooks show what's set up.

Add your own commands, sub-agents, and skillsCopy Anchor Link

Flixa looks in .flixa/ and .claude/ folders, in your project and in your home folder.

Your own commands never replace built-in ones. Sub-agents can't start other sub-agents.

Set permission rules and hooksCopy Anchor Link

Put rules and hooks in a settings.json file:

• Your settings: ~/.flixa/settings.json or ~/.claude/settings.json
• Project settings: .flixa/settings.json or .claude/settings.json, plus settings.local.json in the same folders

{
  "permissions": {
    "allow": ["Bash(pnpm test:*)", "Read(src/**)", "WebFetch(domain:docs.example.com)"],
    "ask": ["Write(docs/**)"],
    "deny": ["Read(.env)", "Bash(git push:*)"]
  },
  "hooks": {
    "PostToolUse": [
      { "matcher": "Edit|Write", "hooks": [{ "type": "command", "command": "pnpm run format" }] }
    ]
  }
}

• deny wins over ask, and ask wins over allow.
• A combined command such as pnpm test && curl ... is allowed only if every part is allowed.
• Rules for Read, Write, Edit, Grep, and Glob apply only to those tools. They don't stop a shell command from reading the same file.
• Hooks run on PreToolUse, PostToolUse, UserPromptSubmit, and Stop. They get a JSON payload on stdin. Exit code 2 blocks the action and sends stderr back to Flixa.

Use Flixa in scriptsCopy Anchor Link

--print runs one prompt without the interactive screen. Only the final answer goes to stdout, and progress goes to stderr, so you can pipe the output.

flixa --print "Summarize the last commit"

git diff | flixa --print "Review this diff"

Your custom commands work here too:

flixa --print "/review src/index.ts"

Actions that need approval are denied unless you add --accept-edits, --auto, or --yolo.

Ship a task in one runCopy Anchor Link

flixa ship takes one task and runs it start to finish: it inspects the repository, makes the change, and verifies it.

flixa ship "Add a retry budget to the API client"

By default it runs in guarded auto mode: edits and commands get a safety review, and clearly destructive commands are blocked.

You can pass a GitHub Issue URL as the task. Flixa reads the issue's title, body, and labels, and treats them as untrusted context.

flixa ship https://github.com/org/repo/issues/123

When a card is created, its Markdown is copied to your clipboard. A card published with --share-url contains the changed-file list, diff stat, verification result, model, and final summary. It doesn't publish your source code. To make a card from your latest session later, run flixa share.

Check your usageCopy Anchor Link

flixa usage

This shows your Flixa plan and usage limits. It needs a Flixa sign-in. Flixa works on every signed-in plan, Free included. BYOK providers use your own key, not your Deni AI plan.

Check your setupCopy Anchor Link

flixa doctor

This checks your Node.js, Git, ripgrep, shell, saved credentials, instruction files, and network connection. Add --offline to skip the network check.

Sign outCopy Anchor Link

flixa logout

This removes the saved Flixa key. For another provider, add --provider:

flixa logout --provider anthropic

Signing out doesn't change Claude Code or Codex settings made with flixa claude-code or flixa codex.

TroubleshootingCopy Anchor Link

"Already logged in"

Run flixa logout, then flixa login again. For other providers, add --provider <provider> to both commands.

"Not logged in"

Run flixa login. If you use a BYOK provider, run flixa login --provider <provider>.

Where are my keys stored?

In the Keychain on macOS, a DPAPI-encrypted file on Windows, or secret-tool on Linux. Without secret-tool, Linux falls back to a file in ~/.flixa/ and shows a warning.