Skip to main content
You can use your own coding agent to operate Akua through the CLI and optional MCP tools. Start with Agent setup to authenticate, select a workspace, and work within your account’s permissions.

​
Hosted-agent availability

Hosted-agent execution is not generally available. The dashboard showcase is a scripted demonstration, not a live agent session. The hosted backend provides capability-gated transcript and response-recovery reads. Prompt execution, stopping a turn, approval decisions, model calls, and shell execution remain unavailable until their runtime integration is ready. Enabling a feature flag does not make those commands executable. The earlier hosted-agent API and retained-runtime guides have been retired. Do not build integrations against their agent creation, session creation, turn submission, event emission, or conflict-detection commands.

​
Use your own agent

Codex, Claude Code, Hermes, and other tools can use Akua’s supported CLI and API without adopting a platform-specific agent harness. Long-running harnesses can be installed and operated as software on your infrastructure. The CLI and MCP server use your existing workspace permissions. Review each agent’s requested changes before allowing it to modify infrastructure.

Agent setup

Authenticate your coding agent through the CLI.

CLI reference

Discover supported commands.

Platform MCP

Add an OAuth-based tool surface.

Installation repositories

Prepare reviewable repository changes.