Skip to main content
This page gets the opensre command onto your laptop or server, then walks you through the short setup so you can start asking questions.

​
What you get

After install, you have:
  • The opensre CLI on your PATH
  • An account-gated interactive shell when you run opensre with no arguments
  • A short webapp sign-in that also activates the OpenSRE-hosted model
No sudo required on macOS/Linux in the usual case — the installer puts the binary somewhere writable (often ~/.local/bin) and tells you if you need a PATH tweak.

​
Install

Pick one method. One-line installer (most people):
In a normal interactive terminal, the installer often starts opensre setup for you when it finishes. In CI or scripts it skips that and prints what to do next. Don’t want auto-setup?
Homebrew:
More options (PATH notes, skipping GitHub CLI install, on-prem layout): Install locally.

​
Set things up

If setup didn’t start automatically, run it yourself:
The browser opens the OpenSRE sign-up page. Create an account or sign in using email or another enabled provider; a successful login activates the hosted model, so no separate LLM key is required. Add GitHub later as an optional integration if you want OpenSRE to work with repositories. When that finishes, OpenSRE opens the interactive shell. Add tools later, when you need them:
For the guided integration and optional local-model wizard, run:
To inspect or end the account session later:
Then check that the tools you connected work:

​
Ask your first question

Open the shell and describe what’s going on:
Ask: why is checkout latency spiking? Full walkthrough with GIFs: Quickstart.

​
Environment-specific guides

​
Stuck?

  • Command not found — open a new terminal, or add the bin directory the installer printed to your PATH
  • The shell keeps asking you to sign in — run opensre account status; expired, revoked, incomplete, or unreachable sessions do not open the shell
  • Docker / make missing — see Quickstart troubleshooting
Need deploy options beyond a laptop binary? See Deployment.