​

feedbacks

orc feedbacks submits product feedback or bug reports with a category, message, and reproduction context. Normally it uses the active profile and Workspace; a Workspace owner can list submitted feedback.

Use --anonymous to report a problem such as a failed login when authentication is unavailable. Anonymous submissions do not resolve or send saved credentials or a Workspace and do not support attachments.

Report a problem anonymously when authentication is unavailable.

Reads back feedback for the Workspace. Listing requires the Workspace owner role.

Submits a report with a category. category is inaccurate, instruction-not-followed, out-of-scope, typo, slow-or-broken, or other. Messages are limited to 2000 characters; you can include a conversation ID or JSON client_context. Screenshots use existing Files IDs; inline images and base64 payloads are not accepted.

Retry identity for operations that support idempotency. Use a unique key for each new operation, and reuse it only when retrying the same HTTP method, path, query values and exact request body. JSON whitespace changes can count as a different body. Keys contain 1–255 characters after trimming and expire after 24 hours. A completed JSON response is replayed without repeating the operation. A different request using the same key returns 409 idempotency_error. An in-progress request returns 409 idempotency_in_progress with Retry-After: 2. Whether this header is required depends on the operation.

Type: string. Optional.

(required) Body field: category; enum: inaccurate|instruction-not-followed|out-of-scope|typo|slow-or-broken|other

Type: string. Optional.

Description of the problem. Leading and trailing whitespace is removed; the trimmed message must contain at most 2000 characters. Omission or a blank string stores an empty message. Sensitive patterns are redacted before storage.; max 2000 chars

Type: string. Optional.

Conversation reference supplied by the caller. Whitespace is trimmed; omission, null or a blank string stores no reference. This field does not fetch conversation contents.; (use "null" or "reset" to clear)

Type: string. Optional.

Up to three distinct files-domain IDs for completed screenshot uploads in the authenticated workspace. IDs are trimmed and deduplicated. Omission attaches no files. Anonymous submissions cannot attach screenshots. Files must use the screenshot purpose and pass the screenshot upload policy; inline images and base64 payloads are not accepted.; csv

Type: string. Optional.

Optional diagnostic context. Omission stores an empty object. Only surface, url, route, viewport, user_agent, app_revision, locale and theme are retained; other keys are discarded. surface accepts authed-sidebar or public-sidebar. Other values must be nonblank strings. URLs must use HTTP or HTTPS; credentials, query and fragment are removed. Routes lose query and fragment. Text whitespace is normalized. Values are truncated to 2048 characters for url, 512 for route and user_agent, 32 for viewport, 128 for app_revision, and 64 for locale and theme.; (JSON object, e.g. '{"custom_id":"x"}')

Type: string. Optional.

Submit reproduction context from a file.

You cannot combine --anonymous with --workspace, credential selectors, or --screenshot-file-ids. Do not include screenshot IDs in an anonymous JSON body either. A failed authenticated submission does not automatically fall back to anonymous submission.

Report a failure and verify the fix covers reproduction details, --stdin submission, keeping receipt IDs, and verification after a fix.

The following global options can be used with orc feedbacks:

For details and examples, see global options.