My Agent Tasks

My Agent Tasks is a feature in the OSC web console that lets you create and schedule automated AI agent tasks that run on your behalf. Instead of having your own machine running an AI agent on a schedule, OSC handles the execution for you in the cloud.

What You Can Do

Create tasks with a natural language prompt that the agent will execute
Choose between two agent runtimes: Claude Code (Anthropic) or Codex (OpenAI)
Schedule tasks to run automatically (every 15 minutes, hourly, daily, weekdays, weekly)
Optionally point tasks at a Git repository so the agent has access to your code
Trigger tasks manually at any time with "Run Now"
Manage tasks via the web console or MCP tools

Prerequisites

An OSC account on a paid plan (Personal, Professional, or Business)
An API key for your chosen runtime (Anthropic or OpenAI)

Agent Runtimes

OSC supports two agent runtimes. You select the runtime when configuring credentials and creating tasks.

Claude Runner (`birme-claude-runner`)

The original OSC agent runtime. Runs tasks using Claude Code CLI from Anthropic.

Supported credentials (choose one):

Credential type	Secret name	Description
Anthropic API Key	`anthropicapikey`	An `sk-ant-...` key from console.anthropic.com
Claude OAuth Token	`claudeoauthtoken`	A token obtained via Claude's OAuth flow

Best suited for: Tasks that benefit from Claude's reasoning, code generation, and OSC platform integration via MCP.

Codex Runner (`birme-codex-runner`)

A newer runtime that runs tasks using OpenAI Codex CLI.

Supported credentials:

Credential type	Secret name	Description
OpenAI API Key	`openaikey`	An `sk-...` key from platform.openai.com

Best suited for: Tasks where you prefer OpenAI models (such as o3, gpt-4.1), or workflows already built around the Codex CLI and AGENTS.md conventions.

Runtime comparison

Feature	Claude Runner	Codex Runner
AI provider	Anthropic	OpenAI
CLI	Claude Code	Codex CLI
Context file	`CLAUDE.md`	`AGENTS.md`
Default model	`claude-sonnet-4-5`	`codex-mini-latest`
Custom models	Yes (`Model` field)	Yes (`Model` field, e.g. `o3-mini`, `gpt-4.1`)
OSC MCP integration	Yes	Yes (via `OscAccessToken`)
Sandbox control	Via allowed/disallowed tools	Via `Sandbox` option
Credential types	Anthropic API key or Claude OAuth token	OpenAI API key only

Getting Started

Step 1: Navigate to My Agent Tasks

Go to My Agent Tasks in the OSC web console.

Step 2: Configure Credentials

The first time you open the page you are prompted to configure your agent credentials.

For Claude Runner, choose one of:

Anthropic API Key — an sk-ant-... key from console.anthropic.com
Claude OAuth Token — a token obtained via Claude's OAuth flow

For Codex Runner, provide:

OpenAI API Key — an sk-... key from platform.openai.com

Enter the credential and click Save. The credentials are stored securely and used to run your tasks.

Once credentials are configured, a status bar at the top of the page shows the credential type. From there you can:

Reconfigure — click to expand the setup form inline and enter new credentials
Remove — opens a confirmation modal to delete stored credentials

Step 3: Create a Task

Click Create Task and fill in:

Field	Description
Name	Short identifier for the task
Description	What the task does (optional, for your reference)
Prompt	The instruction the agent will execute
Agent Type	Runtime to use: `birme-claude-runner` (default) or `birme-codex-runner`
Source URL	Git repository URL to give the agent code context (optional)
Git Token	Personal access token for private repositories (optional, write-only)
OSC Access Token	Short-lived OSC API token for tasks that call OSC services (optional, write-only)
Schedule	When to run the task (choose a preset or enter a cron expression)

Advanced Settings (click "Advanced Settings" to expand):

Field	Description
Model	Model to use (e.g. `claude-sonnet-4-5-20250514` for Claude Runner, `o3-mini` or `gpt-4.1` for Codex Runner)
Max Turns	Maximum agent turns per run (default: `25`, Claude Runner only)
Allowed Tools	Comma-separated tool allowlist (e.g., `Read,Write,Edit`, Claude Runner only)
Disallowed Tools	Comma-separated tool blocklist (e.g., `Bash`, Claude Runner only)
Sub Path	Subdirectory within the source repository to use as the working directory

Schedule presets:

Preset	Cron expression
Every 15 minutes	`/15 * * *`
Hourly	`0 * * * *`
Daily at 9am	`0 9 * * *`
Weekdays at 9am	`0 9 * * 1-5`
Weekly Mon at 9am	`0 9 * * 1`

Click Create to save the task.

Step 4: Run or Monitor Tasks

Tasks run automatically on their schedule. You can also:

Click the Run Now button on any task to trigger it immediately
Check the Last Run and Next Run timestamps in the task table
Edit or delete a task from the actions column

Using MCP Tools

If you have an AI agent connected to OSC via MCP, you can manage agent tasks using natural language.

Setting up credentials

For Claude Runner:

Set up my agent credentials using my Anthropic API key sk-ant-...

For Codex Runner:

Set up my agent credentials using my OpenAI API key sk-... for the codex runner

The setup-agent MCP tool accepts an agentType parameter to target the correct runtime. When you specify an OpenAI key the tool sets agentType to birme-codex-runner automatically. When you specify an Anthropic key it uses birme-claude-runner.

Creating tasks

Create a task that runs with the default Claude Runner:

Create a daily task called "sync-report" that runs every weekday at 9am.
The prompt should be: Review the GitHub issues in my repo and post a summary to Slack.
Use https://github.com/myorg/myrepo as the source URL.

Create a task that runs with Codex Runner:

Create a weekly task called "code-review" that runs every Monday at 8am using the Codex runner.
The prompt should be: Review open pull requests in the repo and add triage comments.
Use https://github.com/myorg/myrepo as the source URL.
Set agentType to birme-codex-runner.

Managing tasks

List my agent tasks and show me which ones ran today.

Run my "sync-report" task now.

Delete the agent task called "old-task".

Available MCP tools

Tool	Description
`setup-agent`	Store agent credentials; accepts `agentType` (`birme-claude-runner` or `birme-codex-runner`)
`create-agent-task`	Create a scheduled agent task; accepts `agentType` to select the runtime
`list-agent-tasks`	List all tasks with schedule and last/next run timestamps
`run-agent-task`	Manually trigger an immediate task run
`delete-agent-task`	Permanently remove a task

Prompt Tips

Write prompts as clear task descriptions. The agent runs non-interactively, so treat the prompt as a complete, self-contained instruction.

Claude Runner prompts:

"Review open GitHub issues labeled 'bug' in myorg/myrepo and add a comment with a suggested fix approach."
"Check the health of my OSC services and send a Slack message to #ops if any are unhealthy."
"Fetch yesterday's analytics data from my Plausible instance and append a row to the Google Sheet at ..."
"Generate a daily standup summary from my Jira board and post it to #team-standup."

Codex Runner prompts (works best with an AGENTS.md in the repository):

"Run the daily report task described in AGENTS.md."
"Review the code in src/ for potential bugs and write a summary to review.md."
"Run the test suite and report any failures with suggested fixes."

For tasks that interact with code, set Source URL to the relevant repository so the agent can read and modify files in context.

Context Files

Each runtime uses a different conventions file to understand the project:

Claude Runner reads CLAUDE.md at the repository root (or in parent directories).
Codex Runner reads AGENTS.md at the repository root.

If you switch a repository between runtimes, add the corresponding context file so the agent has the project background it needs.