Cross-editor collaboration, live now

Live collaboration across
VS Code and IntelliJ.

We Code Live synchronizes project files, cursor presence, room chat, and approved terminal access while each participant continues working in their own editor.

Create your room Watch the product tour

Native files Durable rooms Explicit permissions

PRODUCT

A shared room in
both editors.

This example shows presence, concurrent editing, room discussion, and an explicitly approved terminal-control request.

Product tour · See the room

ROOM HEALTHY

inventory.ts ●stock.test.ts

src services inventory.ts

17
18
19
20
21
22
23
24
25

export async function reserveStock({ sku, quantity }) {
  const item = await inventory.find(sku)

  if (item.available < quantity) {
    throw new StockError(`Only ${item.available} left`)
  }

  return inventory.reserve(sku, quantity)
}

Maya · VS Code

Leo · IntelliJ

main*Ln 24, Col 18 UTF-8 TypeScript

JSON

Kotlin

YOUR PROJECT STAYS YOUR PROJECT

TypeScriptKotlinJavaPythonRustGo

WORKFLOW

How the shared workspace behaves.

Editors keep their native project model while the service coordinates files, messages, permissions, and recovery state.

NATIVE EDITING

Native project files in each editor.

Each collaborator works in their own project window with their own keymaps, plugins, and inspections. Changes converge through one shared model.

ROOM DISCUSSION

Chat messages and links to code.

Participants can send room chat and authorized code links without moving the discussion to another service.

SHARED TERMINAL

View output and request control.

Participants can view streamed terminal output. Input remains locked until the host grants a short, revocable control lease.

PRIYA REQUESTS CONTROL Grant once

CONNECTION RECOVERY

Resume from acknowledged operations.

Receipts, recovery journals, and persistent room state distinguish accepted work from changes that still need attention.

SERVER-ENFORCED AUTHORITY

Room permissions are verified by the service.

Read, edit, full-access, co-host, and publisher decisions are checked before durable changes are accepted.

SamOwnerMayaEditLeoRead

RECOVERY DIAGNOSTICS

Inspect connection and
authority changes.

Select a scenario to see how the client records a disconnection, a permission update, or concurrent document operations.

room diagnosticsLOCAL TRACE

$ wcl doctor --room current --trace recovery

09:42:18.104sockettransport interrupted

09:42:18.119journal17 local operations protected

09:42:20.806receiptserver watermark 2,841

09:42:20.912roomresumed · no replay ambiguity

RESOLUTIONRecovered without discarding accepted work.

OPERATING MODEL

Source synchronization,
not screen sharing.

Each participant edits native files in their own IDE. The room synchronizes project state and limits sensitive capabilities through explicit permissions.

Text, not pixelsSharp source at any connection quality.

Explicit consentRevocable grants for sensitive capabilities.

Operation receiptsKnow which changes the room accepted.

CREATE A COLLABORATION ROOM

Start a shared
workspace.

Create an account, open a room from VS Code or IntelliJ, and invite collaborators who use either editor.

Create your account View pricing