The den guide
How den works, from the first sign-in to the audit log, in the order a new person meets it: the two ways in first, then the mechanics. Every page is short and says what to do.
Start here
Getting started
What den is, the two ways in, how you get an account, and the first ten minutes: a workspace, a topic, an artifact, and an agent connected.
3 minden for households
One memory for the whole house, in the Claude you already use. What the house keeps, how it is added to Claude once, what to say to it, and what it asks before it acts.
3 minden for software developers
The memory your agents and your team share, versioned. What a project keeps, the plugin that installs the connector and the skill together, how a session starts and ends, and how the kind grows into a product of its own.
3 minUsing den
Topics, artifacts, and versions
The unit of work in den: a topic with named artifacts, every write a version that names the one it read, leases for long edits, and a trash that keeps everything.
2 minKinds
Kinds are workflow contracts: which artifacts a topic declares, who owns each, and the instructions an agent follows to write it. Built-in kinds, your own kinds, and the marketplace.
2 minWorkspaces, roles, and the audit log
A workspace is the unit of visibility. Four roles say what a member may do, staff runs den without seeing inside, and the audit log records who changed what and which version.
2 minSharing outside the workspace
Share links give anyone read-only access to one artifact or a whole topic, with optional expiry and instant revocation. Public topics are readable at a stable address.
1 minSearch
One search box over every artifact in a workspace, lexical and semantic together, with filters and a confidence flag that says when den has nothing.
1 minAgents
Connect an agent
One install brings the den connector and the skill that tells an agent how to use it. Claude Code takes a plugin; claude.ai and every other MCP client take the same URL as a connector; sign-in happens in the browser.
6 minSkills
A skill is a procedure an agent loads before it acts. In den a skill is its own resource, versioned like an artifact, listed on a topic, and installed on each machine from one live copy.
1 minPower users
Reference
Security and your data
How sign-in, tokens, roles, and staff access work; what den encrypts, logs, and backs up; and what leaves a workspace only when you say so.
2 minRun your own den
For teams that need den in their own account: one command deploys it, what it creates, how to update, and how data migrations work.
1 minAgents: the same pages are at /llms.txt, each as plain markdown, and den's own procedure is /skill.md.