Skip to Content
Referenceoo CLI

oo feedback

Tell the OpenOrange team about a problem or an idea, and read their replies.

Send the OpenOrange team a problem report, an idea or a question, and read and answer their replies.

A report goes to the OpenOrange team with your name, this Sunport and its version; with --conversation, that conversation's ID as a reference, never its content. This Sunport's server and agent VM logs and service settings from around the time you send it are attached, with secrets removed. Each person or agent sends at most 10 an hour. The team answers in the report's thread and sets its status (new, triaged or closed): oo feedback list shows each report with how many replies it has, oo feedback show its whole thread, and oo feedback reply answers the team. A Sunport not connected to OpenOrange keeps its reports to itself (status local): the team doesn't see them, so no reply comes.

With no login, or when the Sunport doesn't answer or refuses this computer's key, oo feedback send goes through the OpenOrange app instead, unverified, with --email for the team's answer.

oo feedback send

Send the OpenOrange team a problem report (bug: something is broken), an idea (something is missing) or a question (how something works), and print its receipt as JSON: its id, its status, url (its page, with the team's replies) and via. It goes with your name, this Sunport and its version. This Sunport's server and agent VM logs and service settings from around the time you send it are attached, with secrets removed. When a person asked you in this chat turn, Code session or task, it is theirs: their name, with yours as the agent that sent it, and their Feedback page shows the replies; the answer's openHours is OO Open Hours, to offer them, and support.email where they can write to the team. Each person or agent sends at most 10 an hour (too_many_reports, with retry_after_s). It looks once more, a second later, whether the report reached the team: status sent means the team has it, pending that it is still on its way from this Sunport (oo feedback show follows it), local that this Sunport isn't connected to OpenOrange.

With no login, or when the Sunport doesn't answer or refuses this computer's key, it goes through the OpenOrange app (--app) instead: via unverified, answered by email at --email, which is required then, and at most 2,000 characters. The app asks this computer to solve a short bot check first.

oo feedback send [options] text
ArgumentRequiredDefaultChoicesDescription
--kind KINDyesbug, idea, questionbug, idea or question
--conversation IDnothe chat or Code conversation it happened in: sent as a reference only, never its content
--email EMAILnowhere the team answers you, when it goes through the OpenOrange app
--app APPnoApp HTTPS origin (default: https://app.openorange.ai)
textyeswhat happened or what you would like, up to 4,000 characters, or - to read it from standard input

It also takes the connection options.

oo feedback list

Print reports as JSON, newest first: each with its id, kind, text, who sent it, whether it reached the OpenOrange team (status local, pending, sent or rejected), the team's status (new, triaged or closed), how many replies the team sent, how many of them on your own reports you have not opened (unread, summed at the top) and when the last one came. An administrator sees every report from this Sunport; anyone else sees their own. support.email is where a person can write to the OpenOrange team.

oo feedback list [options]
ArgumentRequiredDefaultChoicesDescription
--limit LIMITno50how many to print, 1 to 100 (default 50)

It also takes the connection options.

oo feedback show

Print one report as JSON with its thread, oldest first: the OpenOrange team's replies and this Sunport's answers. On your own report, this marks the team's replies read. With --wait, keep asking every 10 seconds until a new reply from the team arrives or the time is up, then print the thread. With no login, it reads a report sent through the OpenOrange app (--app): its status only, as the team answers it by email.

oo feedback show [options] id
ArgumentRequiredDefaultChoicesDescription
idyesthe report's id, from oo feedback list
--wait SECONDSno0wait up to this long for the team's next reply (at most 900)
--app APPnoApp HTTPS origin (default: https://app.openorange.ai)

It also takes the connection options.

oo feedback reply

Add a message to a report's thread for the OpenOrange team: an answer to their question, or more detail. It goes with your name, as the report did. A Sunport not connected to OpenOrange can't send one (feedback_not_sent).

oo feedback reply id text
ArgumentRequiredDefaultChoicesDescription
idyesthe report's id, from oo feedback list
textyesthe message, up to 4,000 characters, or - to read it from standard input

It also takes the connection options.

On this page