The extension for VS Code, Cursor, Windsurf and Kiro

The wickrunAI extension brings live documents into the editor you already use. Open a file from a project that works in a cloud workspace: the side view shows who else is in the file, everyone's cursor appears in the editor, and the version history sits next to the code. Nothing about the project changes: no files are copied, no settings are imported, and your keys and theme stay the editor's own.

Install

The extension ships as a VSIX file with every release (wickrunAI-<version>-vscode.vsix); download it from the attachments on the wickrunAI releases page. It is not on an extension marketplace yet.

Editor	In the editor	In a terminal
VS Code	Extensions view → `···` → Install from VSIX… → pick the file	`code --install-extension wickrunAI-<version>-vscode.vsix`
Cursor	Command Palette → Extensions: Install from VSIX…	`cursor --install-extension wickrunAI-<version>-vscode.vsix`
Windsurf	Command Palette → Extensions: Install from VSIX…	`windsurf --install-extension wickrunAI-<version>-vscode.vsix`
Kiro	Command Palette → Extensions: Install from VSIX…	`kiro --install-extension wickrunAI-<version>-vscode.vsix`

To update, install the newer VSIX the same way. Remove it from the Extensions view like any other extension.

Sign in once

With the desktop app running (recommended): run "wickrunAI: Sign in", or click wickrunAI in the status bar. The editor shows a six-letter code and the desktop app asks whether this editor may use your wickrunAI account to open live documents; if the codes match, allow it. From then on the editor uses the same account through the desktop app and never sees the desktop's sign-in.
Without the desktop app: the same command opens the browser sign-in (sign in with Google, then enter the code shown in the editor).

To disconnect every editor at once, choose File → Revoke editor access in the desktop app. Editors also disconnect when the desktop app signs in to another account, and a pairing needs confirming again after 30 days.

Which files become live documents

Projects that work in a cloud workspace: if a wickrunAI project uses this folder as its working folder and has its cloud workspace on, the text files in it are live documents.
Without the desktop app: run "wickrunAI: Link this folder to a cloud workspace" and paste a link to any live document in that workspace. The link is kept in the editor, never in the project.
Links: a live document with no file here, such as a Drive file or a file in a shared conversation, opens straight from its link; typing syncs as you go and there is nothing to save.

What you see

The side view: the file, the connection state and who is in the file (people as round avatars, agents as square avatars with a robot badge), with "editing" next to whoever is typing. Below it, the version history: compare with the current text or compare two versions; "Restore this version" asks first and creates a new version, so nothing is lost; "Name a version" labels the current state.
In the editor: other members' cursors and selections in their colours, with name tags that fade a few seconds after they stop.
The status bar: how many people are online, reconnecting or offline; click it to open the side view.

Edits by the editor's own agent

When the agent in Cursor, Windsurf, Kiro or another AI editor changes a file, the edit is signed "R's Cursor" (R is your name) and shown apart from what you typed. It is the same member as that agent coming in through MCP.

Editors do not tell the extension which edits came from their agent, so the extension judges from what you are doing: typing, pasting or undoing at your cursor is you; an edit while the window is in the background, in a file that is not the active one, or away from every cursor is the agent. Replace-all also counts as the agent; if that distinction does not matter to you, turn off the wickrun.agentAttribution setting.

Your existing rules keep working

The first time the extension starts in a folder, if it finds rule files such as AGENTS.md, CLAUDE.md or .cursor/rules, it says once that Butler follows these rules. It only checks that they exist; it does not copy, import or change them.

Links and the wickrun command

Link	Opens
`wickrun://doc/<document ID>`	the live document in the wickrunAI desktop app
`wickrun://open?folder=<path>`	the project that works in that folder
`vscode://wickrun.wickrunai/open?doc=<document ID>`	the live document in VS Code (`cursor://`, `windsurf://` or `kiro://` for the others)

The desktop app includes a wickrun command. Add it to your PATH once:

macOS: ln -s "/Applications/wickrunAI.app/Contents/Resources/cli/wickrun" /usr/local/bin/wickrun
Linux (deb): sudo ln -s /opt/wickrunAI/resources/cli/wickrun /usr/local/bin/wickrun
Windows: add %LOCALAPPDATA%\Programs\wickrunAI\resources\cli to your user Path

wickrun open .          # the project that works in this folder
wickrun doc notes/plan.md  # this file's live document
wickrun link notes/plan.md # print the link only
wickrun acp             # an ACP agent for Zed, JetBrains and Neovim

See the ACP guide for wickrun acp.

Limits you may run into

Only text files are edited live. .env and other secret files, binary files and files over 8 MB stay ordinary files; folders in Restricted Mode are not connected.
Documents in encrypted spaces are not edited in the extension; the side view offers "Open in wickrunAI".
Spreadsheets and files edited one person at a time (such as pptx and docx) open in wickrunAI.
The extension does no masking; masking happens only in the desktop app.
If the server turns down a batch of changes, the document is reopened, the rest of your text is kept, and a notification lets you copy what was turned down.