fix: resolve codemode providers before executor execution

[kentcdodds]

Summary

• resolve the codemode capability registry into a ResolvedProvider before calling executor.execute()
• keep the existing codemode namespace behavior while removing the deprecated raw function path

Testing

• npm exec -- tsc -p tsconfig.json --noEmit

  

Summary by CodeRabbit

• Refactor
  • Improved internal codemode provider architecture to enhance handler function management and execution flow.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: b4c0289c-e8aa-417c-8445-a1ec2cfe6583

📥 Commits

Reviewing files that changed from the base of the PR and between 8d04436 and 56ffa05.

📒 Files selected for processing (1)

• packages/worker/src/mcp/run-codemode-registry.ts

---

📝 Walkthrough

Walkthrough

A new buildCodemodeProvider function extracts registry-derived capability handlers into a normalized ToolProvider named "codemode". The runCodemodeWithRegistry function is refactored to use this resolved provider instead of a raw functions map during execution.

Changes

Cohort / File(s)	Summary
MCP Provider Refactoring packages/worker/src/mcp/run-codemode-registry.ts	Introduced new buildCodemodeProvider function that converts registry handler functions into a normalized ToolProvider. Updated runCodemodeWithRegistry to invoke the resolved provider instead of using a raw functions map.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

🐰 A provider is born from the registry's care,
Tools wrapped and normalized, handlers laid bare,
Old functions transform to a structure so clean,
The finest refactor this bunny has seen! ✨

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly describes the main change: resolving codemode providers before executor execution, which aligns with the primary objective and code modifications.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch cursor/codemode-provider-resolution-1e28

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[kentcdodds]

@cursoragent delete the test

[cursor]

Summary

• Deleted the codemode registry regression test per the GitHub instruction and removed its Vitest include entry, while keeping the runtime provider-resolution fix intact. run-codemode-registry.ts:1-64 vitest.node.config.ts:29-44
• Committed the removal as d3a4531 and pushed it to the PR branch.

Testing

• ✅ npm exec -- tsc -p tsconfig.json --noEmit — re-ran typecheck after removing the test to confirm the remaining implementation still compiles cleanly.
• ✅ git status --short && git log -2 --oneline — verified the new removal commit is on the branch; the only leftover uncommitted item is the unrelated untracked bun.lock.
• I did not perform manual testing because this follow-up only removed automated test coverage and left the server-side implementation unchanged; a targeted compile check was the highest-signal validation for this request.