You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
import{PluginClient}from'@barrersoftware/copilot-plugins';constclient=newPluginClient();awaitclient.start();constsession=awaitclient.createSession();// Install pluginawaitsession.sendAndWait({message: '/plugins install debug-logger'});// All interactions now logged with full details!
Example Output
🐛 ═══ DEBUG LOGGER ENABLED ═══
🐛 [2026-01-17T08:00:00.000Z] SESSION CREATED
Session ID: abc123
🐛 [2026-01-17T08:00:01.234Z] [+1.23s] BEFORE SEND
Message: "What is the capital of France?"
Length: 31 chars
Conversation history: 3 messages
Tool calls: 0, Tool results: 0
🐛 [2026-01-17T08:00:03.456Z] [+3.46s] AFTER RECEIVE
Type: object
Content: "The capital of France is Paris."
Length: 32 chars
🐛 [2026-01-17T08:05:25.420Z] ⚠️ COMPACTION START
Pre-compaction tokens: 125000
Messages: 42
🐛 [2026-01-17T08:05:26.100Z] ✅ COMPACTION COMPLETE
Tokens removed: 80000
Messages removed: 35
🐛 [2026-01-17T08:10:00.000Z] SESSION END
Total session time: 600.00s
Features
📊 Detailed message previews (first 80 chars)
⏱️ Elapsed time since session start
🔧 Tool call and tool result tracking
📏 Message length and count statistics
⚠️ Compaction event visibility
🔍 Response type analysis
Use Cases
Debugging plugin development
Understanding CLI/SDK behavior
Tracking tool execution flow
Performance analysis
Learning how skills work
Diagnosing issues
Why a plugin?
This extends the CLI's capabilities beyond what GitHub provides natively. The CLI doesn't have verbose debug logging built-in, so this plugin:
Fills that gap for developers
Adds functionality GitHub likely won't build
Can be enabled/disabled on-demand
Complements the CLI, doesn't replace it
Testing
Would love feedback! Perfect for anyone developing plugins, debugging issues, or learning the SDK.
This has been fixed in v0.0.412. When a skill fails to load, the CLI now shows a warning in the timeline at startup and directs you to run /skills for a detailed breakdown of which skills failed and why. If you believe this isn't resolved, please feel free to reopen this issue.
Activity
ssfdre38 commentedon Jan 17, 2026
Solution Available: Debug Logger Plugin
I've built a plugin that adds comprehensive debug logging!
Plugin: debug-logger
Live now: https://github.com/barrersoftware/copilot-plugins-registry/tree/master/plugins/debug-logger
What it does:
How to use
Example Output
Features
Use Cases
Why a plugin?
This extends the CLI's capabilities beyond what GitHub provides natively. The CLI doesn't have verbose debug logging built-in, so this plugin:
Testing
Would love feedback! Perfect for anyone developing plugins, debugging issues, or learning the SDK.
Package: @barrersoftware/copilot-plugins
Registry: https://github.com/barrersoftware/copilot-plugins-registry
examon commentedon Apr 7, 2026
This has been fixed in v0.0.412. When a skill fails to load, the CLI now shows a warning in the timeline at startup and directs you to run
/skillsfor a detailed breakdown of which skills failed and why. If you believe this isn't resolved, please feel free to reopen this issue.