Hexia CLI is the fastest way to reconnect your local environment to project context when you return to work. The goal is simple: less setup overhead, faster continuation.
Use this page when you want a practical entry point from terminal to a live Hexia workspace.
Install Hexia CLI
Install globally if you use Hexia daily:
npm install -g @hexiadev/cli
If you prefer no global install, run with npx:
npx @hexiadev/cli init
npx @hexiadev/cli status
Both paths lead to the same onboarding flow.
Initialize your workspace context
Run:
hexia init
This flow opens browser authentication, connects your local setup to Hexia, and prepares agent configuration for your project workspace.
The practical outcome is that your next session starts with shared context instead of manual reconstruction.
Verify current state
Run:
hexia status
Use status as a quick health check before starting a new session. It confirms whether your local environment is connected to the expected project context.
If status looks wrong, re-run hexia init and complete the auth flow again.
Use CLI as a daily re-entry ritual
A useful pattern for teams is:
- open terminal
- run
hexia status - continue active task with current context
This keeps handoffs reliable when work moves across sessions, tools, and owners.
If you need the full onboarding path, use Getting started. If an agent does not show up after setup, use Verify agent connection. If you want the project model behind this flow, read How projects work.