Download free

Editors and the command line

Use NoBreiniers from your code editor or a terminal, or chat with it right in the terminal; if the app is closed, it starts by itself in the background.

Updated · version 2.0.266 · Markdown

You can talk to your Nobreiniers from a terminal (osirisbrain -p "your request", or a whole chat with osirisbrain), from editors that speak the Agent Client Protocol, and from the NoBreiniers extension for your editor. They all work with the same chats, permission level and approvals as the app.

Chat in the terminal

Type osirisbrain with nothing after it and press Enter: a chat opens right in the terminal.

  • It is the same session as the one in the app's window: you can follow it there at any time.
  • The answer shows as it arrives, with each step the agent takes.
  • When the agent needs your approval, the whole card shows in the terminal. Pick your answer with its letter and press Enter. A card that deletes data is answered only with your own click in the app's window.
  • Esc or Ctrl-C stops the turn. /help lists the commands (change the model, pick up an earlier session, start a new one). Ctrl-D leaves.
  • To pick up the last session later, type osirisbrain -c.

Give it tasks from another program (MCP)

Any program on your Mac that uses MCP servers (another agent, an editor, a chat app) can give NoBreiniers tasks. In that program, add a local MCP server with this command:

osirisbrain mcp serve

The program sees three tools:

  • nobreiniers_run: gives NoBreiniers a task and waits for its final answer. It starts a new chat in the folder it names, or continues a chat when it gives its number.
  • nobreiniers_sessions: your chats, newest first.
  • nobreiniers_status: whether NoBreiniers is open, and its version.

Tasks use the same chats, permissions and rules as the app. If a task needs your approval, you approve it in NoBreiniers; the other program only sees that it is waiting. If the program cancels the task, NoBreiniers stops it.

The app does not need to be open

If NoBreiniers is closed, the terminal or the editor starts it by itself, in the background:

  • It says «starting NoBreiniers in the background (about N s)…». The time is what the last starts took on your Mac.
  • It shows no window. The window appears when you open the app yourself (Dock, Finder or Spotlight).
  • It never opens a second copy. If the app is already open, it uses that one. If the app is open at the sign-in, it waits until you sign in.
  • When it is ready, your request goes on by itself.

Your user's password

The app starts by itself only for a user who opens without a password on this Mac. To turn that on, open NoBreiniers once and tick Open without password on this Mac when you sign in.

If your user asks for its password every time:

  • In a terminal, the command asks for it once, without showing what you type.
  • In an editor, the app opens with its window so you can sign in, and the editor goes on after that.
  • In a script, put the password in a file only you can read (permissions 600) and name it in OSIRISBRAIN_PROFILE_PASSWORD_FILE. Never put it on the command line.

In scripts: wait, limit, take tools away

  • It waits for what it started. osirisbrain -p "your request" ends when its work ends. If the turn left something running in the background (a command, a program, a monitor, a helper agent), it waits for it, goes on with the turn that its end wakes up, and prints that answer. While it waits it says what it is waiting for and whether that is still writing. A server (something that listens on a port) never ends by itself, so it does not wait: it says where it is serving and leaves with its answer. Add --wait-jobs to wait for it too.
  • Leave without waiting. --no-wait-jobs leaves as soon as the turn ends and says the number of the run and of the chat. What is still running wakes the chat in the app when it finishes, and osirisbrain wait followed by the chat's number follows it later.
  • A time limit. --max-time 600 stops the run after 600 seconds. The command leaves with the number 124.
  • Take tools away from one run. --deny-tools browser_navigate,mail removes those tools for this run only: they are not in its list, a call to one is refused, and everything the run starts (helper agents, jobs, programs) carries the same limit until it ends. --only-tools read,grep,shell does the opposite: it leaves the run only those and removes the rest, memory and skills included unless you name them. A limit only takes away, never adds; a name that does not exist is an error, and so is naming the same tool in both.
  • Leave nothing in your list. --ephemeral makes the new chat run alone, with no memory, skills or recipes of yours and without your Task Board (it sees only the cards it makes itself, so an empty list there does not mean the card does not exist), and archives it when it ends. It does not stay in your chat list, and its folder does not show up as a project in the sidebar. osirisbrain unarchive brings it back with its work.

When nothing is happening

A background start with no work and no window closes by itself after a while. The next request starts it again.