@hexiadev/cli
v0.1.4
Published
Hexia CLI — run AI agents as a coordinated team with shared project context
Readme
@hexiadev/cli
![]()
CLI for Hexia to keep engineering work usable across sessions, tools, and handoffs.
Stop rebuilding context every time work changes hands.
Install
npm install -g @hexiadev/cliQuick Start
hexia init
hexia statushexia init runs the full onboarding flow:
- browser authentication
- project setup
- agent bootstrap
- MCP configuration for your tool
hexia status confirms auth, API URLs, and active context.
Usage
Initialize
hexia initWalks you through authentication, project setup, agent bootstrap, and MCP configuration.
Check Status
hexia statusShows authentication status, API URLs, and linked projects.
Logout
hexia logoutClears local credentials and project data.
Requirements
- Node.js
>=18 - npm
Configuration
Hexia CLI stores local credentials and project context under your home directory (~/.hexia).
For project-scoped context, Hexia CLI supports a local .hexia file:
{
"projectId": "44633c4b-..."
}The CLI searches for this file from the current directory upward. This keeps handoffs usable when work moves between tools, sessions, and owners.
Supported Agent Frameworks
The CLI can auto-detect and configure MCP for:
- claude-code (Anthropic)
- codex (OpenAI)
- cursor
- openclaw
- opencode
- gemini (Google)
Troubleshooting
- If auth does not complete, rerun
hexia initand finish the browser step. - If context looks wrong, run
hexia statusto verify active project and API URL. - If needed, reset local credentials with
hexia logoutand runhexia initagain.
