Skip to main content

1. Create a project

From the Managed Research dashboard, click New project. Set a name, timezone, and initial budget cap.

2. Complete onboarding

The Start run button stays disabled until onboarding is complete. Open the Onboarding tab and work through the four steps:Step 1: Project basics — Name, timezone, schedule window (at New project).Step 2: Connect GitHub — OAuth or PAT with repo scope. Workers use this to clone and push. Optional; you can skip.Step 3: Starting data & spec — Upload datasets, example traces, or other references the agents should use. Write the project spec describing what agents should research.Step 4: Budgets — Set a monthly cap and per-run cap. Both are hard stops — when hit the run stops with stop_reason: budget_exhausted. Set the timebox (max run duration) to cap how long a run can execute.Click Run checks to run the dry-run validation. When it passes, onboarding is complete.

3. Trigger a run

Click Start run from the project dashboard. You can optionally override the agent model (gpt-5.2 is the default), timebox (max run duration), and schedule.The run moves through:
queued → planning → executing → [blocked] → finalizing → done
                                                        ↘ failed / stopped

4. Monitor

  • Orchestrator statusrunning, idle, or unhealthy (heartbeat > 5 min stale)
  • Worker tasks table — one row per task with state and last heartbeat
If a worker needs approval before an action (e.g. pushing a PR), the run moves to blocked. Approve or deny from the dashboard.

5. Inspect outputs

When the run reaches done, open the Deliverables tab:
Artifact typeContents
report_mdMarkdown report authored by workers — rendered first
github_prPull requests opened on your repo(s) — links with status
Result filesAny other artifacts workers produced — downloadable

6. Check spend

The Usage tab shows MTD spend by provider and funding source, per-run history, and budget remaining.