EKKOLearnAI/ekko-studio

Ekko Studio 中文

A local-first AI workspace for multi-agent chat, coding, and visual workflows.
Available as a desktop app and self-hosted web console, with support for
Hermes Agent, Ekko Agent, and 14 coding-agent integrations, including Claude Code and Codex.
Bring conversations, group collaboration, voice, files, and devices together in one place.

Download Ekko Studio Desktop · Documentation · npm install -g ekko-studio && ekko-studio-web start

Ekko Studio was previously named Hermes Studio / Hermes Web UI. The GitHub repository is EKKOLearnAI/ekko-studio. The primary npm package is ekko-studio, with the ekko-studio-web command. The legacy hermes-web-ui package and command remain supported and receive the same releases.

Captured from the v0.7.33 client on 2026-10-10. Chat, workflows, and Skills use demo data; Agent versions reflect a local installation. See capture notes.

Visual workflows	Agent Manager
Connect agent steps and add a human approval gate.	Manage agent installations, settings, and updates in one place.

Single chat, group chat, and workflows share the same Agent catalog. Coding agents run on the machine hosting the Studio backend; their CLI must be installed there.

Scoped mode uses isolated session configuration; supported runtimes can use the selected Studio provider/model. Global mode uses the CLI's existing configuration and sign-in. Available models, tools, and context controls depend on the runtime. See native coding agents, Antigravity CLI, and DSH setup for details.

• Start a conversation from responsive Agent cards; Ekko is the initial default, and Studio remembers the last agent, model, workspace, launch mode, and reasoning options
• Real-time chat streaming over Socket.IO /chat-run; Studio dispatches each run to the selected runtime adapter
• Multi-session management — create, rename, delete, switch between sessions
• Self-built session database — local SQLite storage for Studio sessions; Hermes state.db remains a read-only source for Hermes history APIs
• Session grouping by source (Telegram, Discord, Slack, etc.) with collapsible accordion
• Active session indicator — live sessions pin to top with spinner icon
• Sessions sorted by latest message time
• Markdown rendering with syntax highlighting and code copy
• Tool call detail expansion (arguments / result)
• Profile-scoped file uploads, clipboard image/file paste, and workspace attachments
• File download support — download uploaded files and agent-generated files by resolved path across local, Docker, SSH, and Singularity backends
• Inline previews for generated HTML, PDF, DOCX, PPTX, XLSX, CSV, images, Markdown, and source files
• Session search — Ctrl+K search across the Studio local session database; read-only Hermes history sessions are not included
• Session categories, message references, compression progress, and durable background delegation results
• Persistent task cards with live step progress, approval prompts, and clarification questions
• Profile-aware model selector with runtime-specific provider/model availability
• Per-turn token usage, cache hits, estimated cost, and generation speed; supported runtimes also expose context usage and compression controls

Unified configuration for 10 platforms in one page:

• Credentials and channel behavior settings write to .env and config.yaml under the selected Hermes profile
• Per-platform configured/unconfigured status detection
• Gateway autostart is opt-in under Hermes settings; ordinary Studio chat does not require a platform Gateway

• Total token usage breakdown (input / output)
• Session count with daily average
• Estimated cost tracking & cache hit rate
• Model usage distribution chart
• 30-day daily trend (bar chart + data table)

• Create, edit, pause, resume, delete cron jobs
• Trigger immediate execution
• Cron expression quick presets

• Profile-aware Kanban board for planning and tracking agent work
• Task creation, updates, and status movement from the dashboard
• Uses the Hermes Kanban CLI and its task storage, with Studio authentication and profile access controls

• Vue Flow canvas for the supported Agent catalog, with file/image attachments and runtime-specific launch settings
• Directed edges, structured conditions, success/failure routes, loops, and approval gates
• Import/export for portable workflow definitions and profile-aware workspaces
• Run budgets, deadlines, stop/rerun controls, and persisted execution history
• Frozen run snapshots, node conversations, edge decisions, and evidence playback on the canvas

• Auto-discover models from credential pool (~/.hermes/auth.json)
• Fetch available models from each provider endpoint (/v1/models)
• Add, update, and delete providers (preset and custom OpenAI-compatible)
• OAuth/device flows for OpenAI Codex, Nous Portal, xAI, Claude, and GitHub Copilot
• Provider URL auto-detection for non-v1 API versions (e.g. /v4)
• Provider-level model grouping, visible-model controls, aliases, refresh, and default switching
• Separate STT and TTS provider catalogs under Models

