FIG. 04 · Project · 2026
Wayline
A local runtime for AI coding agents with a Neovim client. The editor has one place to show a conversation, even when the provider underneath changes.

The problem
Each provider brings a different session model, event stream and set of controls. That makes changing providers an editor integration problem and makes it hard to tell which context accompanies a turn.
My role
I authored the runtime and Neovim client. The runtime handles the provider boundary and exposes a session and event model the editor can render.
The key decision
Keep provider-specific features behind adapters and expose their capabilities to the client. Make the context selection inspectable before a turn, so a file, selection or change is added deliberately.
The result
Wayline is in development. The local CLI already lets you inspect how context changes when you switch modes without sending a model request. The Neovim client uses the same runtime boundary for sessions.
Visual evidence
See what gets attached.
Context is a choice at the start of a turn. Compare the output of two modes in the same empty demo workspace.

01 / Demo capture
Start with no attached context
The local preview reports an empty context list in none mode. There’s no provider response in this capture.
View full size
02 / Demo capture
Add the workspace identity
Workspace mode adds a project entry. The output makes the distinction visible before any request is sent.
View full size Read the Wayline source