oo chat
Create conversations, send messages and retrieve files.
Talk to agents: start a conversation, send messages, follow a reply, stop it, download files and answer an agent's approval questions.
A conversation is a thread with one agent, or a group chat: several people and an agent that answers every message unless it mentions only people (oo chat group). send returns once the message is accepted, before the agent replies: read the reply with get, or follow it as it comes with follow. commands lists the slash commands an agent takes in a message.
oo chat list
Print your conversations as JSON, the latest active first, 25 unless --limit says otherwise. --order created lists them newest started first, in pages: give an answer's next_cursor to --cursor for the next page.
oo chat list [options]| Argument | Required | Default | Choices | Description |
|---|---|---|---|---|
--agent AGENT | no | |||
--limit LIMIT | no | how many, 1 to 100 | ||
--order ORDER | no | activity, created | activity (the default) or created | |
--cursor CURSOR | no | next_cursor of the previous page; lists in --order created | ||
--unfinished | no | add unfinished_run to each: whether one of its runs hasn't ended | ||
--latest-run | no | add each conversation's latest accepted task, its status and source | ||
--archived | no | list the archived conversations instead | ||
--groups | no | list only your group chats |
It also takes the connection options.
oo chat create
Start a conversation with an agent
oo chat create [options]| Argument | Required | Default | Choices | Description |
|---|---|---|---|---|
--agent AGENT | yes | |||
--title TITLE | no | |||
--cwd CWD | no | the folder the agent works in, an absolute path in its workspace or a registered project (OpenClaw agents) |
It also takes the connection options.
oo chat commands
Print the slash commands the agent takes in a chat message as JSON, as the chat's command menu lists them: each one's name, what it does and the arguments it takes.
oo chat commands agent| Argument | Required | Default | Choices | Description |
|---|---|---|---|---|
agent | yes | the agent's ID, from oo agents list |
It also takes the connection options.
oo chat models
Print as JSON every model the agent's key and your limits allow that the Sunport serves: models, each with its alias, name, provider, context_window, inputs, tool_calling, privacy and price where known, and available: a message here may choose it with oo chat send --model only when true; when false, reason_code and reason say why. Also default_alias (the agent's) and current_alias (the model the agent last used here, or null), each null when you can't choose it now, and unavailable_aliases (those two when they can't answer here now). Where the agent can think harder or less for a message, each available model also has thinking_levels and default_thinking_level, and current_thinking_level is the level the conversation thinks at (null before it starts). --agent lists a new conversation's choices before it exists.
oo chat models [options] [thread_id]| Argument | Required | Default | Choices | Description |
|---|---|---|---|---|
thread_id | no | conversation ID from oo chat list | ||
--agent AGENT | no | instead of a conversation: the agent's ID, for a new conversation | ||
--search SEARCH | no | only models whose name, alias or provider has every word | ||
--provider PROVIDER | no | only one provider's models, by the provider each model lists (anthropic, veniceai) | ||
--available AVAILABLE | no | true, false | true: only those a message here may choose now; false: only those it can't, with why |
It also takes the connection options.
oo chat group
A group chat is a conversation of several people and an agent. Its agent answers a message that mentions it, @ and its name or id, or no one (unless its owner set answers mentions), and works for the person who wrote it, who needs chat access to it: without it, a message that mentions no one goes to the people only. A message that mentions only people, @ and their name, is for them. Everyone in the group reads every message and answer. Its creator owns it: the owner adds and removes people and its agent (one for now, which the owner may chat with), sets which messages the agent answers and passes the group to another person in it; anyone in it renames it (oo chat rename), and anyone may leave; an owner who leaves passes it to the person in it longest. Anyone may hide it: it leaves their own oo chat list until something newer comes in it, and they stay in it. oo chat get shows who changed what (group_changed events) and their names. Send, read and follow it as any conversation, with oo chat send, get and follow.
oo chat group [COMMAND]It also takes the connection options.
oo chat group create
Start a group chat; you own it
oo chat group create [options]| Argument | Required | Default | Choices | Description |
|---|---|---|---|---|
--title TITLE | yes | the group's name |
It also takes the connection options.
oo chat group candidates
Print as JSON every active person of the Sunport but you, by person ID, name and email: whom oo chat group add --person takes.
oo chat group candidatesIt also takes the connection options.
oo chat group members
Print as JSON the group's members (kind, id, name, role) and, for its owner, candidates: the people they may add, with their person IDs.
oo chat group members thread_id| Argument | Required | Default | Choices | Description |
|---|---|---|---|---|
thread_id | yes | the group's ID |
It also takes the connection options.
oo chat group add
Add a person or an agent to a group (its owner)
oo chat group add [options] thread_id| Argument | Required | Default | Choices | Description |
|---|---|---|---|---|
thread_id | yes | the group's ID | ||
--person PERSON_ID | no | a person, by the ID oo chat group members shows | ||
--agent AGENT_ID | no | an agent, by its ID from oo agents list |
It also takes the connection options.
oo chat group remove
Remove a person or an agent from a group (its owner)
oo chat group remove [options] thread_id| Argument | Required | Default | Choices | Description |
|---|---|---|---|---|
thread_id | yes | the group's ID | ||
--person PERSON_ID | no | a person, by the ID oo chat group members shows | ||
--agent AGENT_ID | no | an agent, by its ID from oo agents list | ||
--yes | no | confirm it now; an agent passes it only once the person confirmed it in chat |
It also takes the connection options.
oo chat group answers
all: a message that mentions the agent or no one, as a new group does. mentions: only a message that mentions it; one that mentions no one goes to the people.
oo chat group answers thread_id answers| Argument | Required | Default | Choices | Description |
|---|---|---|---|---|
thread_id | yes | the group's ID | ||
answers | yes | all, mentions | all or mentions |
It also takes the connection options.
oo chat group owner
The person owns the group from then on; you stay in it as a member and change no more of it.
oo chat group owner [options] thread_id| Argument | Required | Default | Choices | Description |
|---|---|---|---|---|
thread_id | yes | the group's ID | ||
--person PERSON_ID | yes | a person in the group, by the ID oo chat group members shows | ||
--yes | no | confirm it now; an agent passes it only once the person confirmed it in chat |
It also takes the connection options.
oo chat group hide
Hide a group from your list until something new comes in it
oo chat group hide thread_id| Argument | Required | Default | Choices | Description |
|---|---|---|---|---|
thread_id | yes | the group's ID |
It also takes the connection options.
oo chat group leave
Leave a group
oo chat group leave [options] thread_id| Argument | Required | Default | Choices | Description |
|---|---|---|---|---|
thread_id | yes | the group's ID | ||
--yes | no | confirm it now; an agent passes it only once the person confirmed it in chat |
It also takes the connection options.
oo chat get
Show a conversation with its messages
oo chat get thread_id| Argument | Required | Default | Choices | Description |
|---|---|---|---|---|
thread_id | yes | conversation ID from oo chat list |
It also takes the connection options.
oo chat send
Send a message
oo chat send [options] thread_id| Argument | Required | Default | Choices | Description |
|---|---|---|---|---|
thread_id | yes | conversation ID from oo chat list | ||
--message MESSAGE | no | |||
--attachment ATTACHMENT | no | |||
--model MODEL | no | a model alias from oo chat models; the conversation keeps it | ||
--thinking THINKING | no | off, minimal, low, medium, high, xhigh, max | how hard the model thinks, one of its thinking_levels from oo chat models; goes with --model, and the conversation keeps it | |
--idempotency-key IDEMPOTENCY_KEY | no | reuse the same key when reconciling an uncertain submission (a new one each send by default) |
It also takes the connection options.
oo chat abort
Stop the reply in progress
oo chat abort thread_id| Argument | Required | Default | Choices | Description |
|---|---|---|---|---|
thread_id | yes | conversation ID from oo chat list |
It also takes the connection options.
oo chat download
Download a file from a conversation
oo chat download [options] thread_id file_id| Argument | Required | Default | Choices | Description |
|---|---|---|---|---|
thread_id | yes | conversation ID from oo chat list | ||
file_id | yes | ID of a file in the conversation | ||
--output OUTPUT | yes | |||
--overwrite | no |
It also takes the connection options.
oo chat approve
Answer an agent's approval question
oo chat approve [options] thread_id approval_id| Argument | Required | Default | Choices | Description |
|---|---|---|---|---|
thread_id | yes | conversation ID from oo chat list | ||
approval_id | yes | ID of the agent's approval question | ||
--decision DECISION | yes | allow, allow_session, deny |
It also takes the connection options.
oo chat questions
Show task questions for the person or agent who started the task
oo chat questions thread_id| Argument | Required | Default | Choices | Description |
|---|---|---|---|---|
thread_id | yes | conversation ID from oo chat list |
It also takes the connection options.
oo chat answer
Answer a task question and resume its existing session
oo chat answer [options] thread_id question_id| Argument | Required | Default | Choices | Description |
|---|---|---|---|---|
thread_id | yes | conversation ID from oo chat list | ||
question_id | yes | question ID from oo chat questions | ||
--text TEXT | no | answer a single question as text | ||
--answers ANSWERS | no | JSON map for several questions, e.g. {"color":["Blue"]} |
It also takes the connection options.
oo chat follow
Print the conversation's events as the Sunport sends them, as server-sent events: each chat event (event: chat) with its sequence number (id) and the event as JSON (data), such as a run starting, the reply's text as it streams, a tool call or an approval question. A run ends with an event of type run_done, run_failed or run_aborted, but the stream goes on: it stops when the Sunport ends it, after --max-time (exit 1, api_request_timeout), or at Ctrl-C. --run follows one run, such as the one oo chat send started; --after goes on after the last sequence number it printed.
oo chat follow [options] thread_id| Argument | Required | Default | Choices | Description |
|---|---|---|---|---|
thread_id | yes | conversation ID from oo chat list | ||
--run RUN_ID | no | only this run's events | ||
--after SEQUENCE | no | only events after this sequence number | ||
--max-time SECONDS | no | 300 | stop after this long (default 300, at most 3600) |
It also takes the connection options.
oo chat terminal
Print how a conversation with an agent on a coding harness (Codex, Claude Agent, Gemini CLI, OpenCode or Pi, on a VM of its own) goes on in that VM's terminal: its session there, the folder it works in and the line to run, such as claude --resume SESSION. What you and the agent say there shows in the conversation; a session started in the terminal stays there. The line refuses while a reply is in progress here, and a message here is refused while the line's CLI has the session open. In Pi, web chat model access does not carry over. Use /login if a provider sign-in is needed, then choose an available model with /model.
oo chat terminal thread_id| Argument | Required | Default | Choices | Description |
|---|---|---|---|---|
thread_id | yes | conversation ID from oo chat list |
It also takes the connection options.
oo chat rename
Give the conversation a name, up to 200 characters, and print it as JSON. An agent names a conversation itself after its first answer, unless it has a name; once a person names it, the agent leaves the name as it is.
oo chat rename [options] thread_id| Argument | Required | Default | Choices | Description |
|---|---|---|---|---|
thread_id | yes | conversation ID from oo chat list | ||
--title TITLE | yes | the conversation's new name |
It also takes the connection options.
oo chat archive
Archive the conversation and print it as JSON. Its reply in progress, and the messages waiting behind it, stop; it leaves oo chat list (oo chat list --archived lists it) and takes no more messages, but oo chat get still shows it.
oo chat archive [options] thread_id| Argument | Required | Default | Choices | Description |
|---|---|---|---|---|
thread_id | yes | conversation ID from oo chat list | ||
--yes | no | confirm it now; an agent passes it only once the person confirmed it in chat |
It also takes the connection options.
oo chat delete
Delete the conversation for good, with its messages, after stopping its reply in progress. One support had access to is kept by the record of that access: archive it.
oo chat delete [options] thread_id| Argument | Required | Default | Choices | Description |
|---|---|---|---|---|
thread_id | yes | conversation ID from oo chat list | ||
--yes | no | confirm it now; an agent passes it only once the person confirmed it in chat |
It also takes the connection options.