Description
When using opencode-mission-control commands (like /mc), the plugin throws an uncaught _MC_HANDLED_ error.
Error
cause: "Error: _MC_HANDLED_\n
at <anonymous> (/Users/sid/.cache/opencode/packages/opencode-mission-control@latest/node_modules/opencode-mission-control/dist/index.js:34153:20)\n
at processTicksAndRejections (native:7:39)\n
at Plugin.
trigger (/$bunfs/root/chunk-v9fhy29y.js:1033:1363)\n
at Plugin. trigger (definition) (/$bunfs/root/chunk-yb2r564e.js:687:10463) \n
at SessionPrompt.command (/$bunfs/root/chunk-qpygcnd1.js:3:13873)\n
at SessionPrompt.command (definition) (/$bunfs/root/chunk-v9fhy29y.js:1031:1800)\n
at SessionHttpApi.command (/$bunfs/root/chunk-qpygcnd1.js:2:79212)\n
at SessionHttpApi.command (definition) (/$bunfs/root/chunk-qpygcnd1.js:3:13783)"
Environment
- opencode-mission-control: 1.6.0
- OpenCode: latest
- tmux: 3.6b
- Git: 2.50.1
- OS: macOS (Apple Silicon)
Steps to Reproduce
- Install opencode-mission-control 1.6.0
- Use opencode with the plugin
- Attempt to call
/mc or related commands
- See
_MC_HANDLED_ error
Notes
- The error appears to be thrown inside
dist/index.js:34153:20
- Core functionality (like
mc_launch) seems to work, but some command paths trigger this uncaught error
- Jobs launched via
mc_launch continue running normally despite the error
Description
When using opencode-mission-control commands (like
/mc), the plugin throws an uncaught_MC_HANDLED_error.Error
Environment
Steps to Reproduce
/mcor related commands_MC_HANDLED_errorNotes
dist/index.js:34153:20mc_launch) seems to work, but some command paths trigger this uncaught errormc_launchcontinue running normally despite the error