4 ms·

At that point why not have an obsidian vault in your repo and get the Agent to write to it?

• deleted 7mo ago
  [deleted]
• dangoor 7mo ago
  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
• 1st1 7mo ago
  Because lat gives agents more tools and enforces the workflow. Unlike obsidian, lat allows markdown files link into functions/structs/classes/etc too. This saves agents time on grepping but also allows you to build better workflows with tests. Test cases can be described as sections in `lat.md/` and marked with `require-code-mention: true`. Each spec then must be referenced by a `// @lat:` comment in test code. `lat check` flags any spec without a backlink, so you can review and maintain test coverage from the knowledge graph.
  • afzalive 7mo ago
    This is interesting. I've been using a system-wide Obsidian vault that all my agents use for stuff that's platform-specific instead of project specific (think common Android/Samsung-related or ANR fixes). So far, it hasn't been mind-blowing but it's only been a month so its knowledge from there is also limited. lat seems like it could be useful to cross-reference company-wide projects.
    • 1st1 7mo ago
      potentially. I'm toying with the idea of distributed lat ;)