anomalyco/opencode
1
0
Fork 0
mirror of https://github.com/anomalyco/opencode.git synced 2026-07-25 20:55:42 -04:00
Code Issues 5.9k Packages Projects Releases 19 Wiki Activity

[PR #8994] feat(core): Debug mode #12940

New Issue
Open
opened 2026-02-16 18:17:49 -05:00 by yindo · 0 comments
yindo commented 2026-02-16 18:17:49 -05:00
Owner
Copy Link
Copy Source

Original Pull Request: https://github.com/anomalyco/opencode/pull/8994

State: open
Merged: No

What does this PR do?

PR Summary: Debug Mode Feature

This PR introduces a new Debug Agent Mode that enables evidence-based debugging through structured instrumentation, log analysis, and a guided reproduction workflow.

HEAVILY INSPIRED FROM CURSOR DEBUG MODE

Overview

  • Adds a dedicated debug agent mode alongside existing modes (e.g. build, explore)
  • Enforces a disciplined, multi-phase debugging workflow
  • Introduces infrastructure for structured debug logs and reproduction steps
  • Integrates debugging flows into the API, UI, and SDK

Key Features

1. New Debug Agent Mode

  • Adds a new debug agent mode
  • Description:
    “Evidence-based debugging mode. Use this to generate hypotheses, add runtime instrumentation, analyze logs, and only then implement fixes.”

2. Structured Debug Workflow

The debug prompt (packages/opencode/src/agent/prompt/debug.txt) defines a 7-phase workflow:

  1. Generate testable hypotheses
  2. Add instrumentation logs (3–8 logs)
  3. Reproduce the issue with log clearing
  4. Analyze logs (NDJSON format)
  5. Implement fixes (only with supporting evidence)
  6. Verify with before/after comparison
  7. Cleanup after confirmation

3. Debug Infrastructure

  • Debug module (src/debug/index.ts)

    • Log ingestion
    • Config injection
    • File management

  • Debug config injection

    • Automatically injects a <debug_config> block into system prompts when using the debug agent

  • Log format

    • NDJSON (one JSON object per line)

    • Required fields:

      • sessionId
      • runId
      • hypothesisId
      • location
      • message
      • data
      • timestamp

4. Reproduction Steps System

  • New reproduction steps request/response system (src/debug/repro.ts)

  • TUI component (reproduction-steps.tsx) for user interaction

  • Supported actions:

    • proceed
    • fixed
    • skipped

  • Integrated into the session UI with keyboard navigation

5. API Endpoints

  • POST /ingest/:sessionId
    Ingest debug logs and append them to .opencode/debug.log
  • GET /reproduction-steps
    List pending reproduction requests
  • POST /reproduction-steps/:requestID/reply
    Reply to a reproduction prompt
  • POST /reproduction-steps/:requestID/reject
    Reject a reproduction prompt

6. UI Integration

  • Reproduction steps prompt component with visual indicators
  • Integrated into the session view with proper priority
    (shown after permissions and questions)
  • Keyboard shortcuts for navigation and confirmation

How did you verify your code works?

https://github.com/user-attachments/assets/241d9628-ad32-48e8-9e49-a8e44cf9333b

**Original Pull Request:** https://github.com/anomalyco/opencode/pull/8994 **State:** open **Merged:** No --- ### What does this PR do? #### PR Summary: Debug Mode Feature This PR introduces a new **Debug Agent Mode** that enables evidence-based debugging through structured instrumentation, log analysis, and a guided reproduction workflow. **HEAVILY INSPIRED FROM CURSOR DEBUG MODE** --- ## Overview * Adds a dedicated **debug** agent mode alongside existing modes (e.g. build, explore) * Enforces a disciplined, multi-phase debugging workflow * Introduces infrastructure for structured debug logs and reproduction steps * Integrates debugging flows into the API, UI, and SDK --- ## Key Features ### 1. New Debug Agent Mode * Adds a new `debug` agent mode * Description: *“Evidence-based debugging mode. Use this to generate hypotheses, add runtime instrumentation, analyze logs, and only then implement fixes.”* --- ### 2. Structured Debug Workflow The debug prompt (`packages/opencode/src/agent/prompt/debug.txt`) defines a **7-phase workflow**: 1. Generate testable hypotheses 2. Add instrumentation logs (3–8 logs) 3. Reproduce the issue with log clearing 4. Analyze logs (NDJSON format) 5. Implement fixes (only with supporting evidence) 6. Verify with before/after comparison 7. Cleanup after confirmation --- ### 3. Debug Infrastructure * **Debug module** (`src/debug/index.ts`) * Log ingestion * Config injection * File management * **Debug config injection** * Automatically injects a `<debug_config>` block into system prompts when using the debug agent * **Log format** * NDJSON (one JSON object per line) * Required fields: * `sessionId` * `runId` * `hypothesisId` * `location` * `message` * `data` * `timestamp` --- ### 4. Reproduction Steps System * New reproduction steps request/response system (`src/debug/repro.ts`) * TUI component (`reproduction-steps.tsx`) for user interaction * Supported actions: * `proceed` * `fixed` * `skipped` * Integrated into the session UI with keyboard navigation --- ### 5. API Endpoints * `POST /ingest/:sessionId` Ingest debug logs and append them to `.opencode/debug.log` * `GET /reproduction-steps` List pending reproduction requests * `POST /reproduction-steps/:requestID/reply` Reply to a reproduction prompt * `POST /reproduction-steps/:requestID/reject` Reject a reproduction prompt --- ### 6. UI Integration * Reproduction steps prompt component with visual indicators * Integrated into the session view with proper priority (shown after permissions and questions) * Keyboard shortcuts for navigation and confirmation --- ### How did you verify your code works? https://github.com/user-attachments/assets/241d9628-ad32-48e8-9e49-a8e44cf9333b
yindo added the pull-request label 2026-02-16 18:17:49 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
acp
bad
bug
discussion
docs
documentation
enhancement
extension
good first issue
growth
help-wanted
mcp
model-problem
needs:compliance
nix
opentui
perf
pull-request
Mirrored from GitHub Pull Request
 tui
web
windows
zen
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#12940
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?