Developer tools
What iohr can do
One program that signs you in, calls the API, starts projects, answers questions at your prompt, installs extensions and runs checks. The map of every guide.
iohr is the InOrbit command line. The command line page installs it
and lists every command. This page is the map: what it does for you, in the order most
people reach for it, with a guide for each part.
What you can do with it
| You want to | Run | Guide |
|---|---|---|
| Sign in and call the API from a terminal or CI | iohr login, then iohr api GET /v1/me | Command line |
| Start a project with a record, an atlas and memory | iohr project init my-shop | Projects |
| Approve asks and watch your agents from the shell | iohr | iohr panel |
| Ask a question without leaving the prompt | ? why did that fail | The ? prompt |
| Have the project's Roles answer beside Io | iohr session, then iohr stop | The ? prompt |
| Approve an ask on a Mac with Touch ID | iohr asks key enroll, iohr asks approve | Command line |
| Answer voice calls with Io on your own runner | iohr runner run | Voice tools |
| Keep what a project has learned next to its code | iohr memory remember "We use sqlx" | Projects |
| Send the project's documents to Decisions | iohr sync | Projects |
| See and install programs InOrbit publishes | iohr ext show, iohr ext install agent | Extensions |
| Get a client for your language | iohr sdk generate --lang rust --for work | Generate an SDK |
| Connect another tool for InOrbit to act in | iohr connections add | Connections |
| Open the InOrbit web UI on this machine | iohr-preview ui | iohr ui |
| Try what is not released yet | iohr-preview | iohr and iohr-preview |
How it is put together
- One program, many nouns. Commands read as
iohr <thing> <verb>:iohr project init,iohr ext install,iohr memory recall,iohr connections list.iohr <thing> --helpprints one line per verb. - Plain output when nobody is watching. At a terminal you get spinners, colour and a
menu where a choice is needed. With
--json,NO_COLOR,TERM=dumbor without a terminal, nothing is drawn or asked: results go to stdout as data and notes to stderr. - Your credentials stay yours.
iohr loginkeeps a profile per account. The AI parts run the Claude Code you already have (iohr askand--describecan use Codex instead), signed in with your own account, never an API key, andiohrkeeps no record of the question or the answer. - It tells you what it did not do. A step that needs something InOrbit does not offer
yet is printed as
not yet, never skipped in silence.
Where each part stands
iohr is a pre-release (0.1.0-alpha.39): commands and output can still change
before 1.0. Everything in the table above is in the release except iohr ui, which is in
iohr-preview only.
- Sessions (
iohr session,iohr stop) run on macOS and Linux and need a runner of their own (iohr runner register). - Touch ID signs a review, a document, a decision or a run. A merge, a roll, a migration or an auto-approve rule still goes to your phone. Enrolling needs Xcode's command line tools the first time; Windows and Linux refuse it.
- Voice has no command of its own:
iohr runner runanswers a voice call with Io on a Claude Code session it keeps open, and keeps one ready for the next call.
Each guide says which parts are in the release and which only in
iohr-preview.