Web UI

Huginn ships with a full web application accessible at http://localhost:8421. It’s the visual layer on top of everything Huginn does — agent management, artifact review, workflow building, and a live thread panel for watching sub-agents work in real time.

You don’t have to use it. The TUI and headless mode work without it. But the web UI makes agent configuration, automation pipelines, and artifact review significantly easier.


Starting the web UI

# Recommended: runs Huginn and adds a system tray icon
huginn tray

# Server only (no tray icon — useful in Docker or headless environments)
huginn serve

Open http://localhost:8421 in your browser. The UI is available as long as the Huginn process is running.

Network exposure

By default Huginn binds to localhost only. To expose it on your network (e.g., for accessing from another device via HuginnCloud):

// ~/.huginn/config.json
{
  "web": {
    "bind": "0.0.0.0",
    "port": 8421
  }
}

The left sidebar has a fixed 48px icon strip with the main sections:

IconSectionWhat it does
💬ChatActive sessions and new conversations
🤖AgentsCreate, edit, and configure agents
🔗ConnectionsOAuth providers, CLI integrations, MCP servers
SkillsBrowse, enable, disable, and search skills
🕐RoutinesCreate and manage scheduled agent tasks
🔀WorkflowsBuild and run multi-step automation pipelines
📥InboxResults from Routine and Workflow runs
⚙️SettingsBackend, models, config

Chat view

The Chat view is where you interact with agents. It’s similar to the TUI but adds:

  • Thread panel (right side) — when an agent delegates to a sub-agent, a panel slides in showing the sub-agent’s output streaming live. You can keep chatting with the primary agent while the sub-agent works.
  • Artifact cards — when an agent produces structured output (code files, reports, schemas), they appear as cards with Accept, Reject, and Download actions.
  • Session sidebar — a persistent list of past sessions, searchable and resumable.
  • @mentions — type @Steve to address a specific agent directly in the chat input.

Agents screen

Create, edit, and delete agents without touching JSON files. Each agent’s configuration page exposes all fields:

  • Name, role, description
  • Model and backend (override global config per-agent)
  • System prompt
  • Memory settings (mode, plasticity, vault name)
  • Skills assignment (which skills this agent loads)
  • Tool permissions (read-only, read-write, exec)
  • Color and icon

Changes take effect on the next session start.


Artifact review

When an agent produces a structured artifact (a file to write, a schema, a report), it appears as a card in the thread panel and in the session view. You can:

  • Preview the content inline
  • Accept — writes the artifact to disk
  • Reject — discards it with an optional note back to the agent
  • Download — save without writing to the project

This makes it easy to review changes before they land, especially useful when running agents in less-trusted contexts.


Workflow editor

The /workflows page gives you a visual interface for building automation pipelines without editing YAML directly:

  • Create a Workflow with a name, description, and cron schedule
  • Add steps by selecting from your existing Routines
  • Set on_failure per step
  • Pass variable overrides per step
  • Reorder steps by dragging
  • Run the Workflow immediately with Run Now
  • View per-step status breakdown in the run history

Inbox

The Inbox aggregates results from all Routine and Workflow runs. Each entry shows:

  • Routine or Workflow name and type badge
  • Timestamp
  • Full agent output
  • Per-step status breakdown (for Workflows)

Unread entries are highlighted. A live badge counter over the Inbox icon updates via WebSocket — no polling or refresh needed.


Connections screen

Manage everything that extends your agents’ capabilities:

  • OAuth providers — connect Google (Gmail, Drive, Calendar), Slack, Jira, Bitbucket
  • CLI integrations — Huginn auto-detects gh, aws, gcloud if they’re in your PATH
  • MCP servers — shows the status of any MCP servers defined in config.json

Tokens for OAuth providers are stored in your OS keychain (macOS Keychain, GNOME Secrets, Windows Credential Manager). They never leave your machine.


Screenshot

Screenshot coming soon — run huginn tray to see it now.


See also