* feat: run starter-prompt one-shots on the composer's model Codex and OpenCode children take the model the user picked (the stored preference for warm-ups) instead of the CLI's configured default, so an OpenCode setup whose default provider has no working key still works with a free opencode/* model. Cache keys include the model. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> * feat(opencode): detect a rejected provider key Probe each signed-in OpenCode provider once per auth.json version with a tiny read-only request; on an authentication rejection hide that provider's models, mark it in the account line, and explain the fix. Settings shows harness notes whenever one is set. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> * ui: tint each starter prompt box with its own accent Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> * ui: outline starter prompt boxes instead of tinting them Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> * ui: soften the starter box outlines Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> * review: follow-up nits for model plumbing and dead-key detection Share one opencode child helper between the one-shot and the key probe, cache only definitive probe verdicts, drop the bare 401 marker, mark OpenCode not ready when no model is left, reconcile a saved composer model the harness no longer lists, seed the pre-warm model like the composer does, ignore the model in cache keys for harnesses that ignore it, and render the Settings note. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> --------- Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com>
OpenResearch
The local-first workspace for research agents and autoresearch.
Turn Claude Code,
Codex, or
OpenCode into research agents that can review
literature, develop hypotheses, run experiments, and produce research artifacts.
Get started
Download the local desktop app from openresearch.sh/download, or install the CLI on macOS or Linux:
curl -LsSf https://openresearch.sh/install.sh | sh
orx up
orx up opens the local dashboard at http://127.0.0.1:4791.
Create an account at openresearch.sh to receive email updates and use managed OpenResearch compute.
Built for research agents
| OpenResearch gives you | |
|---|---|
| Parallel exploration | Give each research direction an independent agent session and isolated git worktree. |
| Reproducible experiments | Track variants in a git-native experiment tree; every run receives an immutable archive of its recorded commit. |
| Evidence in context | Keep logs, diffs, files, results, and artifacts tied to the work that produced them. |
| Your choice of agent | Use Claude Code, Codex, or OpenCode, with the harness and model selected per session. |
| Your choice of compute | Run locally, on your own infrastructure, or with managed OpenResearch compute. |
| Local ownership | Keep projects, conversations, experiments, runs, logs, code, and artifacts on your machine. |
Autoresearch
OpenResearch can run the full loop autonomously: propose an idea, change the code, launch an experiment, inspect the evidence, and decide what to try next. Multiple agents can explore different directions in parallel while the experiment tree preserves their lineage.
Run anywhere
The same committed source snapshot can run locally, over SSH, or on Slurm, Kubernetes, Ray, Hugging Face Jobs, Modal, Tinker, and managed OpenResearch compute. Publishing the repository is not required.
Run the workspace next to remote GPUs while using the browser on your laptop:
orx up --remote user@host
SSH config aliases and custom ports are supported. The remote service binds to loopback and has no application-level authentication, so other users on that host can reach it.
CLI and agent integration
Install the OpenResearch skill into supported coding agents:
orx install-skills
Common commands:
orx projects
orx project view <project-id>
orx runs <project-id>
orx logs <run-id>
orx exp run <experiment-id>
orx discover keyword <query>
orx paper <arxiv-id-or-doi>
Run orx --help or orx <command> --help for the complete interface.
Local by default
OpenResearch runs on 127.0.0.1 with a local SQLite store. Creating a project
or launching a run does not publish your code. An
openresearch.sh account is only used for
service-owned capabilities such as organizations and managed compute.
Usage analytics
Official release builds send opt-out, coarse usage events tied to a random installation ID. They do not include code, prompts, file contents or paths, repository names, tokens, emails, or project and experiment identifiers.
orx telemetry off
orx telemetry status
orx <command> --no-telemetry
Source and development builds do not send analytics.