Diagnostics

Run:

odinn doctor
odinn status
odinn audit verify
odinn runs

What odinn doctor includes

The diagnostic report summarizes:

• Ódinn version and exported commit identity;
• operating system and Node.js version;
• provider mode without credentials;
• active experimental flags;
• audit verification status;
• pending approvals;
• browser recovery state;
• queued, running, failed, and needs-review job counts.

The running gateway exposes the same safe snapshot at its authenticated diagnostics endpoint.

What it omits

The report deliberately omits:

• local state paths;
• API keys and OAuth tokens;
• cookies and gateway bearer tokens;
• prompts and private model content;
• browser-profile data;
• provider secrets.

Do not replace this safe report with a raw archive of the state directory.

A useful bug report

Include:

• operating system and architecture;
• Node.js version;
• Ódinn version;
• provider name and authentication mode;
• exact command or UI action;
• expected result;
• observed result;
• sanitized terminal or gateway output;
• whether restart or rollback changed the outcome.

Remove usernames, client names, private hostnames, filesystem paths, prompts with personal data, and any credential-like value.

Correlation

Runtime errors include a request correlation value. Audit records may also associate the request with a run, job, provider attempt, approval, or browser-recovery record. Share the safe diagnostic correlation shown by the UI or report; do not expose raw signed records merely to provide an identifier.

For ordinary defects, use the project’s bug report form. Security issues belong in private vulnerability reporting.