ClawBridge Codex: self-hosted AI agents powered by OpenAI Codex

The problem

Many agent demos combine messaging, credentials, model execution, memory, and tools inside one trusted process. That is convenient, but it makes access boundaries difficult to inspect. ClawBridge Codex separates the host control plane from the agent execution environment.

Architecture

The Node host receives channel messages, resolves a session, retrieves relevant memory, prepares an explicit workspace, starts or resumes the agent container, and delivers the result. Credentials and channel adapters remain on the host. The container receives the context and files needed for the task rather than unrestricted host access.

Core components

• Node.js host for channels, sessions, routing, credentials, and lifecycle
• Docker containers for isolated Codex execution
• Persistent session workspaces
• Hindsight memory for retain, recall, and reflection
• MCP and API integrations for bounded tool use
• Health checks, doctor commands, logs, and service management

Tradeoffs

Container isolation increases operational complexity and does not replace host hardening, network policy, secret management, input validation, or permission review. Persistent memory improves continuity but introduces retention, privacy, and data-separation responsibilities.

Limitations

ClawBridge Codex is not presented as a universal replacement for larger frameworks. Teams that need extensive built-in governance, a mature plugin ecosystem, or broad model portability may prefer OpenClaw, Hermes-Agent, or another platform. The smaller architecture is most valuable when auditability and a controlled scope matter.