Matt VollmerandNick Vigilante
75e0790cd7
Removes all references to "beta" from the Coder Agents documentation under `docs/ai-coder/agents/` and the corresponding `"state": ["beta"]` entries in `docs/manifest.json`. Also updates screenshots, video, and hero image, and regenerates the auto-generated feature-stages table. **Beta reference removal:** - `getting-started.md`: Removed "Coder Agents is in Beta" from the top note, "is in beta" from the Chats API note, and "during Beta" from the feedback section. Removed the version/stability note pinning 2.33.1. - `index.md`: Removed the "Product status" section that stated Coder Agents is in Beta. - `manifest.json`: Removed `"state": ["beta"]` from 17 entries for pages under `docs/ai-coder/agents/`. Preserved all `premium` and `early access` states. - `feature-stages.md`: Regenerated the auto-generated beta features table, which no longer lists Coder Agents. **Asset updates:** - `coder-agents-ui.mp4`: Updated demo video on the agents landing page. - `llm-providers.png`: Updated LLM provider support screenshot. - `models-list.png`: Updated models list screenshot. - `models-add-model.png`: Updated add model form screenshot. - `agents-hero-image.png`: Updated hero image on the `docs/ai-coder` landing page. Two references in `models.md` (`v1beta` in the Google Gemini API URL and `anthropic-beta` in the Anthropic header name) were left unchanged as they are provider API identifiers, not product status labels. PR generated with Coder Agents --------- Co-authored-by: Nick Vigilante <nickvigilante@users.noreply.github.com>
2.5 KiB
Conversation Data Retention
Coder Agents automatically cleans up old conversation data to manage database growth. Archived conversations and their associated files are periodically purged based on a configurable retention period.
Conversations become eligible for purging only after they are archived. Old conversations can be archived manually, or automatically. See Auto-Archive for how the two controls interact.
Debug run and step cleanup is controlled separately. See Chat Debug Data Retention.
How it works
A background process runs approximately every 10 minutes to remove expired conversation data. Only archived conversations are eligible for deletion — active (non-archived) conversations are never purged.
When an archived conversation exceeds the retention period, Coder deletes it along with its messages, diff statuses, and queued messages. Coder retains an attached file while any conversation references it, regardless of whether the conversation is active or archived. A file that exceeds the retention period becomes eligible for deletion only after no conversations reference it. Conversation and file cleanup operations run in batches of 1,000 rows per cycle.
Configuration
Navigate to the Agents page, open Settings, and select the Behavior tab to configure the conversation retention period. The default is 30 days. Use the toggle to disable retention entirely.
Use the admin API to read or update the value:
GET /api/v2/chats/config/retention-days
PUT /api/v2/chats/config/retention-days
What gets deleted
| Data | Condition | Cascade |
|---|---|---|
| Archived conversations | Archived longer than retention period | Messages, diff statuses, queued messages deleted via CASCADE. |
| Conversation files | Older than retention period and not referenced by any conversation | None |
Unarchive safety
Archiving a conversation does not make its attached files eligible for deletion. If you unarchive a conversation before Coder purges it, its attachments remain available, even when the files exceed the retention period.