[flagged]
Lat.md: Agent Lattice: a knowledge graph for your codebase, written in Markdown
31–40 of 70 posts
Re: Lat.md: Agent Lattice: a knowledge graph for your codebase, written in Markdown
#32At that point why not have an obsidian vault in your repo and get the Agent to write to it?
I was thinking the same. Especially now that Obsidian has a CLI to work with the vault.
The one thing I saw in the README is that lat has a format for source files to link back to the lat.md markdown, but I don't see why you couldn't just define an "// obs:wikilink" sort of format in your AGENTS.md
Re: Lat.md: Agent Lattice: a knowledge graph for your codebase, written in Markdown
#33So... does it work? Good description of what it does, but, does it actually make agents better, or use less tokens? What's the benchmark?
Re: Lat.md: Agent Lattice: a knowledge graph for your codebase, written in Markdown
#34So... does it work? Good description of what it does, but, does it actually make agents better, or use less tokens? What's the benchmark?
I'm working on a blog post about lat, stay tuned. Yes, it does work and I continue improving it.
Re: Lat.md: Agent Lattice: a knowledge graph for your codebase, written in Markdown
#35tl;dr: One file, bad (gets too big for context) So give you agent a whole obsidian I am skeptical how that helps. Agents cant just grep in one big file if reading entire file is the problem.
The problem is that for any non-trivial question agents have to grep A LOT to understand the high-level logic expressed in code. In big projects grepping can take minutes some times. Lat short-circuits grepping significantly with `lat search` that agents happily use.
Re: Lat.md: Agent Lattice: a knowledge graph for your codebase, written in Markdown
#36So... does it work? Good description of what it does, but, does it actually make agents better, or use less tokens? What's the benchmark?
I'm working on a blog post about lat, stay tuned. Yes, it does work and I continue improving it.
Cool. I've been thinking about tools to help coding agents lately, and I've always wondered if I could do a better job than actual Claude Code / Codex. They can do the `rg`s and kick off multiple agents and the skills, etc, and I couldn't find a way to actually prove there's a ROI of using something like Agent Lattice. Curious to see the results!
Re: Lat.md: Agent Lattice: a knowledge graph for your codebase, written in Markdown
#37This is one of the things that GitHub Spec Kit solves for me. The specify.plan step launches code exploration agents and builds itself the latest data model, migrations, etc etc. Really reduces the need to document stuff when the agent self discovers codebase needs.
Give Claude sqlite/supabase MCP, GitHub CLI, Linear CLI, Chrome or launch.json and it can really autonomously solve this.
Re: Lat.md: Agent Lattice: a knowledge graph for your codebase, written in Markdown
#38[flagged]
> My concern is scale though. Once you have thousands of nodes the Markdown files themselves become a mess to navigate
The agent will update the graph.
If you have thousands of nodes in md it means you have a highly non-trivial large code base and this is where lat will start saving you time - agents will navigate code much faster and you'll be reviewing semantic changes in lat in every diff, potentially suggesting the agents to alter the code or add more context to lat.
You still have to be engaged in maintaining your codebase, just at a higher level.
Re: Lat.md: Agent Lattice: a knowledge graph for your codebase, written in Markdown
#39> "chalk": "^5.6.2", security.md ist missing apparently.
Why would you even need chalk on modern Node.js? It can style natively now.
Re: Lat.md: Agent Lattice: a knowledge graph for your codebase, written in Markdown
#40> "chalk": "^5.6.2", security.md ist missing apparently.
Fixed