The problem
If you use Obsidian for project management, you know the maintenance tax. Community plugins break on update. Dataview queries become their own project. You spend more time configuring your vault than managing work.
If you use AI coding agents, you know the context gap. Every new session starts with the agent asking what happened since last time. You end up manually updating CLAUDE.md, AGENTS.md, and project specification files between sprints, which is exactly the kind of repetitive, structured work you bought the AI to avoid.
Glia Guru is the dashboard layer for tools you already trust. It reads your Obsidian vault, syncs with your Supabase instance, and generates AI context files automatically when you update tasks, move cards, or define requirements. Your data never leaves your infrastructure. Guru is the intelligence layer, not the storage.
What it does
You provide your Obsidian vault and Supabase instance. Glia provides the orchestration, the views, and the AI context engine. No vendor lock-in. No data capture. If you leave, your data stays exactly where it always was: on your machine and in your database.
When you move a Kanban card, update a requirement, or close a task, Guru translates those actions into structured, token-aware context files optimised for your AI platform. Supports Claude, ChatGPT, Gemini, Cursor, and Windsurf at launch.
Kanban, timeline, table, and calendar views generated directly from your markdown frontmatter. Drag a card, and the frontmatter updates. Change a date in the file, and the timeline reflects it. No query language, no configuration, no Dataview.
Real-time connection monitoring, frontmatter validation, and schema integrity checks across your vault and Supabase instance. When something breaks, Guru tells you exactly what went wrong and where, instead of showing you an opaque error code.
A small number of operating teams are being onboarded each month.
Request accessFrequently asked
An Obsidian vault with markdown files. For cloud sync and cross-device access, a Supabase account. For AI context generation, API keys for your preferred platform. Guru orchestrates what you already have.
No. Guru is a stateless dashboard layer. It reads from your local vault and your Supabase instance. Your data stays in your infrastructure, always.
Claude, ChatGPT, Gemini, Cursor, and Windsurf at launch, with more to follow. The context files are plain markdown, so they work with any tool that reads text files.
Obsidian plugins are community-built, individually maintained, and often fragile across updates. Guru is a managed platform that uses Obsidian as a storage backend. No plugin maintenance, no configuration debugging, no Dataview queries. One product, one team behind it.