Set up Copilot

Worsley captures Microsoft Copilot in your browser, through the extension:

• copilot.microsoft.com and copilot.com.
• Microsoft 365 Copilot on the web, at m365.cloud.microsoft, microsoft365.com and office.com.

Set it up in your browser

1. 1Get the Worsley extension from the Install Extension page. It's in the Chrome Web Store; for Firefox, join the waitlist there for early access. It works in Chrome, in Chromium browsers such as Edge, Brave, Arc, Opera, Opera GX and Vivaldi, and in Firefox.
2. 2Pin it to your toolbar: open the extensions menu (the puzzle-piece icon) and pin Worsley, so its status is one click away.
3. 3In the same browser, log in to Worsley, or create an account if you don't have one yet.
4. 4Open Settings > Connection and select Connect. The extension is now tied to your account, and This Browser shows as Capturing.
5. 5If the Worsley icon says No Site Access, select it and choose Allow Access. Worsley needs access to Copilot and Microsoft 365 on the web to capture, and to nothing else you browse.
6. 6Open Copilot and sign in. If a Copilot tab was already open before you installed the extension, reload it.
7. 7Have a conversation as you normally would. Worsley captures each turn as it finishes.

Using a work or school account? Sign in to Microsoft 365 as usual. Your organization's policies can block browser extensions; if Worsley can't be installed, ask your IT team.

Check that it's working

• Open History in Worsley. Your session shows up there with the tool's name, usually within a minute of a finished turn.
• Select the Worsley icon on a Copilot tab: it shows the conversation you're in and its suggestions once a prompt is analyzed.

What's captured

• Your prompts and Copilot's replies, turn by turn.
• Details of files you attach (name, type and size, not their contents).

GitHub Copilot in VS Code

GitHub Copilot is a different product from Microsoft Copilot, and Worsley can capture its chat panel in VS Code too, through the Worsley CLI. Sign in to the CLI as below, then turn it on. Worsley reads only VS Code's chat history, inside VS Code's user folder.

Sign in to the Worsley CLI

Do this once on each computer where you run VS Code.

1. 1Install the Worsley CLI. It runs on macOS, Windows and Linux and needs Node.js 22.23.4 or later (on a Mac, brew install node works too). On macOS or Linux, run:

curl -fsSL https://www.worsley.ai/install.sh | sh

On Windows, in PowerShell:

irm https://www.worsley.ai/install.ps1 | iex

The installer checks the download against its published checksum, puts the CLI in your home folder (~/.worsley, or %LOCALAPPDATA%\Worsley on Windows) and adds it to your PATH. Open a new terminal window afterward so the worsley command is found. Run the same command again any time to update.

1. 1Sign in. The command below prints a link and a short code, then waits.

worsley login

1. 1Open the link. Log in to Worsley if asked, check that the code on the page matches the one in your terminal and that it names this computer, then select Connect. If you last logged in more than 10 minutes ago, Worsley asks you to log in again first. Opened the page without the code? Type it in.
2. 2Back in the terminal, Worsley confirms Signed in as your email. The sign-in is kept in your system's credential store (macOS Keychain, Windows Credential Manager or Secret Service on Linux), never in a plain file. The code expires after 10 minutes; run worsley login again if it does.

worsley enable vscode-copilot

Using VS Code Insiders? Pass its folder: on a Mac, worsley enable vscode-copilot --dir "$HOME/Library/Application Support/Code - Insiders/User". Then run worsley watch (or worsley sync) to upload, as for any terminal tool.

If a session doesn't appear

• Browser: check that the Worsley icon isn't showing Not Connected, Reconnect or No Site Access, and reload the tool's tab. More in Extension isn't capturing.
• Terminal: check that worsley watch or worsley proxy was running while you worked, and run worsley status. If it says the sign-in was revoked or expired, run worsley login again.
• Still missing after a few minutes? Contact support and tell us which tool and which browser or terminal you used.