Codex CLI
Code-focused work through your installed Codex CLI.
Your tools.
A shared direction.
Keep the agents you already use. Give them specialist roles. Bring decisions to the places where you actually see them.
01 / MANY TOOLS. ONE WORKSPACE. Choose the agent.
Choose the agent.
Shape the role.
A runtime is the connection. A preset is the specialist you make from it. Use different instructions, models, and native profiles around the same installed tool.
Claude Code
Bring your Claude Code connection into the same missions.
Hermes
Discover native profiles; stream worker output where supported.
Pi
Use your installed Pi agent through its built-in connection.
OpenCode
Route work to your configured OpenCode installation.
Leave room for the tools you haven’t met yet.
Register a custom CLI executable and argument template, or connect a chat completions API endpoint. Give that connection a reusable role in the registry.
Install and authenticate each CLI on the host before scanning. Discovery does not install tools or sign into their accounts. API-only connections generate text; file and desktop work need a suitable worker tool.
02 / STAY IN THE LOOP, OUTSIDE THE TABA decision can
A decision can
meet you where you are.
Receive approvals, blocking questions, and failed-run retries in Slack or Telegram. Add comments to steer an approval. Turn on completion updates when you want them.
- Authorized responders and current-request checks
- One applied decision across browser and messaging
- Outbound connections; no public webhook required
The host must stay running. Evidence attestations and baseline acceptance are handled in Helmweave; messaging doesn’t replace them.
ILLUSTRATIVE PREVIEW
See how messaging connects Slack, on your terms.
Use guided app setup, choose a channel or direct message, and select authorized responders. Buttons, reply forms, and approval comments bring decisions into a dedicated conversation.
A private Telegram connection.
Create a dedicated bot and pair your private chat with a one-time link. Replies are tied to the relevant request. Group approvals and arbitrary chat commands aren’t part of this connection.
03 / YOUR HOST IS THE CENTER Local control.
Local control.
Connected intelligence.
The computer where your projects live runs the agents. A browser on your desktop, tablet, or phone is another way to reach that same command center.
YOUR DEVICESDesktop · Tablet · PhoneBrowser + host access key
Your Helmweave hostProjects · agents · SQLite history
YOUR CONNECTIONSModels · audio · messagingThe providers you configure
Your operating context.
Missions, settings, conversation history, and registry data live in local SQLite storage. Provider credentials remain on the host.
The context needed to work.
Relevant task context and audio go to your chosen providers. Enabled messaging sends selected mission names, questions, commands, and completion summaries to its destination.
The same host, another screen.
Connect through a browser using the host’s network address and access key. Network microphone use requires trusted HTTPS.
The web interface, Node host, and SQLite storage target macOS, Windows, and Linux. Desktop automation depends on your worker’s tools; the built-in Hermes desktop health check currently uses CuaDriver on macOS.
Assemble your
command center.
Start with one connected agent and one project. Add specialist roles, workflow templates, and messaging as your work grows.
Get started locally