Great point about sqlite-utils FTS. Saga already has full-text search via tracker_search across all entities (projects, epics, tasks, notes), but we're using basic LIKE queries — proper SQLite FTS5 indexes would be a meaningful upgrade for larger projects. Adding it to the roadmap.
The bugwarrior/syncall direction is interesting too. A github_sync tool that pulls issues into Saga's local tracker (and optionally pushes status back) would close the loop between local agent planning and team-visible issue trackers. Definitely something worth exploring.
Re: SWE-bench agents and issue tracking — most SWE-bench agents read the issue description as input but don't write back to GitHub. Having a local structured tracker that an agent can read/write freely (without API rate limits or auth concerns) is exactly the gap Saga fills.
I built an MCP server that lets Claude (or any MCP client) orchestrate structured debates between multiple LLMs.
You give it a topic, it sends it to all configured models in parallel, they see each other's responses, refine their positions over multiple rounds, and a synthesizer produces a final consolidated output.
Works with OpenAI, DeepSeek, Groq, Ollama, Mistral, Together — anything with an OpenAI-compatible API.
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.