Myles AndersonandClaude Fable 5.1
8cc8fe313f
* Run coding-agent sign-in and setup commands in an embedded settings terminal Settings notes that mention a terminal command now carry a play button that runs it in place: harness sign-ins (claude auth login, codex login, agent login, opencode auth login), gh auth login, hf auth login, and the Cursor installer. The terminal follows the app theme, stays open after the command exits, and continues as the user's login shell for follow-up commands. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> * Address review: keep the settings terminal alive, size and env for the follow-up shell - Hoist the run state out of the note so a successful sign-in (which removes the note) no longer unmounts the terminal mid-session. - PTY children get the imported shell PATH/config env and a TERM. - The follow-up shell opens at the client's last reported size and only after the command actually started. - Light-theme ANSI palette for the app-themed terminal. - Non-zero exits under the shell no longer raise a toast. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> * Address round-2 review: report server failures, share the shell hand-off, drop opencode models - A command failure under the follow-up shell now writes the message to the terminal and marks the header failed; only transport failures toast. - One continue_in_shell helper serves both routes and carries OpenCode's isolated store into the shell after opencode auth login. - opencode models is no longer runnable: it would run in a different configuration than detection and mislead. - Drop the dead on_success parameter; origin check first everywhere; setup route uses the shared origin guard; tests for resize tracking and the shell query flag. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> * Address round-3 review nits Keep the success state after the shell exits, write a late shell-start error to the terminal, report sessionEnded accurately for non-shell terminals, and fix comment anchors and wording. 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,
OpenCode, or
Cursor into research agents that can review
literature, develop hypotheses, run experiments, and produce research artifacts.
macOS 11+ · Windows beta requires Git for Windows
Get started
Install the CLI on macOS or Linux, then launch OpenResearch:
curl -LsSf https://openresearch.sh/install.sh | sh
orx up
On Windows, use the beta download above after installing Git for Windows.
orx up opens the local dashboard at http://127.0.0.1:4791.
Connect a local model to use LM Studio, oMLX, Ollama, or a custom endpoint with OpenCode.
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, OpenCode, or Cursor, 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.