01 / ROUTE
One request.
The right host.
Choose where work belongs without turning a coordinator into the authority for host effects.
INTERFACE → CLIMAX → HOST+ INTELLIGENCE, UNDER YOUR CONTROL
Your intelligence.
Your infrastructure.
One control layer.
Bring AI agents and private machines together. Climax connects your AI interface to your hosts—with explicit permissions and execution you can trace.
IN DEVELOPMENT / PUBLIC CONCEPT · NO LIVE HOST CONNECTIONS
01 / THE CONTROL LAYERIntelligence above. Authority at the host.
ONE CORE. AN EVOLVING ECOSYSTEM.
ChatGPTPRIMARY INTERFACEπ PiNATIVE HARNESSOpenClawREFERENCE INTEGRATIONCodexPLANNEDHermesPLANNED
01 THE PLATFORM
A wider view.
A firmer grip.
One machine or a growing fleet. A personal agent or a research environment. Climax is designed to give AI interfaces a clear path to private infrastructure while each host retains final authority over what may execute.
One request.
02 / AUTHORIZE
Useful access.
Explicit boundaries.
Authenticated MCP carries scoped requests. Access can be limited by user, project, workspace and host.
IDENTITY → POLICY → EXECUTION03 / EXECUTE
Reason once.
Execute deliberately.
Pi forwards the approved invocation without a second reasoning-model call. General command and script execution remain independent of optional adapters.
APPROVED INVOCATION → NATIVE TOOL02 INTERACTIVE CONCEPT
Control should feel
understandable.
Interactive concept · All data is simulated.
Explore three views of the intended experience: connected hosts, an execution trace, and policy boundaries. The demo has no authentication, no host connections and no command execution.
>CLI_ / WORKSPACECONCEPT PREVIEW
Private hosts
A fleet view is useful only when host authority remains visible.
Hosts3
Available3
AuthorityHost-owned
atlas-01Linux · DevelopmentAVAILABLE
forge-02Linux · Agent workspace · OpenClaw referenceAVAILABLE
lab-03Linux · ResearchAVAILABLE
Execution trace
A simulated request showing where authorization, routing and host execution boundaries sit.
EXAMPLE REQUEST
Inspect the workspace and summarize current repository status.
scope: project/climax · host: atlas-01 · effect: read-only1. Request scoped
Identity and requested capability travel with the request.
2. Host selected
Climax routes without acquiring authority over the host.
3. Host admits
Local policy decides whether the invocation may execute.
4. Result returns
Execution truth comes from the selected host.
Policy boundary
An example policy view. Labels show intent; they are not a production security certification.
Read project workspaceOrdinary project filesALLOW
Run approved toolWithin host-owned policyALLOW
Elevated host mutationRequires explicit grantRESTRICTED
Unknown or stale authorityFail closedSTOP
03 UNDER THE SURFACE
Connected by design.
Controlled at the edge.
ChatGPT web/Work is the current primary interface target. Authenticated MCP carries scoped requests. Each selected host checks permissions and owns execution truth.
01 / INTERFACE
>_
Where you thinkChatGPT web / Work
Future interface adaptersAuthenticated MCP
02 / CONTROL LAYER
>CLI_
ClimaxRoute. Coordinate. Trace.
Optional fleet coordinationHost-owned admission
03 / PRIVATE COMPUTE
[_]
Your hostsPi · native tools · adapters
Final execution truthIdentity at the connection
Descope OAuth is part of the implementation boundary; live production interoperability is not claimed.
Clear recovery
If an operation may have started, establish target truth before retrying or moving on.
Coordinator without takeover
A wider fleet view can help route work without becoming the authority for host effects.
04 POSSIBILITIES
Private computing.
Broader horizons.
Designed for developers, operators, researchers and small teams that need useful agent access without giving up host-level control.
>_
Development across machines
Route repository work, builds and diagnostics to the machine that actually owns the environment.
#
Agent environments
Coordinate general execution and optional tool-specific adapters while keeping permissions explicit.
∑
Private research
Run analysis near private data and infrastructure with explicit, inspectable data flows.
05 DEVELOPMENT ROADMAP
Build the core.
Prove the boundaries.
Climax is in development. Qualification determines readiness; no public release date is committed.
Host-first core
Accepted architecture, scoped authority, deterministic Pi execution and bounded Linux integration qualification.
Qualification
Native behavior, recovery, installation and operating-system support.
Product experience
Onboarding, host and agent views, plus dedicated local and Cloudflare-hosted interfaces.
Public ecosystem
Open-source release packaging and broader compatible integrations.
Platform direction
Support is qualified per platform and capability.
LinuxInitial qualification
macOSNative qualification pending
WindowsUnder consideration
Development snapshot · September 2026. OpenClaw is a reference integration. Codex and Hermes integrations are planned. Open-source release planned; licensing and public availability will be confirmed with release.
06 GOOD QUESTIONS
A little more clarity.
Is this preview connected to real machines?+
No. This presentation uses simulated data. It does not authenticate users, connect hosts or execute commands.
Does Climax replace the host's own security and policy?+
No. Each selected host checks permissions and owns execution truth. Climax is a control layer, not a bypass around local authority.
Does data always stay on the host?+
No absolute “never leaves the host” claim is made. Requests, outputs and metadata can traverse the AI and connectivity providers you choose. The design makes those flows explicit.
Can I download and use it today?+
Not as a public supported release. Climax is in development. Core implementation and bounded qualification evidence exist, but release timing will follow qualification and packaging.
Will Climax be open source?+
Open-source release is planned. Public availability and licensing have not yet been confirmed.
THE NEXT LAYER OF PRIVATE COMPUTING