• Create, rename, delete, and switch between Hermes profiles
• Clone existing profile or import from archive (.tar.gz)
• Export profile for backup or sharing
• Profile-scoped configuration, cache, uploads, sessions, jobs, usage, memory, skills, plugins, providers, and model visibility
• Account-bound profile access: super administrators can manage every profile; regular administrators only see and use profiles assigned to their account

• Browse files on remote backends (local, Docker, SSH, Singularity)
• Upload, download, rename, copy, move, and delete files
• Store uploaded files under the selected/requested Hermes profile while keeping downloads path-based for agent-generated artifacts outside the upload directory
• Create directories
• Preview and edit supported files with syntax highlighting, then attach workspace files back to a chat

• Multi-agent chat rooms with real-time messaging via Socket.IO
• @mention routing — mention an agent to trigger a contextual reply
• Context compression — automatic conversation summarization when history exceeds token threshold
• Typing status and reply progress indicators
• Room creation, deletion, and invite code management
• Agent management — add/remove agents from rooms with per-agent profiles
• SQLite message persistence
• Mobile responsive with collapsible sidebar

• Detect, configure, launch, and monitor the 14 coding-agent integrations listed above; install and update supported CLIs from Agent Manager
• Built-in coding-agent terminal, session history, workspace selection, images, and file diffs
• Dedicated proxy routes and API modes for provider/model compatibility
• Standalone desktop chat windows and persisted output/reasoning metadata
• Shared ~/.agents/skills entries are read-only in Coding Agent pages; runtime-specific settings, private skills, and MCP controls vary by agent

• Use DSH in single chats, group-chat rooms, and workflow nodes, with Studio-selected providers/models or native global configuration.
• Select an Agent preset when creating a chat, adding a group member, or configuring a workflow node; resumed conversations retain their selected preset.
• Reuse the native web profile’s plugins. Plugin configuration embeds the plugins’ own settings UI with light/dark theme support; Plugin list manages installed packages. Agent presets have a separate Studio management page.
• Manage DSH settings, instructions, MCP, and private skills. Shared ~/.agents/skills entries are display-only in every Coding Agent page; editing and deletion are blocked.

Install DSH on the machine running the Studio backend through Agent Manager. Native plugin installation requires pnpm on that machine’s PATH. See DSH setup, profiles, and compatibility for details.

• Desktop-only multi-tab browser that agents can navigate through the managed MCP server
• Isolated browser profiles, per-tab control leases, proxy settings, downloads, cookies, and permissions
• Accessibility snapshots, screenshots, console logs, and page annotations for agent-assisted browsing
• Bounded page queries and sequential action batches, with observations of changed text, selected values, and newly opened tabs

• Connect the App over LAN, authenticated direct transport, or cloud relay, with relay fallback when a direct connection is unavailable
• Follow single-chat, group-chat, and workflow progress through task cards and notifications; supported iOS builds also show Live Activities
• Share a single conversation with an App account, configure its input/file/voice/terminal permissions, and revoke access
• Use persistent terminal sessions from the App

See App connectivity and session sharing for setup and permission boundaries.

• Profile-scoped evaluation settings for memory recall, skill matching, and learning
• Optional browser-action, group-chat, and workflow assessments with independent controls

See JEV configuration and integration status.

• Browse and search installed skills
• View skill details and attached files
• Install and manage Skill Bundles with profile-aware usage statistics
• User notes, persistent Ekko Agent memory, and profile-scoped memory management
• Interactive Journey graph for skill/memory relationships, category filtering, detail inspection, and playback

• Light/dark mode, interface style, base font size, text color, and active color
• Per-account background images and live preview across the workspace

• View agent / server / error logs
• Filter by log level, log file, and keyword
• Structured log parsing with HTTP access log highlighting

• Device and LAN peer views for local-network discovery and peer tooling
• MCP manager for the managed ekko-studio-* servers, profile injection, and api / browser / devices / use / plan toolsets; task plans and clarification use the dedicated ekko-studio-interaction server
• Runtime version and version-preview tooling for testing newer builds in isolation
• Performance monitor views for super administrators

