Matt Vollmer
506fba9ebf
Fixes several documentation gaps and inaccuracies in the Coder Agents docs identified during a deep review against the current product state. ## BYOK (User API Keys) `models.md` stated *"Developers cannot add their own providers, models, or API keys"* — this has been incorrect since the provider key policy system shipped (Apr 2, #23751/#23781). - Added **Key policy** section documenting the three admin toggles (`central_api_key_enabled`, `allow_user_api_key`, `allow_central_api_key_fallback`) with a truth table showing all resolution outcomes - Added **User API keys (BYOK)** section covering the developer-facing key management page, status indicators, selection priority, and key removal - Updated `platform-controls/index.md` to reference BYOK instead of claiming keys are admin-only ## Reasoning effort enum fixes - **OpenAI**: removed `none` — code accepts `minimal, low, medium, high, xhigh` - **OpenRouter**: narrowed to `low, medium, high` per `ReasoningEffortFromChat` in `chatprovider.go` ## Tool table completeness - Added `spawn_computer_use_agent`, `read_skill`, `read_skill_file` to `index.md` tool table - Added "Workspace extension tools" section to `architecture.md` for `read_skill`/`read_skill_file` - Fixed orchestration restriction note to list all 5 gated tools instead of just `spawn_agent` - Added conditional availability notes for desktop and skills tools ## Platform controls Three admin-only settings existed in the Behavior tab with no documentation: - **Virtual desktop** — admin toggle, Anthropic + portabledesktop requirements - **Workspace autostop fallback** — default TTL for agent workspaces without template-defined autostop - **Data retention** — moved `chat-retention.md` into `platform-controls/` since it's admin-only, fixed nav path --- > PR generated with Coder Agents
2.1 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.
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, it is deleted along with its messages, diff statuses, and queued messages via cascade. Orphaned files (not referenced by any active or recently-archived conversation) are also deleted. Both 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.
The retention period is stored as the agents_chat_retention_days key in the
site_configs table and can also be managed via the API at
/api/experimental/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 active or recently-archived conversation | — |
Unarchive safety
If a user unarchives a conversation whose files were purged, stale file references are automatically cleaned up by FK cascades. The conversation remains usable but previously attached files are no longer available.