MobSession for VS Code / Cursor

Run a shared Claude Code session from your editor, drive it from an in-editor panel, and let your team watch and steer it live in the browser.

This extension is a thin host around the mobsession CLI. When you start a session it runs the MobSession daemon on your machine, in your workspace folder, mints a join link, and opens a panel in your editor with the live transcript. Your teammates open the link at mobsession.ai to follow along and add prompts. The agent runs on your computer with your files; collaboration happens through the shared session.

This is a separate VS Code / Cursor extension, not a Claude Code plugin. It wraps the MobSession daemon; it does not modify Claude Code.

Features

• Start a shared session from the MobSession view in the activity bar. It runs in your workspace folder.
• In-editor session panel: a live transcript of the agent's work plus a prompt box, so you can follow and steer the session without leaving the editor.
• Drive the session from the panel: answer or skip an AskUserQuestion, approve or reject prompts your teammates queue, interrupt the current turn, and toggle "trust all" (auto-approve everyone).
• Join a shared session: paste a control link a host gave you and drive their session from your own editor, with no local daemon.
• Share: copy the public join link for your team, or open the session in your browser.

Installing (VS Code or Cursor)

MobSession is a standard VS Code extension, and Cursor runs the same package. There is no separate Cursor build: install the same .vsix the same way in either editor.

1. Open the Command Palette (Ctrl/Cmd+Shift+P) and run Extensions: Install from VSIX..., then choose mobsession-vscode-<version>.vsix. (You can also drag the .vsix onto the Extensions panel.)
2. Reload the window (Command Palette → Developer: Reload Window) so the new build activates.
3. Install the CLI on your PATH (see Requirements): npm i -g mobsession.

Notes:

• The extension uses only standard editor APIs (the in-editor panel, commands, workspace settings, clipboard), all of which Cursor supports, so behavior is identical in both editors.
• Cursor's extension gallery (Open VSX) is not involved: you install the .vsix directly, so it does not matter which gallery the editor uses.
• After installing a newer .vsix, always reload the window so the updated panel bundle takes effect.

Requirements

• The MobSession CLI on your PATH: npm i -g mobsession (or set mobsession.command to an absolute path).

Use

1. Open the MobSession view in the activity bar.
2. Click Start a shared session. It starts in your workspace folder, and the session panel opens in your editor with the live transcript and a prompt box.
3. Copy join link and share it with your team so they can watch and steer from mobsession.ai. Open in browser opens your private host link if you would rather drive it from a browser tab.
4. From the panel you can send prompts, answer the agent's questions, approve or reject queued prompts, interrupt a turn, and toggle trust.
5. Stop session ends it.

To join someone else's session: run MobSession: Join a shared session from the Command Palette and paste the control link they sent you. The panel opens connected to that session. (The control link contains a secret, so it is entered in a hidden input and never written to logs or settings.)

Settings

• mobsession.command: the CLI to run (default mobsession).
• mobsession.webUrl: web app base URL the join link points to (default https://mobsession.ai).
• mobsession.convexUrl: the backend deployment the in-editor panel connects to. It must match the deployment the CLI uses; only change it for local development.
• mobsession.openOnStart: open the session panel in the editor automatically when a session starts (default true). Use Open in browser to view it in a browser instead.

command, webUrl, and convexUrl are machine-scoped, so a workspace you open can never change what runs or where the panel connects.

Security

The session runs on your machine, in the folder you start it in, under your account. The extension refuses to start a session in an untrusted workspace. The host control link is a private credential: keep it to yourself, share only the public join link with your team.