You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Contributors who work in VS Code have no one-click way to run T3 Code from a source checkout. Today you open a terminal, run vp run dev, find the pairingUrl: line in the output, and paste it into a browser. If the dev runner is left behind after VS Code restarts, you hunt for it by hand. The development runbook documents the steps, but nothing in the editor does them for you.
I searched Ideas for vscode, extension, and launcher and found nothing overlapping.
Proposed outcome
A small, optional, private extension at apps/vscode. It is not published and does not touch the product runtime.
Activity Bar icon. One click starts this checkout's dev runner (vp run dev) without a terminal and opens the app in VS Code's Integrated Browser, using the one-time pairing URL. On VS Code for the Web, which has no Integrated Browser, it opens a normal browser tab.
Stop and recover.Stop source server works while the server is still starting and stops only the process the extension started. If VS Code restarts an unresponsive extension host, the next start stops the server that was left behind.
Isolated state. Dev state lives under the selected checkout's .t3/vscode-dev, never in ~/.t3/userdata, which matches the repo's rule about not touching the live install.
Honest failures. If startup fails, the error links to a T3 Code Source output channel with the dev runner's log, with credentials redacted.
Plain JavaScript. It has no runtime dependencies and uses VS Code APIs only. It packages with vsce and installs from a VSIX.
It adds no server, contract, or client changes. It only runs the existing dev runner.
Out of scope: publishing to the Marketplace, controlling an installed desktop app, and any change to how the dev runner works.
Decisions requested
Home. Should this live in apps/vscode in this repo, or would you rather it stay in a separate repository? I'm fine either way.
Shape. Is a private, unpublished extension that only wraps vp run dev the right scope?
Docs. Should the setup steps go in docs/operations/development.md, or stay in the extension's own README?
Verification plan if approved
The launcher and extension logic have their own Node tests (node --test) covering the start, stop, recover, and failure paths.
A manual pass on VS Code desktop and VS Code for the Web, with screenshots of the Activity Bar view and the opened app.
A working version is on my fork, which is level with current upstream main: https://github.com/SiavZ/t3code/tree/main/apps/vscode. I won't open a PR here unless a maintainer approves the direction, and I'm happy to reshape or drop it.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Problem
Contributors who work in VS Code have no one-click way to run T3 Code from a source checkout. Today you open a terminal, run
vp run dev, find thepairingUrl:line in the output, and paste it into a browser. If the dev runner is left behind after VS Code restarts, you hunt for it by hand. The development runbook documents the steps, but nothing in the editor does them for you.I searched Ideas for vscode, extension, and launcher and found nothing overlapping.
Proposed outcome
A small, optional, private extension at
apps/vscode. It is not published and does not touch the product runtime.vp run dev) without a terminal and opens the app in VS Code's Integrated Browser, using the one-time pairing URL. On VS Code for the Web, which has no Integrated Browser, it opens a normal browser tab..t3/vscode-dev, never in~/.t3/userdata, which matches the repo's rule about not touching the live install.vsceand installs from a VSIX.It adds no server, contract, or client changes. It only runs the existing dev runner.
Out of scope: publishing to the Marketplace, controlling an installed desktop app, and any change to how the dev runner works.
Decisions requested
apps/vscodein this repo, or would you rather it stay in a separate repository? I'm fine either way.vp run devthe right scope?docs/operations/development.md, or stay in the extension's own README?Verification plan if approved
node --test) covering the start, stop, recover, and failure paths.A working version is on my fork, which is level with current upstream
main: https://github.com/SiavZ/t3code/tree/main/apps/vscode. I won't open a PR here unless a maintainer approves the direction, and I'm happy to reshape or drop it.Written with Claude Opus 5.5 in Jcode.
All reactions