Skip to main content
You choose whether the Autter CLI stays local or connects to the Autter platform. You can change this choice at any time.
Placeholder diagram of Autter data moving from a developer machine to Git notes and an optional organization cloud

​
Storage at a glance

DataLocal-onlyConnected personal dashboardTeams or Enterprise
Prompt recordsLocal SQLiteUploaded unless prompt_storage is localTeam prompt store, with best-effort secret and PII redaction
Line-level attributionLocal Git notesLocal Git notesLocal Git notes plus team and SCM-linked processing where enabled
Agent and model identifiersGit notesGit notes and connected transcript or usage recordsGit notes and team analytics
Git name and emailGit notesUsed with connected attributionStored as employee identity and SCM membership
Tool calls, MCP calls, skills, errors, interruptions, tokensNot uploaded as cloud analyticsUploaded for personal analyticsUploaded for team analytics
SCM profile and pull request metadataNot uploaded by local-only CLISCM profile metadataPR description, opener, reviewer, status, and related metadata
Pull request diffsNot uploaded by local-only CLIDepends on connected product workflowProcessed to compute AI percentage; not stored
Error and exception telemetrySent by defaultSent by defaultSent by default unless disabled or redirected
Autter’s public CLI privacy document does not state a universal cloud retention period. Check your agreement, deployment policy, or the Autter Trust Center for current terms.

​
Local-only mode

Without login, Autter says it does not send code, prompts, or agent-usage data to the Autter platform. Local-only storage includes:
  • Prompt records in local SQLite storage
  • Temporary checkpoints under .git/ai
  • Attribution in Git notes, including the agent, model, line ranges, acceptance metrics, and steering developer’s Git name and email
Git notes are part of the repository’s Git data. Anyone who receives the notes and has repository access can read their metadata. The open source CLI sends error and exception telemetry by default. Disable it with: 
autter config set telemetry_oss off

​
Connected personal dashboards

When you opt in to a personal dashboard, Autter Cloud receives:
  • Agent activity such as tool calls, MCP calls, skills, interruptions, errors, and token usage
  • Prompts and agent responses used for personal analytics
  • AI percentage, parallel-agent counts, and related dashboard metrics
  • SCM profile metadata from GitHub, GitLab, or Bitbucket
Personal agent-usage data is visible only to you unless you share it.

​
Transcript upload path

When a commit has a captured agent transcript, Autter:
  1. Reads and normalizes the local JSON or JSONL transcript.
  2. Removes detected secrets before the transcript leaves the machine.
  3. Queues the transcript in local durable storage as a content-addressed object.
  4. Adds a cas:<hash> reference to the prompt record in the authorship note.
  5. Lets the background service upload queued content to the connected organization environment.
This process is best-effort. Missing, empty, or invalid transcripts are skipped, and transcript failures do not block commits.

​
Teams and Enterprise

Team deployments can also store:
  • Employee names, email addresses, and SCM team membership
  • Full prompt records with best-effort secret and personal-data stripping
  • Full agent sessions for review and summarization
  • Pull request metadata from supported SCMs
  • Organization-wide attribution, token, cost, and agent-usage analytics
Prompt records are write-only for developers unless an administrator grants read access. Self-hosted deployments send this data to the team’s own Autter instance.

​
Opt out of cloud storage

To clear credentials and reselect local-only mode: 
autter logout
autter onboard --local --force
This stops future connected writes from that machine. It does not automatically delete data uploaded before you opted out.
Switching to local-only mode does not delete existing organization data. Use your organization’s deletion process or contact Autter support for a deletion request.

​
Stay connected but keep prompts local

You can keep platform authentication while preventing future prompt uploads: 
autter config set prompt_storage local
Attribution and other enabled telemetry can still sync. Use local-only mode if you want to stop connected storage as a whole.

​
Disable Autter for a repository

From the repository, run: 
autter config --add exclude_repositories .
This adds the repository’s remote to your machine-level exclusion list.

​
Protect sensitive data

  • Never place credentials or secrets in agent prompts.
  • Keep prompt_storage set to local for repositories that cannot upload prompts.
  • Review Git-note access because attribution includes developer identity.
  • Store CI access tokens in a secret manager.
  • Review organization permissions before enabling prompt access for developers.
For published policy details, see the Autter privacy policy and Trust Center.