Interesting approach using SQLite as the persistence layer for AI agents. The local-first architecture makes a lot of sense for development workflows where latency matters.
One question: How do you handle concurrent writes from multiple agents working on the same project? SQLite has WAL mode, but I'm curious if you've encountered any race conditions in practice, especially when agents are running in parallel.
Also, the MCP (Model Context Protocol) integration is clever - having a standardized way for agents to query project state could really simplify the orchestration layer. Are you seeing other teams adopt MCP for similar use cases?
SQLite handles this well in practice. saga-mcp uses WAL mode with busy_timeout=5000 and synchronous=NORMAL, so concurrent writes queue up rather than fail. The intended use case is one agent per project per session — if you had multiple agents writing to the same .tracker.db, WAL mode serializes the writes transparently.
For MCP adoption — it's growing fast. Claude Code, Claude Desktop, Cursor, and Windsurf all support it natively now. The spec is simple (JSON-RPC over stdio or SSE), so the barrier to both building and consuming MCP servers is low.
Interesting approach using SQLite as the persistence layer for AI agents. The local-first architecture makes a lot of sense for development workflows where latency matters.
One question: How do you handle concurrent writes from multiple agents working on the same project? SQLite has WAL mode, but I'm curious if you've encountered any race conditions in practice, especially when agents are running in parallel.
Also, the MCP (Model Context Protocol) integration is clever - having a standardized way for agents to query project state could really simplify the orchestration layer. Are you seeing other teams adopt MCP for similar use cases?
Thanks for your valuable feedbacks.
SQLite handles this well in practice. saga-mcp uses WAL mode with busy_timeout=5000 and synchronous=NORMAL, so concurrent writes queue up rather than fail. The intended use case is one agent per project per session — if you had multiple agents writing to the same .tracker.db, WAL mode serializes the writes transparently.
For MCP adoption — it's growing fast. Claude Code, Claude Desktop, Cursor, and Windsurf all support it natively now. The spec is simple (JSON-RPC over stdio or SSE), so the barrier to both building and consuming MCP servers is low.