BatonX CLI
Let developers use supported AI coding agents inside governed sessions. BatonX prepares the workspace, applies the effective policy and preserves a human review point before changes are accepted.
Explore the CLI workflowBatonX / Product
BatonX connects developer workflows, project context, approved models and enterprise controls in one customer-managed product.
BatonX CLI
Agent-driven changesBatonX Chat
Read-only guidanceControl Plane
LLM Gateway
Audit evidence
The experiences
Use the native coding-agent workflow for development and read-only project guidance for the wider delivery team.
Let developers use supported AI coding agents inside governed sessions. BatonX prepares the workspace, applies the effective policy and preserves a human review point before changes are accepted.
Explore the CLI workflowGive developers, analysts, QA and architects a project-specific assistant without granting write or command execution capability.
Explore project ChatThe shared foundations
Organisation-owned controls connect the two experiences. Configure the boundary centrally and keep model destinations explicit.
Define organisations, projects, repositories, providers, models and policies from one administrative experience.
Explore the Admin ConsoleRoute model access through an approved path, keep provider credentials outside the agent runtime and provide request, usage and cost metadata.
Explore integrationsCreate structured evidence for sessions, policy decisions, approvals and security events. Send standard events to customer-owned operational systems.
Explore securityApproved requests follow a governed route. Policy-denied access stops at the boundary, with decisions and access events represented in audit evidence.
One product, two governed experiences
Developers and analysts use CLI and read-only Web Chat through one BatonX control layer. Policy-approved requests continue to approved AI models; denied requests stop at the policy boundary. The control layer produces audit evidence of policy decisions and access events.
Developers
Analysts · QA
BatonX CLI
Agent-driven changes
BatonX Chat
Read-only guidance
BatonX control layer
Audit evidence
Policy decisions · access events
Approved AI models
Cloud or internal
Access blocked
Requests outside approved policy stop at the boundary.
BatonX is designed to integrate additional coding agents and compatible LLM endpoints through adapters. Agent and provider integrations can evolve while identity, policy, governed access and audit remain shared platform responsibilities.
Compatibility depends on each model’s capabilities and adapter validation. Additional integrations are an expansion direction, with support status documented individually.
Explore the adapter approachDiscuss a customer-managed pilot around your projects, supported agents and approved model endpoints.
Request a pilot