Skip to main content
Start with Autter’s built-in setup validation:

​
Validate the setup with autter doctor

autter doctor checks the installation end-to-end and prints a fix line for every failed check. It verifies:
  • The Git version and the Autter configuration file
  • The repository filters that decide whether the current repository is tracked
  • The background service and its Git event capture
  • A real checkpoint round-trip, from checkpoint through commit to line-level attribution
  • Integration status for the coding agents detected on the machine
  • Login state, plus platform reachability in connected mode
The command exits 0 when no check fails and 1 otherwise, so you can use it in scripts. Add --json for a machine-readable report. If every check passes but something still looks wrong, gather more context:

​
autter: command not found

In an already-open terminal on macOS, Linux, or WSL, load the installer’s PATH entry directly:
For fish, use source "$HOME/.autter/env.fish". New terminals load it automatically through your shell configuration; IDE terminals need an IDE restart, not just a new terminal tab. If the command is still not found in a fresh terminal, the installer could not detect a shell configuration file. Add this line to your shell configuration (the env.fish variant for fish) and restart the shell:

​
No attribution appears

1

Restart the coding agent

Agent hooks are loaded when a session starts. Restart the agent or editor after installing Autter.
2

Refresh integrations

Run:
3

Make a tracked edit

Ask the agent to modify a file inside the repository, then run autter status before committing.
4

Check repository filters

Run autter config allow_repositories and autter config exclude_repositories. Exclusion takes precedence.

​
The background service is unavailable

Use autter bg tail -f to follow logs while reproducing the issue.

​
Onboarding does not connect

Retry the primary flow first:
If you are already onboarded and only need to sign in again:
Autter opens a browser and waits for you to approve the device. If that still cannot complete:
  1. Sign in at app.autter.dev.
  2. Open the intended organization and create a PAT under Org Settings → Access Tokens.
  3. Run autter login --token <token>.
  4. Confirm the connection with autter whoami.
Do not paste the token into tickets, chat, or command output you share.

​
Data uploads when you expected local-only mode

Check the active backend and prompt mode:
Return to local-only mode and disable open source error telemetry:

​
Attribution is missing after a rename

git mv attribution preservation is not supported yet. Autter can treat lines in the renamed file as new or human-authored.

​
Get support diagnostics

Run autter doctor first and apply the fixes it prints. When you need a full report to share, run autter debug and review the output before sharing it. Remove repository paths, identities, tokens, and other sensitive values.

Open a GitHub issue

Report reproducible open source CLI problems.