Report a bug (runtime, MCP, and product)

Use our public GitHub feedback repository when something breaks — especially while installing or running the Kynver runtime on your machine.

Important: nothing is sent automatically

kynver report-bug and kynver doctor runner-install run only on your machine. They prepare a draft and show links — they do not upload to Kynver or GitHub.

A bug is reported only after you or an agent manually creates a GitHub issue and pastes the draft. After that, the report lives in public GitHub Issues and Kynver triages from there (there is no separate in-app bug queue for this path).

Quick links

• Choose a template
• Install / runtime template
• Other product bugs
• All filed reports
• Repository

If you are installing the runtime

On the machine where the problem happens, run:

kynver doctor runner-install
kynver report-bug --json

The second command prints machine-readable steps for AI agents and a draft issue body. You still need to create the GitHub issue — copy the draft into the Install / runtime bug template (link above).

Do not paste API keys, runner tokens (krc1.*), or .env secrets.

If you are an AI agent

1. Run kynver report-bug --json on the user's machine.
2. Read submission.autoSubmit — it is always false. Do not tell the user the bug was sent unless a GitHub issue was actually created.
3. Read guide.agentSteps, issueBodyDraft, and submission.installTemplateUrl / submission.productTemplateUrl.
4. Create a GitHub issue (install/runtime → install template; other product areas → product template), OR show the user the draft and URL to paste manually.
5. With GitHub CLI: gh issue create --repo Totalsolutionsync/kynver-feedback --title "[install] <short summary>" --body-file draft.txt
6. After the issue exists, the report is visible at All filed reports — Kynver watches that list, not an internal API.

If the user cannot authenticate to GitHub, your job is to surface issueBodyDraft and the template URL; the report is not filed until they submit the GitHub form.

What to report here vs elsewhere

• kynver bootstrap, kynver start, doctor failures — GitHub — Install / runtime bug
• MCP connector or hosted tool errors — GitHub — Product bug
• Account not approved for Agentic OS (403) — Early access — not a bug
• Billing, account lock, disputes — hello@kynver.com
• Security vulnerabilities — Email security@kynver.com — do not use public issues