• Token-based auth (auto-generated on first run or set via AUTH_TOKEN env var)
• Username/password login with account management in Settings
• Default bootstrap credentials are admin / 123456; users are prompted after login to change the default username and password
• Super administrators can manage users and profile bindings; regular administrators can manage their own account details

CLI maintenance commands:

# Delete persisted login IP lock records
ekko-studio-web clear-login-locks

# Delete login locks and restart the running Studio server
ekko-studio-web clear-login-locks --restart

# Create or reset the default super administrator login to admin / 123456
ekko-studio-web reset-default-login

clear-login-locks removes ${HERMES_WEB_UI_HOME:-~/.hermes-web-ui}/.login-lock.json. If the server is running, restart it to clear in-memory lock state. reset-default-login updates the Studio account database; if an admin user already exists, its password is reset to 123456 and the account is enabled as a super administrator.

• Display (streaming, compact mode, reasoning, cost display)
• Agent (max turns, timeout, tool enforcement)
• Memory (enable/disable, char limits)
• Session reset (idle timeout, scheduled reset)
• Privacy (PII redaction)
• Model settings (default model & provider)
• Profile and provider configuration

• Manage voice providers under Models → STT and Models → TTS; existing Settings → Voice links redirect there.
• TTS adapters: Edge, OpenAI-compatible, MiMo, Doubao, ElevenLabs, Gemini, xAI, Mistral, MiniMax, and DeepInfra.
• STT adapters: Browser, OpenAI-compatible, Doubao, Groq, Mistral, xAI, ElevenLabs, and DeepInfra.
• Use editable turn-based voice input from the chat mic, or open the full-screen real-time voice stage for a continuous voice-focused experience.
• Provider keys and MiMo voice-clone audio stay server-side; the browser receives only masked secret status.
• Starting a new voice turn stops current assistant playback first, but does not implicitly cancel an active agent run.
• For supported settings, security notes, and current non-goals, see docs/voice-dialogue.md.
• The real-time stage does not claim simultaneous full-duplex listen/speak; telephony and always-on wake-word listening remain out of scope.

• Integrated terminal powered by node-pty and @xterm/xterm
• Multi-session support — create, switch between, and close terminal sessions
• Real-time keyboard input and PTY output streaming via WebSocket
• Window resize support

• Native Electron shell for Windows, macOS, and Linux
• Bundles the Studio runtime and starts the local server automatically
• Capture a screen region, annotate it, and attach it to single or group chat; configure an optional global screenshot shortcut
• Hide Studio during capture on supported Windows/macOS setups; Linux capture uses X11 or the system Screenshot Portal according to the desktop environment
• Uses Cloudflare download endpoints for desktop auto-update metadata and assets first
• Falls back to GitHub Releases latest assets if the Cloudflare update feed is unavailable
• Windows upgrades attempt to close an existing Ekko Studio process before replacing files

Download the latest Ekko Studio desktop installer from GitHub Releases.

Desktop builds are published for macOS, Windows, and Linux, with separate architecture assets where applicable. The desktop app bundles the Studio runtime and stores Hermes Agent data in ~/.hermes on Windows, macOS, and Linux.

The desktop wrapper stores its own Studio state separately in ~/.hermes-web-ui unless HERMES_WEB_UI_HOME is set.

After the packaged desktop app starts, it installs managed command shims so the desktop app, bundled Hermes Agent CLI, and bundled server CLI do not conflict:

The desktop command is ekko-studio; the previous managed hermes-studio command is removed when the new shim is installed. No compatibility alias is created.

Use ekko-studio cli -h for Hermes Agent CLI help and ekko-studio web -h for server CLI help. ekko-studio-mcp defaults to the api toolset; choose browser, devices, use, or plan to keep the exposed MCP surface focused on the current task.

Desktop auto-updates read the latest feed from https://download.ekkolearnai.com/latest first. If that endpoint is unavailable, the updater falls back to https://github.com/EKKOLearnAI/ekko-studio/releases/latest/download.

npm install -g ekko-studio
ekko-studio-web start

The legacy package hermes-web-ui continues to receive the same releases. Both packages expose ekko-studio-web and the existing commands. Install either package; their global command aliases overlap. To switch, uninstall the old package before installing the other. User data remains in ~/.hermes-web-ui.

Open http://localhost:8648

Requires Node.js 23 or newer. Ekko Agent is included; to use Hermes Agent, install its runtime on the same machine or use the bundled Desktop/Docker distribution.

