Provider is not ready
Confirm the selected provider, model name, endpoint, and credential. Start local servers before retrying. Use the connection check and retain its exact error rather than switching providers without user intent.
Build or tests fail
Find the command and package root that actually failed. Keep the original output, correct the owning source or dependency configuration, and run that same command again before broad project validation.
Browser task cannot inspect a page
Confirm the browser extension is enabled and the current tab allows access. Restricted browser pages may block extension access. Start with a page you are authorized to inspect and request only the context needed.
Ticket remains blocked
A blocker records work the harness could not safely finish within the available evidence or repair budget. Review its root cause, next action, changed files, and validation proof. After a repair, ask for QA and run the required checks; do not mark it done from a model statement alone. See how repair history and verification are handled.
Report an issue
Share the product surface, OS, provider/model, task, exact failing step, and a redacted screenshot or log. Remove credentials and private customer content first. For security issues, follow the private reporting instructions.
Check the installed version
Run rmai --version for the CLI or check the installed extension version in VS Code. Compare it with the release notes.