Report a Bug

It's an alpha, so there's plenty to find. If you think you've found a security problem, don't open a public issue: use the private security advisory form.

Report a bug from the app

1. Press Report a bug, the bug icon at the right of the top bar.
2. Say what you did and what went wrong, and pick roughly when it happened.
3. Press Prepare report. The app shows the whole report before anything leaves your browser.
4. Press Copy and open a GitHub issue. A new issue opens with the report filled in, and the same text is on your clipboard. Nothing is posted until you submit it on GitHub.

The report holds:

• your words;
• the app version;
• the server's Node version, OS and sign-in mode;
• your browser, OS and screen;
• the app section you were on;
• the types of recent errors, with where in the app's code they happened.

It leaves out:

• your chats, prompts, personas and characters;
• API keys, passwords, tokens, cookies and session ids;
• error messages, because they can quote your chats;
• addresses, file paths and query strings.

Server errors are included only when the server's owner sends the report. If the report is too long for a link, the issue opens cut short: paste the full report from your clipboard over it. Download diagnostics saves the same report as a file you can open, check and attach.

What else helps

What you expected, a screenshot, how often it happens, and whether it happens only with one character, model or setting.

If the app won't open

Open an issue on the Orbweaver GitHub page. In Docker, docker compose logs orbweaver shows the server log. It never contains your password, but read it before you post, because error lines can name your chats or characters.

Builds run from source also have a Capture report button. It saves the server's full flight recorders to bug-reports/ in the checkout for the developer's own review. That capture can hold chat content, so never attach it to a public issue.