Docs › Account and usage › What AstraCode sends and keeps
What AstraCode sends and keeps
What leaves your machine when you work, what AstraCode records, what stays on disk, and the settings that turn each part off.
On this page
- Privacy Mode is always on
- What goes through the gateway when you work
- What AstraCode records about how you use it
- Agent outcomes and feature use
- Tab completion quality
- What stays on your machine
- Problem reports
- Sending a run
- Your credentials
- Turning things off
This page describes what the editor sends and stores, setting by setting, so you can decide what to keep on. The legal terms are in the privacy notice.
Privacy Mode is always on
AstraCode Settings > General shows Privacy Mode as Always on, with a padlock, because there is nothing to switch: your code is not trained on, not used to improve the product, and not stored. The gateway records which model served a request and how many tokens it used. No prompt and no reply is written down, on any setting.
What goes through the gateway when you work
To answer you, AstraCode sends the model what it needs, through the AstraCode gateway (astracode.gatewayUrl, https://api.astracode.io by default) to the model provider:
- Chat and the agent: your messages, attachments, the files the agent reads, the output of the commands it runs, results from connectors, and your rules and memories.
- Tab completion: the 2,000 characters before the cursor and 600 after it, the file's path, its language, and the signatures of what the file imports. Nothing excludes secret files on its own; list them in
astracode.tab.ignoredFiles, or turn offastracode.completions.enabled. - The codebase index: each source file, in function-sized pieces, so the agent can search by meaning. The resulting vectors stay on your machine under
~/.astracode/index. Nothing is indexed in a folder you have not trusted. Turn it off withastracode.index.enabled. - Web search: the search query, which the gateway passes to a search service. Turn it off with
astracode.agent.webSearch. - Dictation: the recording, to be transcribed.
- Inline edit, commit messages and branch reviews: the selection, the staged diff or the branch diff they work on.
Pages the agent reads with web_fetch, and pages it opens with the browser tools, are fetched from your machine, not from ours.
What AstraCode records about how you use it
Agent outcomes and feature use
astracode.agent.reportOutcomes (default on) sends counts and fixed labels with your account: how each agent run ended (finished, stopped, looped, hit the step limit, or failed, and which kind of failure from a fixed list), which kind of error the panel showed you, whether an update worked and where it failed, how many steps and tool calls a run took, which tools errored and how often, whether the project's checks passed, how many steps were left open, and whether the reply stayed in the language you wrote in.
From 18 November 2026 it also covers which AstraCode command you ran, which panel button or action you used, which AstraCode setting you changed (never its value), when the editor starts and closes, when you sign in and out, when it showed you a usage limit, and, for each finished run, whether you kept it, edited its files yourself (never which), asked again, how you rated it, and its own check with the kinds of problem found, each with its time.
Before you sign in, these go under a random install id, which joins your account when you sign in. There are no prompts, no code, no file names, no command lines and no error text, and none of the fields is free text. Turn it off and the agent works exactly the same.
Tab completion quality
astracode.completions.reportQuality (default on) sends whole numbers every 30 minutes and when the editor closes: how many suggestions were shown and accepted, how many were avoided or served from the cache, how many requests failed, and how long requests took. They are sent with your account, so they are not anonymous, and nothing is sent while you are signed out. No code, file names or paths. Turn it off and completions work exactly the same.
What stays on your machine
| What | Where | How long |
|---|---|---|
| Chat history | The editor's own storage, one file per chat | Until you archive it; there is no automatic deletion |
| Chat transcripts the agent can read back after a summary | ~/.astracode/projects/<project>/ | astracode.transcripts.retentionDays, 30 days by default; 0 keeps none |
| Checkpoints for undo | The editor's own storage, outside your repository | The newest 200 |
| Memories | ~/.astracode/memories | Until you delete them |
| Lessons from fixed failures | ~/.astracode/lessons | Dropped after 45 days unless learned again |
| Codebase index vectors | ~/.astracode/index | Rebuilt as files change |
| Background task output and subagent transcripts | The editor's own storage | astracode.agent.taskRetentionDays, 30 days by default |
| Plans | .astracode/plans in the project, or ~/.astracode/plans | Until you delete them |
Transcripts hold whatever the chat held, including code. None of these files is sent anywhere unless you send it.
Problem reports
AstraCode: Report a Problem sends what you write, an optional screenshot or recording, and a block of diagnostics: the editor version, platform, install type, how many folders are open, whether there is a git repository, the mode and approval setting, the panel's state, a pending update, recent failures (status and reason only) and recent lines of the editor's own log. No paths, folder or file names, branch names, prompts, replies, code, tokens or email. You see the whole report before it goes, and nothing is sent until you choose Send. See Reporting a problem and getting help.
Sending a run
Send this run to the AstraCode team, on a run's summary card, sends that run's request, the agent's reply, its own check and the diffs of the files it changed. Before anything goes, secrets are removed and marked [removed], .env values are blanked, key files and binary files are left out, and a read-only preview opens so you can read every line. The run is kept for 30 days, can be read only by the founders, can be deleted from your dashboard, and is never used for training.
Your credentials
- Your sign-in session and your own API key are kept in the operating system's keychain through the editor's secret storage.
- Connector tokens you paste, such as a GitHub token, are kept there too, and sent only to the connector they belong to.
astracode.gatewayUrlis fixed for the whole application, so a repository you open cannot redirect your credentials somewhere else.
Turning things off
| To stop | Turn off |
|---|---|
| Agent outcome and feature-use counts | astracode.agent.reportOutcomes |
| Tab completion quality counts | astracode.completions.reportQuality |
| Tab completion entirely | astracode.completions.enabled |
| Sending code for search by meaning | astracode.index.enabled |
| Web searches | astracode.agent.webSearch |
| The agent reading web pages | astracode.agent.webFetch |
| Local chat transcripts | Set astracode.transcripts.retentionDays to 0 |
| Memories | astracode.memories.enabled |
| Lessons | astracode.agent.lessons |
Every setting is described in the settings reference.
← Bring your own key Reporting a problem and getting help →
All documentation
Get started
Using the editor
- Tab completion
- Edit and ask about a selection
- Reviewing the agent's changes
- Git: commit messages, branch review and conflicts
- Dictation
- Layout, themes and the settings page
Agent
- Agent overview
- Agent, Plan, Ask and Debug
- Approvals and permissions
- Plan mode
- Debug mode
- Tools
- Browser tools
- How the agent checks its work
- Checkpoints and undo
- Running several agents at once
- Subagents and background tasks
- Remote agents in GitHub Actions
- Infrastructure as code
Context
Workspaces
Connectors
- Connectors (MCP servers)
- Connector configuration reference
- Use AstraCode from Claude, ChatGPT and other apps
Extending AstraCode
CLI
Account and usage
- Usage and limits
- Bring your own key
- What AstraCode sends and keeps
- Reporting a problem and getting help
Troubleshooting
- Troubleshooting
- Sign-in problems
- Install and update problems
- Chat panel problems
- Agent run problems
- Connector problems
- Dictation problems
- Usage, billing and network errors
- CLI problems