Quick start
ravion bug when something is broken and ravion feedback when something is confusing, harder than it should be, or missing. Both are also available as ravion report bug and ravion report feedback.
What to include
- What happened, then what you expected.
- The exact error text.
- IDs of the resources involved, such as
proj_,env_,minst_,pipe_,prun_,sexec_,mdep_, andstk_. Each one resolves athttps://app.ravion.com/go/<id>, so a single ID is enough for us to find the resource. A dashboard URL works just as well. - The command you ran, passed as
--command.
Requirements
- Sign in with
ravion login, or setRAVION_API_KEY. See Authentication. - Run
ravion switchto change which organization a report is filed under. - Up to 20 reports per hour, and 64 KB per message.
Report submitted. and exits 0. No ticket ID is returned, so email support@ravion.com if you need a reply.
For AI agents
Nothing about these commands is interactive — no prompts, no editor, nothing read from stdin — so agents can call them directly. Exit0 means the report was submitted and 1 means anything else. There is no --json output.
Agents should paste the IDs they are already holding rather than describing resources in prose. Ravion auto-detects opencode, Claude Code, Codex, Gemini CLI, Cursor, and Aider; pass --agent for anything else.
Every command’s help output ends with these hints, and unexpected errors append them, so agents discover the commands on their own. Add them to your agent instructions to make reporting routine rather than a fallback.
Command reference
Every flag for
ravion report, ravion bug, and ravion feedback.Contact support
Reach the team about your account, billing, or an urgent issue.