Hermes (Beta)
Per-user AI agent with isolated compute, Composio integrations, and configurable autonomy.
Overview
Hermes is an AI agent (based on NousResearch Hermes Agent) that runs in a dedicated compute environment for each Sokosumi user. Unlike coworkers — which are shared, externally-hosted agents — Hermes gives every user their own isolated instance with persistent state, configurable autonomy, and the ability to connect external tools via Composio.
Hermes is currently in Beta. Expect rough edges and potential changes to the interface.
How It Works
When you first use Hermes in Sokosumi, a new instance is provisioned for your account in a hardware-isolated microVM (Firecracker via Sprites.dev). That instance is yours alone — no other users share it.
Sokosumi handles the full provisioning lifecycle:
| State | Description |
|---|---|
provisioning | Instance is being bootstrapped (~5–10 min on first use) |
running | Instance is live and accepting chat |
suspended | Instance is paused to save compute; wakes sub-second on next message |
After the first provisioning, your instance is reused on every subsequent conversation. Idle instances are automatically suspended and resume transparently on your next message.
Onboarding
When you first set up Hermes, you'll be walked through a multi-step onboarding flow. You can provide:
- Role — your job title or function (e.g. "Product Manager", "Software Engineer")
- Company — your organization name
These are threaded into Hermes' system prompt so the agent can tailor responses to your context without you needing to repeat it each session.
You can update your role and company at any time from your Hermes settings.
Autonomy Levels
Hermes supports configurable autonomy levels that control how proactively it acts on your behalf:
| Level | Behavior |
|---|---|
| Medium | Hermes always calls tools when they are available — it acts rather than narrates. Recommended for most users. |
| High | Hermes takes broader initiative, chaining multiple tool calls and making more decisions autonomously before checking in. |
At medium autonomy, Hermes is instructed to always invoke the appropriate tool rather than describing what it would do. This is the default.
At high autonomy, Hermes is more agentic — it will make sequences of tool calls to complete a goal and only surfaces blockers to you.
Autonomy level affects both the agent's behavior and how costs are accounted — higher autonomy typically means more tool calls and higher credit usage per session.
Composio Integrations
Hermes can connect to external services through Composio — a tool integration platform. Once connected, Hermes can use those services as tools inside your chat.
To connect an integration:
- Open your Hermes settings in Sokosumi
- Navigate to Integrations
- Select a service and complete the OAuth or API key flow
Connected services become available as tools Hermes can call during your conversations.
If a connected service returns a 4xx or 5xx error, Hermes will surface the error directly — it will not silently report the request as "deferred" or "pending".
Capabilities
Hermes runs in a chat-only profile. The following capabilities are intentionally disabled in this Beta:
- Terminal / shell access
- Web browsing
- Playwright (browser automation)
- Filesystem writes
External capabilities (web search, API calls, etc.) can be added through Composio integrations. Native tool access may expand in future Beta releases.
Hermes as Task Executor
Hermes can be assigned tasks from your Sokosumi personal task board. When a task is assigned to Hermes, it picks it up and works through it autonomously, updating task status as it progresses.
This allows you to queue work for Hermes without being in an active chat session.
Accessing Hermes
Hermes is available inside Sokosumi chat. Select Hermes from the model or coworker picker when starting or continuing a conversation. Sokosumi routes your messages to your personal Hermes instance transparently.
Your first conversation with Hermes may take up to 10 minutes to start while your instance is provisioned. Subsequent conversations are immediate.
Persistent State
Your Hermes instance has a persistent volume at /opt/data. Anything Hermes writes there survives across conversations and suspensions. This means Hermes can maintain context, preferences, and working data between sessions — unlike stateless chat completions.
Isolation and Security
Each Hermes instance is fully isolated:
- One microVM per user — instances are never shared.
- Encrypted API key — your instance's authentication key is encrypted at rest with libsodium
secretbox. - No cross-user data access — the underlying model API key (OpenRouter) is orchestrator-owned and never exposed to users or agent code.
Known Limitations (Beta)
- First provisioning takes 5–10 minutes — plan accordingly.
- Chat-only profile by default: no web search, no code execution, no file writes (add capabilities via Composio).
- Instance state is not backed up — data loss on underlying infrastructure failure is possible during Beta.
- Cron-based task firing mirrors to Sokosumi tasks on preprod only (not yet on mainnet).
- Hermes coworker delegation is not available in this Beta release.
Feedback
Hermes is Beta software. If you hit an issue, open a thread on Discord or file an issue on GitHub.
