Getting started

den is the memory behind the assistant you already use. Say something to Claude, on a phone or in a terminal, and den keeps it with its history, for the people you share it with. One memory, reachable from every assistant, and yours to take as ordinary files.

There are two ways in, and each has its own page in this guide because each speaks its own words:

• den for households: one memory for the whole house. Groceries, who to call, what is due, what happened. Added to Claude once; then everyone at home just talks to it.
• den for software developers: the memory your agents and your team share, versioned. A session starts where the last one stopped, and nobody re-explains the project.

Underneath, it is one den. A project or a house is a topic. A topic holds named, versioned artifacts: for a project the status, the journal, the spec; for a house the groceries, the contacts, the journal. Every write is a new version that names the version it read, so two writers never overwrite each other. People read and write through the app; assistants read and write through one MCP connector, with the same words. The rest of this page is the mechanics, in the developer's words.

#Getting in

den is invite-only. Someone on your team with the staff role sends you an invite, or you ask for one at /request-access. The invite link opens a page where you set a password, or continue with a Google account whose address matches the invite. The first time you sign in, a short wizard asks your name, what you do and what you are interested in, suggests what to set up, and offers to connect Claude. You get a personal workspace named after you.

Sign in at /signin with your password or with Google; either gives the same session. Your session lasts thirty days on that browser; the Tokens and devices page shows every browser, laptop, and connector that can act as you.

#The screen

The sidebar has one switcher and a handful of pages.

• Workspace switcher. A workspace is the unit of visibility. You get a personal one; a team works in a shared one. Everything below the switcher belongs to the workspace you picked.
• Topics. The projects in this workspace. Open one to see its artifacts. Deleted ones wait in Trash.
• Kinds, Marketplace and Skills. What topics follow, what can be installed, and the procedures an agent loads.
• Members and Audit. Who is in the workspace, with what role, and who changed what.
• Connect an agent and Tokens and devices. The connector URL, the CLI line, and every credential that acts as you.

#Your first topic

1. Open Topics and press New topic. A key is a stable id such as q4-plan or INT-3653, not a sentence. Pick a kind; note fits when nothing else does.
2. Open the topic. The kind says which artifacts it expects. Write the first one in the editor, or paste a file.
3. Every save is a version. The version list shows who wrote each one and when, and any version can be read again.

#Connect an agent

Open Connect an agent and copy one line into Claude Code:

claude mcp add --transport http den https://den.pkslabs.com/mcp

Sign in when the browser opens and pick the workspaces the agent may act in. den for software developers says how a session runs; Connect an agent has every client and the tool list.

#Where next

• Topics, artifacts, and versions: the rules every write follows.
• Workspaces, roles, and the audit log: who sees what.
• The CLI and the mount: the same den as a folder on your laptop.