Multiplayer and Follow mode

One workspace, several people. vector invite starts your workspace as a shared server and prints two links: your own, and an invite link for teammates. Anyone who opens the invite lands in the same Vector UI, on the same sessions, files, and agents, as a guest. The header shows who is present, and a short "joined" or "left" notice when someone comes or goes.

The invite link

How the link works

The invite carries a guest password that is generated fresh each time you run vector invite. Guests are a separate credential from you, so revoking access is as simple as ending the session with Ctrl+C.

Where it works

On a network you trust, run vector invite --hostname 0.0.0.0 (from the next CLI release, add --trusted-network) and share the link it prints for your network address; the link carries the guest password over plain HTTP, which is why the network has to be one you trust. From the next CLI release you can instead keep the server local, expose its port through a TLS tunnel — tailscale serve <port> or cloudflared tunnel --url http://localhost:<port> — and pass that address with --public-url https://your-host.

What guests can do

Read and steer sessions in that workspace, open its files, and run the agent. From the next CLI release, terminals, direct shell commands, slash commands, commits and branch switches (they run the repository's git hooks), and answers to permission requests stay with you, and a guest cannot write inside .git or give a session more permissions than your rules do; the npm CLI (1.99.99) and the vectordev.ai/install build do not enforce these yet. From the next CLI release, a spend limit a guest sends can only lower a run's limits, never raise the ones your config or your own prompt set, and the usage totals a guest can read cover only that workspace. From the next CLI release, a guest is not offered free models labelled “May train on your prompts”, and once a guest has worked in a session, nothing from that session goes to one, your own prompts included. vector invite runs from the CLI, so the desktop 1.99.108 update does not bring this to the npm CLI (1.99.99) or the vectordev.ai/install build.

Your own coding agents stay yours

Claude Code, Codex and the other agents you start from Host locally run on your computer, signed in to your own accounts, so a guest can't see, start, message or resume them, or open the terminal one runs in. A guest can't reach them through your agent teams either: teammates' messages don't reach these agents.

What the agent does for a guest

The agent a guest steers runs on your machine under your permission rules: whatever they let it do without asking, it does for the guest too. Vector's default rules let the agent run shell commands without asking, so a guest can have it run commands as you. When the agent does ask, for example before it reads a file outside the workspace, only you can approve. Setting "bash": "ask" before you invite makes the agent ask you before each shell command, but a guest can still change the workspace's files, and with them code your tools run later, such as a formatter's or language server's config or a script you run yourself. Share the link only with people you would trust at your keyboard.

Follow mode

Watch the agent type. With Follow mode on, the editor opens whatever file the agent is editing, scrolls to the lines it changed, tints them in that agent's colour, and places a labelled caret at the end of the edit. Every edit is attributed to the agent that made it, so a session with several agents reads like a shared document with named cursors.

Turn it off when you are typing

The eye button in the Codespace toolbar, or Settings → General → "Follow the agent in the editor". Off, the agent's edits to the file you have open are still highlighted; other files stay closed until you open them.

What it never does

Your own saves, build output, and formatter runs do not move the editor. Only edits published by an agent do.