Feature status
Feature status
What is settled and what is still moving. den is below 1.0, so its keys and commands can
change between minor versions; a change that breaks an existing den.yaml or command gets a
Breaking: line at the top of its changelog entry, with the migration.
| Status | Means |
|---|---|
| Stable | In regular use and documented. A change that breaks it comes with a Breaking: line in the changelog. |
| Beta | Works and is documented, but is newer and has seen less use. Its keys and behaviour may still change. |
| Planned | Not implemented. |
Beta
| Feature | Page |
|---|---|
Writing and changing a runbook with an agent: den runbook new --agent, n and E in the Runbooks panel, the agent: key and agents: entries | CLI, panel, MCP |
Runbook sources: runbooks from a git repository, den.lock, trust | Runbook sources |
| Terminal tabs: the data store’s client inside den | Terminal tabs |
Planned
| Feature | State |
|---|---|
| Kafka (Amazon MSK with IAM auth) | A kafka service loads and validates, and connecting it reports that Kafka is not implemented yet. |
Stable
Everything else: the Connect, Tunnel, VPN, AWS, Secrets, Runbooks, Config, Logs, Help and Updates
panels; RDS, ElastiCache,
MemoryDB, DocumentDB,
Redshift, OpenSearch and
Neptune; transports; SOPS, AWS Secrets Manager,
KeePassXC and Vault secrets; runbooks, sequences and den run;
den mcp; den doctor, den init and the
JSON Schema.
Known gaps
- Updating den from inside den on Windows is untested. den replaces its binary by renaming a new one
over it, which Windows may refuse while
den.exeruns, and the restart after an update is offered on macOS and Linux only. On Windows, install a new version withinstall.ps1(Install). - The VPN needs a kernel with PPP. WSL 3.0.1’s kernel has none; see Troubleshooting.
- Planned secret providers (AWS SSM Parameter Store and a generic
commandprovider) are in the commented examples ofden.yaml, not implemented: using one stops den loading the file.
Last updated on