How I turned VS Code Copilot into a LAN web hub to share Copilot access and usage budgets

Source: Dev.to

I wanted a practical setup: code on desktop, use Copilot from a second device, and keep prompt history organized as reusable and reviewable work assets. So I built Copilot Share, a VS Code extension that: Shares Copilot over LAN, with no cloud relay Supports optional access code protection Uses session-oriented workflows with built-in search, summary, clone, export, and import features In this post, I’ll show a 60-second setup and three real workflows: second-screen coding, workshop sharing, and review-ready session exports. Extension: https://marketplace.visualstudio.com/items?itemName=warlordy.copilot-share https://github.com/warlordy/vscode-extension-copilot-share I use Copilot most when I am already in a coding flow, but some of the best follow-up work happens away from the main keyboard. Sometimes I want to keep coding on my desktop and use a phone or tablet as a second screen for prompts, review, and quick experimentation. Instead of treating those prompts as one-off messages, I wanted them to be reusable work assets. That is what led to the session-oriented part of Copilot Share. Install Copilot Share from the VS Code Marketplace. Click the status bar item (Copilot Share) and select Start Sharing. Open Local Web on the host machine, or copy Public URL for another device on the same LAN. If access control is enabled, enter the access code in the browser. Start chatting in a browser. That is the whole idea: a simple local web hub for Copilot that is quick to start and easy to use on any device in the room. This is the workflow that motivated the project. I keep VS Code open on my main monitor and use a phone or tablet for prompts, follow-up questions, and quick rewrites. That lets me: Draft ideas without breaking concentration on the main editor Review Copilot responses on a separate screen Keep a longer conversation going while I stay focused in VS Code Because the web hub is LAN-first, there is no cloud relay setup in the middle. I start it from the status bar, open the web URL, and keep moving. Copilot Share also works well when one host machine needs to serve a small group. For example, in a workshop or team session, one person can host the extension in VS Code and others can connect from their own devices on the same local network. That makes it easier to: Demo a prompt workflow live Let attendees follow along on their own screens Share a single Copilot-enabled setup without asking everyone to configure the same environment When access control is needed, you can enable it with an access code so the chat APIs stay protected. This is where the session-oriented part becomes really useful. Instead of leaving a conversation buried in chat history, Copilot Share supports search, summary, clone, export, and import. That means a session can become something you revisit later, share with someone else, or export as a Markdown artifact for review. I find that especially useful when a prompt thread is doing real work, such as: refining a feature idea documenting a technical approach collecting implementation notes turning a rough prompt into a reusable template I did not want another complicated setup or a product that only works if everything is perfectly configured. I wanted the lowest-friction path possible: Start from the VS Code status bar Open a browser on the same network Keep prompts organized as sessions Make the result easy to review, export, and reuse That is the design goal behind Copilot Share. If this sounds useful, you can try it here: Marketplace: https://marketplace.visualstudio.com/items?itemName=warlordy.copilot-share

Source: https://github.com/warlordy/vscode-extension-copilot-share

If you do try it, I would love feedback on the setup flow, the session workflow, and whether the LAN-first approach fits your own use case.