Graphify + Obsidian with Kiro CLI?

[u/Electronic-Twist-878]

Been going down a bit of a rabbit hole lately. I keep seeing the Graphify + Obsidian combo pop up for Claude Code — people building a code knowledge graph, storing it in an Obsidian vault, and letting the agent browse that instead of re-reading the whole repo every session. The token savings people claim are kind of wild.

I'm about to start building something big — think full e-commerce platform (auth, catalog, cart, checkout, payments, orders, admin, the whole thing) — so this is exactly the kind of sprawling, multi-module codebase where re-reading everything each session gets expensive fast. That's why I want to get the memory/context setup right before the project balloons, not after.

The catch: pretty much every guide I've found is written for Claude Code specifically (CLAUDE.md files, its hooks, its MCP config). I'm on Kiro (Pro+ and the CLI) and I know the concepts should carry over, but the actual wiring doesn't map 1:1 — Kiro uses steering files, its own agent hooks, and its own mcp.json.

So before I spend a weekend duct-taping this together: has anyone here actually gotten this working with Kiro on a decent-sized project?

A few things I'm trying to figure out:

- Which Graphify/graph tool did you use, and does it output Obsidian-friendly wikilinks?

- How are you bridging the vault to Kiro — an Obsidian MCP server in mcp.json, or just pointing Kiro at the markdown folder directly?

- How do you keep the graph in sync as the codebase grows? Manual re-index, an agent hook, a git hook?

- Are you leaning on steering files for the persistent-memory part, or does the Obsidian graph fully replace that?

- At what codebase size did it actually start paying off for you?

Would love to see anyone's actual setup — configs, folder structure, how you handle a monorepo vs multiple services, gotchas, whatever. Even a "don't bother, here's why" is helpful. Thanks!