Glia Guru is not for everyone. It is for developers who already use Obsidian for project management and want a visual planning layer and automated AI context files without migrating to another tool.
You use Claude, Cursor, or Windsurf daily.
You lose 20 minutes every session writing or updating CLAUDE.md context files. Your AI assistant keeps asking you to explain the project. The context files you wrote last week are already wrong.
Your vault is already the source of truth.
You manage projects from one Obsidian vault. Everything is there: sprint items, architecture decisions, session notes. But you can't see across projects without opening dozens of files.
You tried Linear. You tried Notion. You came back to markdown.
Every PM tool you adopt creates a second database you have to keep in sync with the actual work in your vault. You're done with that.
If you don't use Obsidian for project management, Glia Guru is not for you. That is a deliberate choice, not a limitation.
It's 9am. You open Cursor. The first thing your AI says is "Can you describe the project structure?" You paste in a CLAUDE.md you wrote three days ago. Half of it is already wrong. The feature you shipped yesterday isn't mentioned. The architecture decision you made on Tuesday isn't reflected. Your AI assistant starts the session with stale context, and you spend the first 20 minutes catching it up.
Now imagine the alternative. Before you open Cursor, Glia Guru has already read your vault. It knows what you shipped last week. It knows which tasks are open. It knows the architecture notes you updated yesterday. It generates a fresh CLAUDE.md, an AGENTS.md, and a Windsurf prompt file from your actual project state. Your AI assistant starts the session already informed.
That is what the AI context engine does. It reads your vault, understands the project state, and generates context files automatically. The files update when your project evolves. You never write CLAUDE.md by hand again.
Glia Guru indexes your vault's task files, architecture docs, and session notes.
The context engine generates CLAUDE.md, AGENTS.md, and agent-specific prompt files.
Your AI assistant starts every session with current, accurate project context.
It's Monday morning. You have three active client projects and two internal tools in development. Each has its own folder in your vault, its own task files, its own architecture docs. To figure out what matters this week, you open five sets of notes, grep for tags, cross-reference dates in frontmatter, and eventually build a mental model of the week ahead. By the time you start coding, you've lost 30 minutes to project archaeology.
Now imagine opening a single dashboard. Every task tagged across your projects is already on a visual board, pulled directly from your vault's markdown files. You see which project has overdue items, which one hasn't been touched in 11 days, and which has a task that's been in progress since last Tuesday. You drag, prioritise, and start the week in five minutes.
That is what the planner does. It reads your vault, surfaces the state of every project, and gives you a timeline, board, and list view. Changes you make in the dashboard write back to your vault as markdown frontmatter. No second database. No migration. No sync conflicts.
Timeline, board, and list views — all generated from the markdown files in your Obsidian vault.
Every project on one dashboard. See overdue items, stalled work, and active tasks without opening a single note.
Drag, prioritise, reschedule. Every change writes back to your vault as markdown frontmatter. No second database to keep in sync.
Glia Guru is built for the way you already work. Currently onboarding the first 100 vaults.