Start hosted, or integrate external runtimes where your team already works.

Atellagent is self-serve through hosted workspaces with no customer runtime integration required. Atellagent Client integrates customer-operated runtimes and includes supported local-agent hooks for teams operating Codex, Claude Code, or Gemini CLI.

Hosted path

No runtime integration to begin.

Use a hosted workspace for governed coding conversations and workflows. Governance is built into this execution path rather than added through a hook.

What you bring

Your team and your work

Create an organization, enter the workspace, select the configured model/provider path, and work in a hosted environment.

What Atellagent provides

A governed execution environment

Policy, control decisions, evidence, and hosted execution surfaces are available without installing a local runtime adapter.

External agent hosts

Supported coverage, by host lifecycle.

Atellagent Client connects the documented prompt, model-input, and tool-call lifecycle events available in each host.

HostPrompt or model-input boundaryTool-call boundaryObserve / enforce
CodexUser prompt submissionDocumented supported tool hooksAt configured supported events
Claude CodeUser prompt submissionDocumented supported tool hooksAt configured supported events
Gemini CLIBefore-modelBefore-toolAt configured supported events

A malformed response, timeout, or unavailable control service causes the client to deny the governed operation rather than silently allow it.

Action discovery

Use native guardrails while you connect governed systems.

Supported hooks show the actions an existing agent attempts and record central decision evidence. They provide runtime enforcement and coverage gaps; governed MCP and hosted runtimes provide the typed action contracts for rich policy.

External client quick start

Make the host boundary explicit, then choose its posture.

1. Select the host

Choose a documented hook surface

Confirm the specific Codex, Claude Code, or Gemini CLI lifecycle events that apply to the work you want to govern.

2. Configure and discover

Enable hooks and inventory actions

Use the client and host-hook documentation to establish runtime enforcement, then observe the action surface produced by real work.

3. Enforce native coverage

Block unrecognized native actions

In Enforce mode, require a reviewed native action profile before an action can receive a generic allowance. Connect consequential systems through governed MCP for typed conditions and release controls.

Customer-owned runtimes

Bring your own runtime through an SDK, bridge, or adapter.

Atellagent Client supports documented customer-operated integrations for your runtime or target, so you can connect your existing execution path to the same policy and evidence lifecycle.

Review the client and setup guide.

Read the published client setup before selecting an external integration path.