CLI troubleshooting

Start with Autter’s built-in diagnostics:

autter debug
autter bg status
autter whoami
autter config

No attribution appears

Restart the coding agent

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

Refresh integrations

Run:

autter install-hooks

Make a tracked edit

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

Check repository filters

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

autter bg status
autter bg restart
autter bg tail -n 100

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

Retry the primary flow first:

autter onboard --force

If onboarding still cannot complete:

Sign in at app.autter.dev.
Open the intended organization and create a PAT under Org Settings → Access Tokens.
Run autter login --token <token>.
Confirm the connection with autter whoami.

Do not paste the token into tickets, chat, or command output you share.

Check the active backend and prompt mode:

autter config notes_backend.kind
autter config prompt_storage
autter whoami

Return to local-only mode and disable open source error telemetry:

autter logout
autter onboard --local --force
autter config set telemetry_oss off

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

Run autter debug and review the output before sharing it. Remove repository paths, identities, tokens, and other sensitive values.

Report reproducible open source CLI problems.