One SageFS Daemon, Every Client

One SageFS Daemon, Every Client An architecture diagram generated by Archify. VS Code · sagefs-vscode ext · Architecture component VS Code sagefs-vscode ext Neovim · sagefs.nvim · Architecture component Neovim sagefs.nvim AI Agents · MCP · streamable HTTP :37749 · Architecture component · Copilot / Claude AI Agents MCP · streamable HTTP :37749 Copilot / Claude Web Dashboard · :37750/dashboard · Architecture component Web Dashboard :37750/dashboard SageFS Daemon · one per machine · SageFS process tree · MCP :37749 · Dashboard :37750 SageFS Daemon one per machine MCP :37749 · Dashboard :37750 Session Worker · project A · FSI · SageFS process tree · own watcher Session Worker project A · FSI own watcher Session Worker · project B · FSI · SageFS process tree · own watcher Session Worker project B · FSI own watcher Session Worker · bare FSI · SageFS process tree · own watcher Session Worker bare FSI own watcher Supervisor · --supervised watchdog · SageFS process tree · exponential backoff Supervisor --supervised watchdog exponential backoff watchdog SageFS process tree Legend Frontend Backend Database Security External

Clients are thin

  • • VS Code, Neovim, Web Dashboard, and MCP agents all talk to one daemon
  • • Ports: MCP on 37749 (Streamable HTTP + legacy SSE), dashboard/SSE on 37750
  • • Each client keeps its own viewing-session identity; the dashboard does not follow another client's selection

Sessions are isolated workers

  • • Every session is a separate OS process with its own FSI, loaded project, and file watcher
  • • Workers cannot interfere with each other
  • • Hard resets use spawn-first restart: a replacement worker starts before the old one stops, so the session keeps serving during cold start

Crash-proofing

  • • sagefs --supervised runs under an Erlang-style watchdog
  • • Auto-restart uses exponential backoff
  • • The daemon API exposes watchdog state, and editor status bars show it