Skip to main content
This page lists Mirror CLI’s commands, shortcuts, options, and files for quick lookup. For explanations, start with the overview. Mirror is in early beta; run /help and mirror --help to see what your installed version supports.

Slash commands

Type / in the prompt to browse commands, or type a command’s name and press Enter. Commands marked Idle only are rejected while a turn is running. Wait for it to finish, or press Escape, then run the command again.

Conversations and workspaces

Models, connections, and settings

Screen and session

/model, /effort, /login, /logout, /approvals, /settings, /connect, /connections, /disconnect, /web-provider, /memory, /context, /usage, /feedback, /editor, /themes, and /tips come from bundled extensions, and disappear if you turn their extension off.

Keyboard shortcuts

In the prompt

In lists and prompts

Change shortcuts

To change a shortcut, create ~/.mirror/keybindings.json and restart Mirror. Each entry replaces all the keys for one action, and an empty keys list disables the action. Keys use prompt-toolkit names, such as c-g for Ctrl+G. For example, to make Ctrl+C always exit:
~/.mirror/keybindings.json
Escape can only be bound to InterruptRequested. Projects can’t change your shortcuts.

Launch options

Run mirror in the directory you want to work in to open the interactive CLI. Passing a prompt runs a noninteractive session. --model and --api apply to one launch only, while /model changes the saved selection. --approval-mode is saved for later launches. /status shows the active values.

Noninteractive use

Passing a prompt is shorthand for mirror exec PROMPT. Both run one new local session without the TUI and print the final answer:
Omit the prompt or use - to read it from stdin. Piped input alongside a prompt argument is appended in a <stdin> block. First open Mirror interactively in that directory to accept the usage and folder notices. Supply provider credentials through the environment or a saved login; exec rejects --api-key. Calls that require approval fail, so select --approval-mode auto only when you want automatic tool approval. exec starts a fresh session without extensions and doesn’t support --continue or --conversation-id.

ACP clients

Run mirror acp to serve the Agent Client Protocol on stdin/stdout for a client such as Zed or Omnigent. The client sends prompts and receives responses and tool calls. Approval requests go to the client, and cancellation interrupts the turn. Model and reasoning flags apply. Like exec, ACP uses environment credentials or a saved login, starts fresh sessions without extensions, and requires the directory’s notices to have been accepted interactively.

Startup updates

Interactive installations can check for updates and ask before installing a newer release. Accepting an update installs it alongside the current version. Use MIRROR_SKIP_UPDATE=1 mirror to bypass both checks and cached releases. Update selection doesn’t remove your configuration or conversations. Run mirror update in an interactive terminal to check for an update without starting a session. It asks before installing and exits when finished. Updates require uv on your PATH. To upgrade the original tool installation, run uv tool upgrade reflection-mirror.

Environment variables

Export web provider keys before launching Mirror. A key alone doesn’t select its provider; /web-provider saves the selection in ~/.mirror/config.json, which mirror exec and mirror acp also use. Commands the agent runs don’t receive REFLECTION_API_KEY, OPENAI_API_KEY, ANTHROPIC_API_KEY, OPENROUTER_API_KEY, GEMINI_API_KEY, YOU_API_KEY, TAVILY_API_KEY, or FIRECRAWL_API_KEY.

Files

Mirror keeps its data in ~/.mirror/:
~/.mirror
analytics
memory
sandboxes
worktrees
AGENTS.md
PINNED_MEMORIES.md
cli.db
config.json
keybindings.json
last_model.json
models.json
reflection_api_key
state.db
tool_approvals.json
Reinstalling or upgrading Mirror doesn’t change these files. Mirror also reads these files from your repository, in each directory from the repository root down to your working directory:
your-repo
AGENTS.md

Usage analytics

Mirror sends product usage events to Statsig so Reflection can see how its features are used. An event records that something happened, such as a submitted prompt, a slash command, a tool call, or a finished compaction, with counts and durations. To turn analytics off, open /settings and switch Usage analytics off, or set "analytics": false in ~/.mirror/config.json. Events that couldn’t be sent are saved in ~/.mirror/analytics/ and retried the next time Mirror starts with analytics on, which also drops any older than five days. Turning analytics off leaves that folder as it is; delete it to remove unsent events.

Report a bug

  1. Run /feedback and confirm Open GitHub form, or open the feedback form yourself. Mirror attaches no session data. Write and review the report on GitHub before submitting it.
  2. Include your operating system, the output of mirror --version, the steps that cause the problem, and any error message.
  3. If you attach logs from ~/.mirror/logs/, review them first and remove anything private. Issues are public.
Don’t share logs recorded with --log-level debug: they include request headers, which contain your API key.
Last modified on November 19, 2026