Single-container deployment with integrated Hermes Agent:

# Use pre-built image (Recommended)
WEBUI_IMAGE=ekkoye8888/hermes-web-ui docker compose up -d

# Or build from source
docker compose up -d --build

docker compose logs -f hermes-webui

Open http://localhost:6060

• Persistent Hermes data is stored in ./hermes_data
• Studio auth token is stored in ./hermes_data/hermes-web-ui/.token
• On first run with auth enabled, the token is printed to container logs
• All runtime settings are environment-variable driven in docker-compose.yml

For detailed notes and troubleshooting, see docs/docker.md.

When Studio starts backend chat features, it prefers a source checkout that contains run_agent.py such as ~/.hermes/hermes-agent. If no source checkout is found, it falls back to the Python environment used by the installed hermes command, then the system Python. This supports both source installs and package installs such as pip install hermes-agent.

These variables configure Ekko Studio, its local Hermes runtime integration, and development/preview helpers. Provider API keys and Hermes Agent settings are normally managed through Hermes profiles; environment variables here are process-level overrides.

hermes-web-ui remains an alias for the ekko-studio-web commands below.

Add --no-open to start or client when no browser should open.

restart, update, and upgrade stop the Agent Bridge broker by default so restarted or updated servers do not reuse stale Python bridge processes. Set HERMES_AGENT_BRIDGE_STOP_ON_SHUTDOWN=0 before restarting only when you explicitly want to keep the bridge broker and running bridge sessions alive.

update / upgrade first attempt npm cache clean --force, then install the latest version of the running package (ekko-studio@latest or hermes-web-ui@latest) and restart that package. The Web UI version check uses the same package identity. Cache cleanup is best-effort; if it fails, the updater continues with the install.

On startup the BFF server automatically:

• Initializes Studio data directories, local databases, and bundled skills
• Starts the Hermes agent bridge when a Hermes runtime is available; Gateway autostart follows the opt-in Hermes setting
• Opens a browser on successful startup unless --no-open is set

git clone https://github.com/EKKOLearnAI/ekko-studio.git
cd ekko-studio
npm install
npm run dev

• Frontend: http://localhost:8649
• BFF Server: http://localhost:8647

npm run harness:check
npm run test
npm run build   # outputs to dist/

See DEVELOPMENT.md for contributor commands and ARCHITECTURE.md for the complete package and state model.

Browser / Desktop / App
          │ HTTP + Socket.IO
          ▼
Koa bootstrap (composition only)
          │
          ├─ Studio platform ── chat, groups, global agent, workflows,
          │                    sessions, files, voice, devices, webhooks
          ├─ Hermes family ─── profiles, models, skills, memory, jobs,
          │                    Kanban, channels, terminal, Hermes bridge
          ├─ Ekko family ───── Ekko runtime and agent-owned services
          └─ Coding family ─── coding-agent adapters, scoped config, native CLI execution

The server is organized by business ownership under packages/server/src/modules/{studio,hermes,ekko,coding-agents}. Routes stay thin, controllers own HTTP concerns, services own reusable behavior, and only packages/server/src/bootstrap may compose concrete modules and adapters. Cross-agent code belongs to Studio; an agent module must not absorb a shared product surface merely because it uses that agent today.

Studio state and Hermes Agent state remain separate. Studio defaults to ~/.hermes-web-ui; Hermes profile data remains under the Hermes home. For the full ownership tree, dependency rules, and API migration contract, see docs/harness/server-module-boundaries.md.

Frontend: Vue 3 + TypeScript + Vite + Naive UI + Pinia + Vue Router + vue-i18n + SCSS + markdown-it + highlight.js

Backend: Koa 2 + Socket.IO + SQLite + node-pty

BSL-1.1

The license covers Ekko Studio, the hermes-web-ui npm package and CLI, desktop applications, firmware, release artifacts, documentation, and associated files in this repository.

The MCP entry point is bin/ekko-studio-mcp.mjs; tools use the ekko_studio_* prefix. Existing hermes-studio-mcp / hermes-web-ui-mcp commands and hermes_studio_* calls remain compatible. Restart the MCP client to discover the new tool names. Studio migrates managed server configurations to ekko-studio-api, ekko-studio-browser, ekko-studio-devices, ekko-studio-use, and ekko-studio-interaction.