-
Notifications
You must be signed in to change notification settings - Fork 24
All issues
Issue creation is restricted in this repository
Issues
is:issue state:open
is:issue state:open
Search results
Follow-ups from the #734 review: exit-hold observability, held-exit simplification, terminal-state predicate consolidation, CI-run JS exitCode test
enhancementNew feature or requestNew feature or requestStatus: Open.#735 In debugmcp/mcp-debugger;Bundled CLI: split main() out of src/index.ts so the bootstrap needs no env flag; e2e project is not run by CI
enhancementNew feature or requestNew feature or requestStatus: Open.#732 In debugmcp/mcp-debugger;js-debug child adoption: our launch/attach intent is written into parentConfig and stripped again by a deny-list in another package
enhancementNew feature or requestNew feature or requestStatus: Open.#730 In debugmcp/mcp-debugger;[FEATURE] DeepSeek Harness (dsh): document the mcp-client patch now, ship a bundle in the npm package once dsh's bundle contract is documented
enhancementNew feature or requestNew feature or requestStatus: Open.#728 In debugmcp/mcp-debugger;- Status: Open.#718 In debugmcp/mcp-debugger;
- Status: Open.#709 In debugmcp/mcp-debugger;
- Status: Open.#710 In debugmcp/mcp-debugger;
- Status: Open.#705 In debugmcp/mcp-debugger;
packages/adapter-ruby has no vitest.config.ts, so standalone per-package test runs fail at setup
bugSomething isn't workingSomething isn't workingStatus: Open.#696 In debugmcp/mcp-debugger;- Status: Open.#695 In debugmcp/mcp-debugger;
- Status: Open.#694 In debugmcp/mcp-debugger;
- Status: Open.#693 In debugmcp/mcp-debugger;