Myles AndersonandClaude Opus 4.8
e53a84d3be
* Consolidate composer controls behind a settings switch icon Move Mode, Model, Reasoning, and Literature sources out of the composer bar and into a single popover opened by the switch icon. The bar now shows just the switch, attach, context meter, and send. - Nested pickers open as right-side flyouts so they never clip or overlap the panel's own rows. - Literature sources render inline (no extra click) and are cached across opens so reopening the panel doesn't flash "Loading…". - Unify hover styles across all composer controls: a shared surface-fill that fades in over 150ms with matching radius; the attach icon is the same text color as the others and no longer shifts color on hover. - Keep the model label on one line (no wrap) and align every row's chevron. Rebuilds the embedded ui/dist. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> * Move model picker to the composer bar with a harness logo Take the model picker out of the settings popover and place it back on the bar's right side, next to the context-window meter. Its menu opens right-aligned again so it doesn't run off the edge. - Show the in-use harness's brand mark on the model-picker trigger. The onboarding agent-card logos are extracted into a shared HarnessLogo component (single source of truth) that both call sites use. - Rename the settings "Mode" row and its dropdown header to "Permissions". Rebuilds the embedded ui/dist. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> * Re-implement composer settings popover in Tailwind Rebuild the composer redesign against the new inline-Tailwind UI (the prior CSS-file implementation was obsoleted by the styles.css → Tailwind migration merged from main). - Permissions, Reasoning, and Literature sources live behind the switch icon in a settings popover; nested pickers open as right-side flyouts via arbitrary-variant overrides on the panel; sources render inline. - Model picker stays on the bar's right and shows the in-use harness's brand mark; the onboarding agent logos are extracted into a shared HarnessLogo component. - Unify hover across all composer controls (switch, attach, pills, bare, context meter): a surface fill that fades in over 150ms; the attach icon matches the others' color and no longer shifts color on hover. Rebuilds the embedded ui/dist. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
OpenResearch CLI (orx)
Important
If you are an OpenResearch user or someone who is interested in autoresearch, we'd love to chat with you. Please email contact@alphaxiv.org if interested.
Stay updated or use OpenResearch compute
To receive email updates about the OpenResearch CLI or spin up compute from OpenResearch, create an account at openresearch.sh.
Run autoresearch on your machine
- Run research agents in parallel. Spins up agents in different worktrees so you can investigate several different directions at once.
- Works with Claude Code, Codex, and OpenCode
- Bring your own compute. Works with SSH, Slurm, Kubernetes, Modal, HuggingFace and more.
- Give it a goal. Can run the entire autoresearch loop from literature review to experiment analysis.
- Local and private. Your code and your data stays on your machine.
https://github.com/user-attachments/assets/33b62182-0795-490d-9366-0fb0b4bd49fd
Quick start
curl -LsSf https://openresearch.sh/install.sh | sh
orx up
The dashboard opens at http://127.0.0.1:4791. Give the agent a goal — for
example, ask it to reproduce a paper:
/reproduce-paper <paper URL or title> on <compute>
or turn one into an interactive marimo notebook:
/paper-to-marimo <paper URL or title> on <compute>
The dashboard
orx up runs a single local process on 127.0.0.1 — an embedded web UI plus a
JSON/SSE API over a local SQLite store. From there you get:
- Agent chat — a research assistant with full project context, backed by your locally installed harness: Claude Code, Codex, or OpenCode (pick the harness and model in the UI). Ask it to analyze runs, dig into results, edit code, and spin up new experiments.
- The experiment tree — every experiment is a git branch: a runnable snapshot of your code. The root is your baseline; children are variants measured against it, so lineage stays explicit.
- Runs — projects and experiments stay local by default and run on this machine from their recorded Git commit. Enable GitHub syncing for a project when you want Modal, Hugging Face Jobs, Kubernetes, Slurm, SSH, Ray, or OpenResearch compute; remote launches push the exact branch first.
- Autoresearch — describe a goal and let the agent run autonomously toward it: proposing, launching, and analyzing experiments.
Everything binds to loopback only. Creating a local project does not call GitHub; public paper repositories and paper search use the network only when you choose those flows.
On a remote machine
Develop from your laptop while the dashboard runs next to your GPUs:
orx up --remote user@host # or an ~/.ssh/config alias; append :PORT for a custom SSH port
This starts orx up on the remote box over SSH, tunnels the port back, and
opens your browser locally. Note the remote server is unauthenticated on that
host's loopback, so other users on the same box can reach it.
Commands
Run orx --help (or orx <command> --help) for full usage. The highlights:
| Area | Commands |
|---|---|
| Dashboard | up |
| Auth | login, logout |
| Projects | projects, explore, project, create-project, env |
| Experiments | experiments, create-experiment, exp status/cmd/run/cancel |
| Runs & evidence | runs, logs, search-logs, artifacts, artifact, wandb, query, chart, report |
| Compute | compute, instance create |
| Literature | lit, paper (full-text search across alphaXiv, OpenAlex, bioRxiv — no login required) |
| Agent integration | install-skills, skill |
| Maintenance | version, update, telemetry, delete database/cli/all |
orx install-skills drops the OpenResearch skill into your local coding agents
(Claude Code, Codex, OpenCode, Cursor) so they can drive orx themselves —
orx login offers this too.
Installing
The install script above fetches the latest prebuilt release (macOS and Linux, x86_64 and arm64) and is the same as:
curl -LsSf https://github.com/alphaXiv/openresearch-cli/releases/latest/download/openresearch-cli-installer.sh | sh
orx update keeps script-installed binaries current; interactive terminals
also get a once-a-day background check with a one-line stderr notice (silence
it with ORX_NO_UPDATE_CHECK=1).
From source
Requires Rust (stable) via rustup. The prebuilt dashboard
UI is committed at ui/dist, so a plain build works:
cargo build --release # binary at target/release/orx
cargo install --path . # or install onto your PATH (~/.cargo/bin)
To hack on the dashboard UI itself (Vite + React, embedded into the binary at build time):
cd ui && pnpm install && pnpm build
Run the tests with cargo test.
Configuration
- API URL — defaults to production (
https://api.openresearch.sh); override with--api-urlorOPENRESEARCH_API_URL. - Credentials —
orx loginopens your browser, mints a personal access token, and stores it at${XDG_CONFIG_HOME:-~/.config}/openresearch/credentials.json(mode0600). Sent asAuthorization: Bearer …on every request.
Usage analytics
orx sends usage analytics linked to a random installation ID—not an account—to
help prioritize features. It's opt-out, and the orx up onboarding surfaces the
choice on first run.
- Collected: command name, a random per-install UUID, CLI version, OS/arch,
the official build channel, a CI flag, coarse install type, and coarse event
labels (e.g. onboarding completed, project created, chat session started, or
a run launched on
modal). When onboarding is completed, the disclosed research profile is also sent unfiltered: selected research areas, the Other-area description, research background, and representative paper IDs and titles. - Not automatically added: code, prompts, file contents or paths, project or experiment IDs/names, repo names, tokens, emails, or account identifiers. Anything entered in the onboarding profile is sent exactly as submitted and may contain identifying information. The random install UUID is not tied to your account.
orx telemetry off # persistent, per-machine
orx telemetry status # current state + the random install id
orx <cmd> --no-telemetry # per-run
Only official prebuilt release artifacts can send usage analytics. Source,
worktree, cargo install --path, and cargo-dist PR/dry-run builds remain off and
do not create an installation ID. ORX_TELEMETRY_ENV=off additionally disables
analytics in an official binary; it cannot enable analytics in a source build.
Events are fire-and-forget on a background task and never block a command.