New Research: Supply Chain Attack on Axios Pulls Malicious Dependency from npm.Details →
Socket
Book a DemoSign in
Socket

opencode-debug-agent

Package Overview
Dependencies
Maintainers
1
Versions
8
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

opencode-debug-agent

OpenCode plugin for runtime debugging - capture and analyze execution data

latest
Source
npmnpm
Version
0.1.7
Version published
Maintainers
1
Created
Source

opencode-debug-agent

OpenCode plugin for runtime debugging - capture and analyze execution data via HTTP instrumentation.

Features

  • Debug Agent - Primary agent specialized for debugging workflows
  • Debug Skill - Use debugging tools from any agent via skill({ name: "debug" })
  • HTTP Server - Hono-based server with CORS support for browser/Node instrumentation
  • Port Persistence - Server remembers its port across sessions
  • 5 Tools - debug_start, debug_stop, debug_read, debug_clear, debug_status

Installation

Add to your opencode.json:

{
  "plugin": ["opencode-debug-agent"]
}

Or for local development, copy to .opencode/plugin/.

Usage

Using the Debug Agent

Switch to the debug agent (Tab key) and describe your issue. The agent will:

  • Start the debug server
  • Instrument your code with fetch() calls
  • Ask you to reproduce the issue
  • Analyze captured logs
  • Help identify the problem
  • Clean up instrumentation

Using the Debug Skill (from any agent)

Load the debug skill and help me debug this API timeout issue.

The build agent can then use all debug tools.

Manual Tool Usage

debug_start          # Start server, get instrumentation snippet
debug_status         # Check if server running, get port
debug_read           # Read captured logs
debug_read(tail: 10) # Read last 10 entries
debug_clear          # Clear log file
debug_stop           # Stop server

How It Works

  • Start server: debug_start launches an HTTP server and returns a ready-to-use fetch() snippet
  • Instrument code: Insert the snippet at strategic locations to capture runtime data
  • Reproduce issue: User runs their code normally
  • Analyze logs: debug_read returns captured data as structured JSON
  • Clean up: debug_stop and remove instrumentation

Instrumentation Example

// Snippet returned by debug_start:
fetch("http://localhost:54321/log", {
  method: "POST",
  headers: {"Content-Type": "application/json"},
  body: JSON.stringify({label: "LABEL_HERE", data: {YOUR_DATA}})
})

// Used in code:
fetch("http://localhost:54321/log", {
  method: "POST", 
  headers: {"Content-Type": "application/json"},
  body: JSON.stringify({label: "before-api", data: {userId, params}})
})

Files

  • .opencode/debug.log - NDJSON log file
  • .opencode/debug.port - Persisted port number

Development

bun install
mise run build
mise run test
mise run lint

License

MIT

Keywords

opencode

FAQs

Package last updated on 16 Feb 2026

Did you know?

Socket

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts