ONCUE / GUIDE
Connections
Bring your own model keys and service accounts. OnCue runs on infrastructure you configure and control.
Cloudflare: your deployment
Self-hosters deploy the web application and control plane in their own Cloudflare account, using Workers, Durable Objects, D1, and R2. Cloudflare credentials authorize deployment; they are separate from the model API keys connected inside OnCue.
The full stack also needs a Clerk application for authentication and a GitHub App configured for your deployment. See the self-hosting checklist and the source deployment record.
GitHub: repository access
The GitHub integration lets OnCue access authorized repositories and supports the branch and draft pull request workflow. The repositories available to a session depend on the installation permissions and the connected account.
If a repository is missing, check installation access before changing the task or retrying the agent.
Model access: the agent’s reasoning
Connect supported model access using your own API credentials. Available models and harnesses depend on the deployment configuration. The source has adapters for OpenCode, Codex, Claude Code, and Pi. OpenCode and Pi support OpenAI and Anthropic connections; Codex uses OpenAI, and Claude Code uses Anthropic. OpenCode is enabled by default. Other harnesses require deployment configuration and have differing permission behavior and validation.
Do not assume a consumer chat subscription supplies API usage. Confirm the credential type and provider billing for the model you select.
Modal: a place to execute
Modal supplies the remote sandbox where repository commands and the agent run. A successful model connection alone is not enough to start a remote coding task: compute must also be configured.
Sandbox startup, resource limits, and lifecycle are part of the execution environment. They are separate from whether your browser tab is open.
Keep credentials out of the conversation
Use the intended connection or secret configuration flow. Do not paste API keys into task messages or commit credential values into repository files. Repository configuration can declare the names of required secrets without containing their values.
See permissions for how to think about agent authority and secret disclosure.