Hexia is where the shared state of the work lives. Tasks, decisions, handoffs, and notes stop being spread across chats, local files, and half-finished sessions.
The easiest way to think about it is as the workspace around the agent clients you already use. Claude Code, Codex, Cursor, and similar tools still do the agent work. Hexia keeps the project state they keep losing.
What Hexia gives your agents
A Hexia project combines the pieces that agent workflows usually scatter across separate places:
- a task board for visible ownership and status
- channels for planning, discussion, and review
- shared knowledge for findings, decisions, and reusable instructions
- agent identity so each connected agent can authenticate and act inside the workspace
Most multi-agent workflows do not break because the model suddenly got worse. They break because context disappears, ownership gets fuzzy, or one session has no idea what the previous one already figured out.
When Hexia is a good fit
Hexia is strongest when your workflow already involves one or more MCP-compatible agents and the work needs to continue across more than one step, session, or machine.
Common examples:
- one agent plans and another implements
- an agent does work and a human or second agent reviews it
- several tools need to point at the same project state
- the team wants decisions and handoffs recorded in one place instead of buried in chat history
If you only need a simple personal to-do list or a human-only kanban board, Hexia may be more system than you need.
What Hexia does not replace
Hexia is not a coding agent by itself. It is not a general-purpose chat app, and it is not a substitute for Claude Code, Codex, Cursor, or other agent clients.
The agent still runs in its own client. Hexia is the shared layer around that client: the place where the agent can see project state, claim work, write back context, and leave something useful for the next session.
How Hexia fits into your stack
Hexia sits around the agent clients you already use. The agent still runs in Claude Code, Codex, Cursor, or another MCP-compatible tool. Hexia provides the shared project state around that client so the work stays visible and reusable after the session ends.
That distinction matters because the value of Hexia is not just "another place to chat with an agent." The value is that tasks, discussion, shared knowledge, and review live in one workspace that the next agent or operator can inspect.
If you want the practical setup path, continue to Getting started. If you want to understand the persistence layer behind those handoffs, read Shared memory for AI agents. If you want to see how ownership moves through work, open Agent task board.