Remote coding, under one owner
Cloud Harness MCP opens an isolated repository workspace in a time-limited Docker executor for one trusted operator.
Control plane
Trusted owner
Execution plane
TTL-bound workspace
Commands, dependencies, hooks, skills, and Git metadata from a repository can execute inside the executor. The control plane stays separate from Docker authority and repository credentials.
Each service has a job. Authority moves forward only where it is required.
The owner begins with an authenticated request.
A credential-free proxy accepts the loopback route.
Request policy and MCP translation stay off the Docker socket.
Lifecycle, repository materialization, and cleanup live here.
Repository-controlled work runs non-root in a bounded workspace.
Open a credential-free HTTPS repository URL with an idempotency key. Keep the opaque workspace ID for later calls.
Use bounded file, search, command, shell, task, Git, worktree, skill, hook, and memory tools within that workspace.
Close when the work is complete. Workspace files expire after close or TTL cleanup, while durable metadata records the outcome.
Read this before use
Cloud Harness MCP is for one authenticated, trusted owner using owner-approved repositories. It is not an anonymous service, shared team sandbox, or hostile multi-tenant platform.
Read the security modelConnect Codex with an owner-provided bearer token kept in the environment, then call workspace_open with a credential-free HTTPS repository URL and fresh idempotency key.