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>
1.9 KiB
Chat Debug Data Retention
Coder Agents automatically cleans up old chat debug data to manage database growth. Debug data includes persisted debug runs and their associated debug steps.
This setting is independent from conversation data retention, which only purges archived conversations and orphaned files.
How it works
A background process removes debug runs older than the configured retention period. When a debug run is deleted, its debug steps are deleted via cascade.
The retention clock uses the debug run's updated_at value, which reflects the
last write to the debug run. It does not use the chat archive time. If a debug
run remains in progress for an unusually long period, such as after broken
finalization, it can still be purged once its updated_at value is older than
the cutoff.
Configuration
Navigate to the Agents page, open Settings, and select the
Lifecycle tab to configure chat debug data retention. The default is 30 days.
Set the value to 0 to disable debug data retention entirely. The maximum value
is 3650 days.
Use the admin API to read or update the value:
GET /api/v2/chats/config/debug-retention-days
PUT /api/v2/chats/config/debug-retention-days
Interaction with conversation retention
Conversation retention and debug data retention are orthogonal controls:
| Control | What it deletes | Default |
|---|---|---|
| Conversation retention | Archived conversations and orphaned files | 30 days |
| Debug data retention | Debug runs and debug steps, based on debug run updated_at |
30 days |
Deleting a chat still deletes its debug data immediately via cascade, regardless of the debug retention window. Unarchiving a chat does not restore debug data that was already purged.