EDITOR INTEGRATION
Sykes VCS Editor Plugins
Sykes VCS Editor Plugins connect real editing environments to the Engine. They observe source edits where they happen and preserve enough structure for those edits to become CRDT operations instead of only opaque saved-file diffs.
The editor-facing edge of Sykes VCS
Editor Plugins sit between development tools and the Sykes VCS Engine. They capture source edits and send those changes into the Engine in the shape required for structured operation history.
- Emit edit operations instead of only saved-file snapshots.
- Preserve the source and shape of an edit.
- Keep editor-specific APIs outside the Engine itself.
Starting with Neovim
Neovim is the first editor target because it is the environment being used while Sykes VCS is built. The prototype communicates documents and operations such as insert, delete, undo, and redo into the Engine.
- Neovim is the current practical integration target.
- Other editor targets remain to be decided.
- Browser-editor support is not currently planned.
Keystrokes, paste, formatters, and refactors
A plugin must handle both small edits and large generated changes. Typing one character, pasting a block, running a formatter, or applying a refactor should all produce Engine input without collapsing into disconnected file snapshots.
- Keystrokes can map to small insert or delete operations.
- Larger edits can become larger operations or grouped changes.
- Editor context helps preserve useful structure.
Agents need structured interfaces too
Coding agents are not editor plugins, but they need a related path into the same Engine. The existing opencode prototype proves that automated changes can participate in the structured history while retaining their own identity.
- Agent changes use the same Engine operation model.
- Agent work can be grouped into larger tasks.
- Future agent and CLI interfaces remain separate from editor-specific adapters.
Prototype plugins exist, local proof is next
The plugin work is still early. The Neovim and opencode prototypes prove parts of the path, while the next major proof point is a complete local Neovim, opencode, and Sykes VCS flow.
- Current integrations are prototypes, not polished releases.
- The editor contract still needs a stable public surface.
- Filesystem watchers alone do not provide the required fidelity.
NEXT STEP
Editor Plugins connect real tools to the Engine
The Sykes VCS Engine defines the CRDT rules. Editor Plugins connect those rules to editing environments so source changes can enter the system when they happen.