Skip to content

From report to fix

What happens to a report sent from your editor: the hourly triage, public issues in elide-dev/elide, +1s on duplicates, draft benchmark cases, and tracking with report_status.

On this page
Open in ChatGPTOpen in Claude

An accepted report becomes a public issue in elide-dev/elide, usually within the hour.

Report lifecycle The coding agent calls preview_report, which scrubs, dedupes and previews. The developer confirms, and submit_report puts the report in the queue. An hourly triage turns it into a public issue, a +1 on an existing issue, a draft benchmark case, a docs fix, or human review. report_status reads the status back to the agent. Coding agent preview_report scrub · dedupe · preview, read-only Developer confirms one-click form or confirm token submit_report into the queue Hourly triage usually within the hour Public issue · intake, kind:<kind> +1 on an existing issue Draft benchmark case Docs fix Human review report_status reads it back
  1. The agent calls preview_report: secrets and personal data are stripped, duplicates checked, and a preview returned. Nothing is sent.
  2. You confirm, and submit_report puts the report in the queue.
  3. An hourly triage job reads the queue.
  4. Each report becomes a public issue, a +1 on an existing issue, a draft benchmark case, a docs fix, or goes to human review.
  5. report_status reads the status back to the agent.

Outcomes

OutcomeWhen
New public issueThe report is new. Labels: intake and kind:<kind>.
+1 on an existing issueThe problem is already reported.
Draft benchmark caseA perf report includes a repro.
Docs fixThe docs were wrong or missing.
Human reviewTriage can’t decide.

Track a report

Call report_status with the id submit_report returned. It reports the state and, once triaged, the issue URL.

Follow issues with the intake label at elide-dev/elide. For immediate help, ask on Discord at https://elide.dev/discord.

Was this page helpful?