Livebuf

Livebuf keeps one shared copy of each open file between people using VS Code or Cursor. When two people who can see the same GitHub repository open the same file, typing in one editor shows up in the other, with each person's name on their cursor.

You do not send an invite link. Access follows the repository. If GitHub lets someone see the project, and they have Livebuf installed and signed in, they are in the same session. On a public repository that means any logged-in GitHub user. On a private repository it means only the accounts that can already open it.

Start

Install Livebuf (syncline.livebuf), then open the Livebuf icon in the activity bar.

1. Choose Connect GitHub and approve the editor's GitHub login.
2. Open the project folder. Its git remote must be a GitHub repository.
3. Livebuf joins that repository. If it does not, choose Join this repository.
4. Open a file. Anyone else who can see the repository, with Livebuf connected, opens that same file and the edits meet.

The sidebar lists who is connected right now. Leave stops your editor from syncing until you join again. The same actions are in the Command Palette under Livebuf.

Agents

A person types directly into the shared file. An agent does not. It submits a proposal, and the sidebar shows Accept and Reject on that proposal. Pause agents stops new proposals.

A coding agent can also connect locally. Livebuf asks once whether to allow it for the current workspace. When two connected agents plan or change the same files, they coordinate privately. Both people then see one plan and choose Accept plan, Try another idea, or Cancel. Both people must accept before either agent proceeds on its own branch.

Livebuf does not use your Cursor, OpenAI, or other model login. An agent is a separate program that speaks Livebuf's protocol. The sample program in the repository is one of those.

Server

A new install uses the public Livebuf server. To point at another server, set Livebuf: Server URL. A local development server is ws://127.0.0.1:8787.