Spaces
Spaces are Huginn’s persistent conversation rooms — two types, DMs and Channels, each giving you an ongoing relationship with one or more agents that survives restarts.
Two types of Spaces
Direct Messages (DMs)
A DM is a one-on-one conversation between you and a single agent. There is exactly one DM per agent. Open the same DM tomorrow and all your history is right there.
DMs are immutable — you cannot rename, archive, or delete them. They are designed to be a permanent home for your relationship with a specific agent.
When to use a DM:
- You always go to the same agent for the same kind of work (e.g., Mark handles code review, Steve handles architecture).
- You want the simplest setup — no configuration required.
- You want every past conversation in one place.
Open a DM from the TUI:
/dm mark
From the web UI, click the agent’s name in the Direct Messages section of the left sidebar. If the DM already exists, you are taken back to it with full history intact.
Channels
A Channel is a named, multi-agent collaboration room. You pick a lead agent (the orchestrator) and up to 20 member agents (the specialists). The lead receives your messages first and can delegate subtasks to members.
When to use a Channel:
- You want multiple agents to share context on the same project.
- You need a specialist team — architect + implementor + reviewer, for example.
- You want to organize work by project or initiative rather than by individual agent.
Open a Channel from the TUI:
/channel "API Redesign"
Creating a Channel
Natural language
Just describe what you want:
create a channel called backend-team with Steve as lead and Mark and Chris as members
Huginn creates the channel and opens it immediately.
From the web UI
- Click New Channel in the sidebar.
- Give it a name (e.g., “Q2 Launch”, “API Redesign”).
- Select a lead agent — this agent orchestrates the work.
- Add member agents — the specialists the lead can call on.
- Optionally pick an icon and a hex color.
- Click Create.
Example setup
Channel: API Redesign
- Lead: Steve (architect)
- Members: Mark (code review), Chris (implementation)
When you send a message, Steve gets it first. Steve’s system prompt includes the full team roster and can delegate subtasks to Mark and Chris inside the same channel.
Via API
curl -X POST http://localhost:8421/api/v1/spaces \
-H "Content-Type: application/json" \
-d '{
"name": "Backend Refactor",
"lead_agent": "steve",
"member_agents": ["mark", "chris"],
"icon": "🔧",
"color": "#58a6ff"
}'
Workstreams
A Workstream is a named thread inside a Space. Use them when a single channel covers multiple initiatives and you want to keep sessions organized by topic.
Workstreams are like Slack threads, but for agent conversations. Creating one does not affect how agents work — it is purely an organizational layer for you.
Creating a Workstream:
- Navigate to a Space in the web UI.
- Open the Workstreams panel.
- Click New Workstream, give it a name and optional description.
- Tag sessions to it as you work.
| Action | Description |
|---|---|
| Create | Name and optional description |
| Tag session | Associate any session with the workstream (idempotent) |
| List sessions | All sessions tagged to this workstream, newest first |
| Update | Change the name or description |
| Delete | Removes the workstream — sessions are not deleted |
Memory in Channels
When any agent in a Channel stores a memory, Huginn replicates it to every other member’s personal vault automatically. This is called memory replication fan-out.
How it works:
- Mark records a decision: “Use cursor pagination for all list endpoints.”
- Huginn fans that memory out to Steve’s and Chris’s vaults.
- Each replica is tagged with provenance — which agent wrote it and which channel it came from.
- Anti-echo protection prevents replicated memories from being re-replicated.
- Failed replications retry automatically: 5s, 30s, 2m, 10m — up to 5 attempts.
Every agent on the team stays in sync without any manual copy-paste.
Note: Memory replication requires MuninnDB to be running. If you see replication failures, confirm MuninnDB is active.
DMs vs Channels — quick guide
| Situation | Use |
|---|---|
| One agent, focused work | DM |
| Multiple agents, shared project context | Channel |
| You want zero setup | DM |
| You want a team roster + delegation | Channel |
| You need to rename or customize the space | Channel (DMs are immutable) |
| You want a permanent, unarchivable record | DM |
Navigating Spaces
TUI commands:
/dm [agent-name] # Open or resume a DM
/channel [name] # Open or create a channel
Web UI:
The left sidebar shows two sections — Direct Messages and Channels. Each space shows an unseen badge when it has new activity. Click any space to open it and clear the badge.
Archived channels are hidden from the default list. You can retrieve them via the API:
GET /api/v1/spaces?archived=true
Key concepts reference
| Concept | Description |
|---|---|
| Lead agent | Orchestrates the channel. Receives your messages first. In a DM, this is always the agent you are talking to. |
| Members | Channel-only. Up to 20 agents that the lead can delegate to. |
| Unseen count | Badge showing sessions updated since you last read the space. |
| Archived | Channels can be soft-archived (hidden, not deleted). DMs cannot be archived. |
| Workstream | A named thread grouping sessions within a space by topic. |
Troubleshooting
Cannot rename or archive a DM DMs are immutable by design. Create a Channel if you need a customizable, archivable space.
Agent not found when creating a channel Check the agent name spelling on the Agents screen. Names are case-insensitive but must match exactly.
Unseen count does not update Check the WebSocket connection status indicator. Refresh the page to reconnect.
Memory replication failures Failed replications are queued and retried automatically (up to 5 times). Check that MuninnDB is running.
See also
- Named Agents — defining the agents that participate in Spaces
- The Loop — how agent delegation works
- Workflows — scheduled automation (separate from Workstreams)