Integrations
Leyline connects the Vue interface to pi runtimes, bundled extensions, local SQLite data, and a PTY terminal.
- pi SDK integration covers session discovery, runtime actions, JSONL history, and native Settings integration.
- Elune integration covers embedded capture, private local storage, usage accounting, trace views, and host routes.
- Memory integration covers durable context, the Memory Inspector, and rollout feedback.
- Subagent integration covers agent definitions, model overrides, and child sessions.
- Deep research integration covers research-session binding, parallel workers, persisted source state, and citation checks.
- Vision agent integration covers image delegation, scoped model selection, and context replacement.
- Terminal backend covers the PTY WebSocket.
- API reference lists all HTTP and WebSocket contracts.
Bundled runtime resources
Normal runtimes load the bundled output-budget, ultrafast, memory, subagent, research, and vision-agent extensions. Conversation runtimes also install inline Elune capture. Isolated custom-prompt children retain output-budget and inline capture.
Leyline also uses pi's native MCP and tool search. It does not load Codemode. See Runtime construction for conflict filtering and Ultrafast for tier behavior.
Normal runtimes also append .pi/LEYLINE_SYSTEM.md to the system prompt. This prompt describes Leyline's operating context. It does not replace pi or project instructions.
Local metadata
Backend connections, display and file-editor settings, memory, rollout feedback, and subagent/vision overrides use SQLite under ~/.local/share/leyline/. Pi session history remains in JSONL files.
Display and saved connections belong to the native app backend. Agent defaults, Project settings, and Session details edit overrides on the selected backend at fixed scopes.
Trace records use a separate elune/elune.db on the selected backend. Capture configuration stays in memory.sqlite as tracing.enabled. Explorer spans projects on that backend. It does not aggregate saved connections.
Models & providers and MCP servers require piSettings and use pi-owned global files on the selected backend. Provider/model configuration, MCP configuration, and native credentials do not use SQLite. See Settings integration for the SDK boundary and Pi Settings routes for the supported API.
See SQLite metadata for the table inventory and Environment variables for storage overrides.
Browser and Electron servers
Browser development and packaged Electron use the same backend modules. Each window can select a saved backend. See Architecture for startup paths and transport routing.