Mods vs Cursor and VS Code extensions
Different places to extend your workflow
A Claude Code mod extends the Claude session. A VS Code extension extends the editor host; Cursor also provides editor features and its own agent workflows. Similar-looking UI does not imply compatible APIs. Reusing a TypeScript file alone does not port an extension.
| Question | Claude Code mod | Editor extension |
|---|---|---|
| Where does it run? | Claude Code mod runtime | The editor's extension host |
| What does it target? | Session events and supported UI surfaces | Editor commands, documents and views |
| What must be checked? | Installed CLI declarations and permissions | Editor API, version and extension permissions |
| What can be shared? | Pure logic and documented contracts | Pure logic and documented contracts |
Pick the surface you use
For a terminal session counter, a mod keeps the information near the conversation. For an editor document action, an editor extension may have the closer integration. If the workflow spans both, separate reusable logic from the host adapter; do not assume Node, DOM or editor APIs exist in the mod sandbox.
Port in small steps
Write down the triggering event, required state, display and cleanup behavior. Port one read-only feature first. Then verify command semantics, keyboard access and failure handling on the supported surface. Review network and file access again because permissions do not transfer across hosts.