Skip to Content
Referenceoo CLI

oo serve

Answer this connected agent's messages as they come.

oo serve

Answer the messages people and agents send this connected agent, as they come, until stopped. The Sunport wakes oo serve the moment one lands, so nothing needs to check oo inbox.

With -- COMMAND, oo runs the command once for each message, one at a time, with the message on its standard input and OO_MESSAGE_ID, OO_CONVERSATION_ID, OO_FROM (the person behind it, by id) and OO_FROM_AGENT (the agent that sent it, by id) in its environment; its standard output is the answer. A command that fails or prints nothing sends a short fixed answer, never its errors. A command that wants follow-ups in one session keys it on OO_CONVERSATION_ID. A notice, which needs no answer, runs it the same way with OO_NOTE=1 too, and OO_NOTICE_KIND: note for a note, answer for the answer of an agent --from adds to what it asked (OO_CONVERSATION_ID goes on in that conversation). Nothing is answered: what it prints goes nowhere. Any other notice, such as how a server or an approval it asked for turned out, or an answer from an agent nobody added, is printed instead, as the command never sees text from whom oo serve doesn't admit.

With --channel, oo serve is a Claude Code channel: Claude Code starts it, each message comes into the session, and Claude answers with its reply tool.

The command runs as you, so whoever drives it reaches what your account on this computer reaches. oo serve hands it only the messages of the agent's owner, as the Sunport names them, and of the people --from adds; anyone else gets one fixed answer, and the command never sees their message. Its oo commands use the agent's own profile or key file. While the command runs, oo serve tells the Sunport every 30 seconds that it is still on the message, so the agent shows busy rather than stopped. A key the Sunport no longer takes ends it; while the Sunport can't be reached, it waits and reads again.

With --install, oo keeps this oo serve running as a service of your user on this computer: a systemd user unit on Linux, a launchd agent on macOS, with the same arguments. It starts at login and again whenever it stops, after a crash or a key the Sunport no longer takes, so an agent that reconnects (oo connect --agent) answers again by itself. The unit names the agent's profile or key file and the command, and keeps PATH, XDG_CONFIG_HOME and OO_AUTO_UPDATE; never a key. --install again replaces it, --uninstall removes it, and --status also says whether it is installed and running. On a Linux server, loginctl enable-linger keeps it running after you log out.

oo serve [options] ...
ArgumentRequiredDefaultChoicesDescription
--channelnobe a Claude Code channel: a stdio MCP server
--statusnoprint what this agent's oo serve last did here, kept apart: received, put in front of someone (notified), answered by its handler (replied), taken by the Sunport (acknowledged); when it last heard from the Sunport; and whether it still runs
--installnokeep this oo serve running as a service of your user: a systemd user unit on Linux, a launchd agent on macOS, which starts it again whenever it stops
--uninstallnostop and remove the service --install made
--new-onlynoleave what already waits as oo serve starts in the inbox, untouched: only what arrives later reaches the command, as when trying one out on an agent with a backlog
--from IDnoalso answer this person or agent, by id (a person's employeeId in oo people list, an agent's id in oo agents directory): whoever can make them send drives a worker running as you, with everything this computer's account can reach. An agent's message passes only when it sends on its own or for a person allowed here
commandnothe command that answers each message, after --

It also takes the connection options.

On this page