AGENTS ON YOUR CUE.

Put your next coding
task in motion.

Your harness. Your models. Your infrastructure.
One workspace to hand off coding tasks
and bring the work back for review.

01

From a task to a change
you can review.

Give the agent a clear task. Follow the work as it happens. Come back to the conversation, the diff, and the checks.

ONCUE / IN MOTION01
Video coming soon
A task, from first prompt to final reviewVIDEO PLACEHOLDER
YOUR CUE. ITS WORKSPACE. YOUR CALL.Explore the workflow

02

Bring your own.
Make it your OnCue.

Start with the harness you want to use. Connect your models, run on Modal, and host the control plane yourself.

Choose the agent. Keep the workspace.

OpenCode, Codex, Claude Code, or Pi. OnCue gives different coding harnesses the same place to work: a remote sandbox, a conversation, and changes you can review.

Explore harness compatibility

OpenCode is enabled by default. Other harnesses are enabled in your deployment; model compatibility and permission features vary.

ONCUE / IN MOTION01
Video coming soon
Choosing a harness and starting a sessionVIDEO PLACEHOLDER

Your models. Your API keys.

Connect your OpenAI or Anthropic API keys and choose from the models supported by your harness. Model access stays in your accounts, with usage billed by the provider.

Read about model connections

The current integration supports OpenAI and Anthropic. Available models depend on the catalog and harness; a chat subscription is not an API credential.

ONCUE / IN MOTION02
Video coming soon
Connecting model keys and choosing a modelVIDEO PLACEHOLDER

Room to run. In your cloud.

The agent works in a Modal sandbox, separate from your browser. Bring your Modal workspace and token pair; OnCue coordinates the session while your compute account runs the task.

Understand remote compute

Self-hosting also requires deploying the sandbox controller. Compute usage and lifecycle limits belong to your Modal setup.

ONCUE / IN MOTION03
Video coming soon
Configuring Modal and opening a remote workspaceVIDEO PLACEHOLDER

Your infrastructure. End to end.

OnCue deploys to your own Cloudflare account as a single Worker. It serves the app, the API, and the live connection to each session. A Durable Object keeps every session’s thread, D1 holds your data, and R2 stores artifacts.

Read the self-hosting checklist

You also create a GitHub App and a Clerk application for your deployment. Deploying uses a Cloudflare API token or a Wrangler login, not a key entered into a chat.

ONCUE / IN MOTION04
Video coming soon
Setting up your own OnCue deploymentVIDEO PLACEHOLDER

STANDING BY.

Ready on your cue.

Choose your stack. Give the work a direction.