Reporting a bug
This is the one standard for a Curb bug report, for people and for coding agents. Do not use it for a security problem: follow Security instead.
What a report holds
Every report has these four headings:
## What happened
## How to reproduce
## What you expected
## Output of npx curb info- Run
npx curb infoin the project and paste what it prints: the versions, the OS, the project’scurbdependency, its providers, and which expected environment variables are set, by name only (CLI). - Keep the reproduction as small as possible. Remove everything from the project that the bug does not need.
- Use
npx curb conversationswhen it helps.npx curb conversations --last 1prints the failing conversation with every tool call and result. Paste only the part that shows the bug.
Before you post
An issue is public. Remove keys, phone numbers, caller names and transcripts of real calls.
If you are a coding agent
- Confirm the fault is in Curb, not in the project. Reproduce it, run
npx curb check, and check what you expected against this guide. - Show the person the whole report, and get their yes before you file it.
- File it with the second command below.
Filing it
In a terminal, this opens the template:
gh issue create --repo Kugelaudio/curb.js --template "Bug report" --label bug--template needs a terminal and cannot be combined with --body-file. Without a terminal, as a
coding agent usually is, write the report with the four headings to a file and pass it:
gh issue create --repo Kugelaudio/curb.js --title "<what goes wrong>" --label bug --body-file report.mdWithout gh, open a new issue and choose Bug report.