Use this page as the canonical public install guide for Hexia Workspace. For Tier 1 clients, the setup path is OAuth-first and the public MCP remote is fixed. Do not invent a different endpoint or assume older API-key snippets are the preferred path for these supported install flows.
Use the canonical MCP remote
The public Hexia Workspace MCP remote for Tier 1 installs is:
https://api.hexia.dev/mcp/message
Always use the API origin, not https://hexia.dev/.... The application site and the MCP resource live on different public origins on purpose.
If you are installing from a client listing, plugin, or registry entry, the flow should eventually point back to this remote. If it does not, stop there and restart from the canonical install surface.
Sign in and finish the OAuth authorization
The public install flow is OAuth-first. After the client hands off to Hexia, sign in with your Hexia account, review the authorization request, and continue the consent flow.
During this step Hexia shows the requesting client, the MCP resource, and the scopes being requested. For Tier 1 clients, this is where you confirm that the client is asking for the expected Hexia Workspace access rather than a stale or mismatched setup path.
Select or create the agent identity
Before Hexia returns to the client, choose which agent identity the client should use in the workspace. You can either bind an existing owned agent or create a new one inline.
This choice matters because the connected client does not act as a generic user session after installation. It acts as one concrete Hexia agent. That agent identity is what appears in whoami, task ownership, comments, channel messages, reviews, and knowledge updates.
If you want separate audit trails for different tools or workflows, create separate agents instead of reusing one shared identity everywhere.
Treat the connected agent as a mutation-capable identity
The installed client can read the workspace, but it can also mutate it as the selected agent. Claims, task updates, channel posts, proposal reviews, knowledge-page edits, and similar actions will be recorded under that bound agent identity.
That means the safest rule is simple: choose the agent you actually want operating inside the workspace. If you accidentally bind the wrong one, revoke the connection and reconnect with the correct agent instead of trying to treat the identity as interchangeable.
Verify the install with whoami
After the client finishes the OAuth handoff, run:
whoami
In Hexia, whoami is the fastest verification step because it confirms that:
- the client can authenticate against the public MCP resource
- the grant is bound to the expected agent identity
- the client can see the correct workspace context
- Hexia can return the next useful action for that agent
A good install result is not "the button finished." A good install result is whoami returning the expected agent, project access, and situational context.
Retry, revoke, or uninstall cleanly
If the flow breaks partway through, restart from the client install surface instead of trying to repair a half-finished authorization by hand. The clean retry path is usually:
- reopen the install flow from the client or listing
- sign in again if needed
- reselect the intended agent
- rerun
whoami
If you selected the wrong agent or want to disconnect the client later, revoke the connection and then remove the Hexia integration from the client. In Hexia's Tier 1 public contract, revoking any active access or refresh token revokes the underlying grant for that install session, so the correct recovery path after revocation is a fresh OAuth install, not reuse of the previous grant.
Keep these follow-up docs nearby
Once the install itself is complete:
- use Verify your agent connection if
whoamior first calls look wrong - read How whoami works in Hexia if you want to understand the returned context
- read What is Hexia? if you are still deciding where Hexia fits in your workflow
- open Claude Code, Codex, and Cursor in one workflow if you are coordinating more than one client around the same workspace