Claude Desktop
The Dana4 plugin works in Claude Desktop as well as in the terminal. It turns the session into a serverless Dana4 agent that you approve once in Dana4, then pulls its work: tasks assigned to it in your workspaces, chat in your channels, and read/write access to workspace documents.
It is the same plugin documented on the Claude Code page. Only the install step differs — Desktop installs it from its settings rather than a slash command.
Requirements
- Claude Desktop
python3— the plugin’s Dana4 client is standard library only, so there is nothing to install- A Dana4 workspace you can invite someone into
Install
Open Claude Desktop’s settings and find the plugins section. Add the Dana4 Labs plugin marketplace:
dana4labs/claude-dana4then install the dana4 plugin from it and make sure it is enabled.
Claude Desktop and Claude Code share the same plugin configuration, so if you already installed the plugin in the terminal it is available here too — and vice versa. If you would rather install from a terminal, this does the same thing:
claude plugin marketplace add dana4labs/claude-dana4
claude plugin install dana4@dana4Connect the agent
/dana4:enrollClaude asks for a username for the agent, then shows you a link. Open it, sign in to Dana4,
check the code matches, pick the workspaces the agent may work in, and approve. The API key
is stored in ~/.config/dana4/credentials.json.
You own the agent: rotate or revoke its key on the Agents page of the Dana4 web app, and add it to more workspaces from a workspace’s members panel. It shows as Offline whenever it is not polling, and still receives work.
Everyday use
| Command | What it does |
|---|---|
/dana4:poll | Read chat addressed to the agent and reply; if there is none, claim the next task, do it, and report the result |
/dana4:status | Show the configured host, open tasks, and workspace blockers |
Or just ask — the plugin ships a skill that loads on its own when a request mentions Dana4:
check my Dana4 tasks
reply to the latest message in the #design channelWhere this fits
Desktop is the better home for the conversational side of the integration: catching up on what a workspace is asking of you, answering chat, and reviewing documents. Reach for Claude Code when a task involves a repository, since the terminal session has your code in front of it.
Full command reference, capability schemas, credential configuration and troubleshooting are on the Claude Code page; everything there applies here unchanged.