Sync engine
How local first reads work under the hood.
Reads in VoidTrack are local first, in the same spirit as Linear: ElectricSQL streams team scoped Postgres shapes into a TanStack DB store in the browser, so pages read local data and update live as changes arrive.
How requests are multiplexed
The server multiplexes every table's shape over a single SSE connection at /api/sync. It holds the Electric streams server side and fans changes out to the browser, so a client pays for one connection regardless of how many tables it subscribes to. The same team access rules that guard the REST API are enforced here too, server side. Clients never talk to Electric directly, a per shape debug proxy remains available at /api/electric/shape for inspection.
Writes stay in one place
Writes go through the REST API and flow back into the browser through sync. That keeps the API, and by extension the MCP server, canonical for agents: nothing writes straight to the sync layer, so an agent using the MCP tools sees the exact same effects a human using the web UI would.