| name | using-disbug |
| description | Use Disbug reports, sessions, pins, or downloaded report JSON to investigate and verify bugs. |
Using Disbug
Use Disbug as evidence for reproducing, diagnosing, fixing, and verifying a reported bug.
Choose the available interface
- If you can run shell commands and
disbug is installed, use the CLI. Run disbug --help or disbug <command> --help when you need exact syntax.
- If you have Disbug MCP tools but no shell access, use those tools. Read their schemas for exact inputs.
- Follow the user's requested interface when they name one.
Do not assume that having the disbug mcp command means the current agent is connected to it. If MCP tools are unavailable, use the CLI when possible or ask the user to run disbug configure and restart the agent.
Investigation workflow
- Treat the report URL as the stable identity for a cloud report. Preserve any
?pin= selection.
- Start with the session summary or the selected pin's feedback. Establish what the user expected, what happened, the page, and the relevant time window.
- Fetch only the evidence needed for the current hypothesis. Useful evidence can include console output, network activity, user actions, page state, screenshots, storage, system context, and files attached to a pin. Session and pin output includes attachment filenames and IDs; download a relevant attachment so its contents reach the agent.
- Correlate evidence before changing code. Prefer timestamps, request IDs, routes, and visible state over guesses.
- Implement the smallest well-supported fix, then run the repository's relevant checks.
- Verify against the original report. If new reports are arriving during a live debugging session, use Disbug's watch capability to continue from fresh evidence.
- When a user-requested fix is verified, update that pin to
resolved and add a concise note describing the verified change. Use dismissed only when you have a concrete reason, and include it in the note. Leave the status unchanged when the fix is incomplete, uncertain, or unverified.
Fetching, reading, or diagnosing a report must never change its status. A status update is an explicit final workflow action performed through the Disbug CLI or MCP tool; it is not background automation. Keep pin notes attached to the pin they describe. Do not update the session status automatically, including when every pin is resolved or dismissed. Use the session status command or MCP tool only when the user explicitly requests a session-status change.
For a downloaded report JSON file, inspect the local file with the CLI or the MCP local-report capability. Local JSON inspection does not require cloud authentication.
Efficient evidence use
Avoid loading every large evidence field by default. Begin with the session or pin overview, then request the smallest useful set of fields. Expand only when the current evidence is insufficient.
When authentication fails, use the CLI login flow if shell access is available. When agent integration is missing or stale, use disbug configure; use disbug doctor to verify the result.
