Open agentic runtime

The open
agentic runtime.

Build persistent agents locally, connect the tools they need, and run the same agent anywhere with durable sessions and isolated workspaces.

Start building

Agent starters

Choose what to run.

Use a starter prompt to let Codex build the agent in your workspace, connect its tools, and launch its first Blue session.

Email triage

M B

Summarize your inbox, surface messages that need replies, and leave every action under your control.

Meeting recaps

F C M

Turn meeting transcripts into decisions, assigned actions, and concise follow-up emails.

Customer support

M N

Triage incoming issues, draft grounded responses, and escalate the conversations that need a person.

Daily briefing

31 M A

Start each day with the schedule, important messages, open work, and decisions that need attention.

Slack reply nudges

S T

Notice important mentions that have gone unanswered and send a private reminder with context.

Friday inbox cleanup

M O

Archive low-value mail, flag unfinished threads, and prepare a final list of replies before the weekend.

Ready starter

Build Email Triage

Give this prompt to Codex, Claude Code, or OpenCode from the directory where you want the agent. It will scaffold the files, connect Gmail, start Blue, and run the first session.

Agent prompt
Build and run a local Email Triage agent with Blue in this workspace.

Use the @opencomputer/blue CLI and make the result a normal Blue agent repository that I can inspect, edit, test, and deploy.

1. Verify Node.js 22 or newer is available.
2. Install or update to the current Blue CLI:
   npm install --global @opencomputer/blue@latest
3. Create an agent named email-triage unless this directory is already a Blue agent:
   blue init email-triage
4. From the agent directory, add the Gmail tools:
   blue tools add gmail
5. Rewrite agent/instructions.md so the agent:
   - summarizes recent inbox messages;
   - groups them into urgent, needs reply, informational, and low priority;
   - recommends a next action for every important message;
   - never modifies labels or sends mail without explicit confirmation.
6. Review the generated Gmail tool and Blue configuration. Keep the OpenCode harness and the default OpenRouter model.
7. Connect my Gmail account locally:
   blue connect google
   Let me complete the managed connection in the browser when Blue asks. Never print or commit credentials.
8. Start the agent with:
   blue dev
   Keep this process running and wait until Blue reports that the runtime is ready.
9. Find the exact tokenized URL printed on the line that starts with "web:". Open that local management URL in my browser so I can test the agent myself. Preserve the full #token value, never expose it publicly, and show me a clickable URL if browser opening is unavailable.
10. In the Blue management UI, have me create the first session with this prompt:
    Triage my latest 20 inbox emails. Summarize what matters, identify anything that needs a reply, and recommend next actions. Do not modify or send anything.
11. Keep blue dev running while I test. Tell me which files you created and how to return to this agent later.

Work through recoverable setup issues yourself. Stop only when I need to complete an OAuth or account authorization step.