[tarr1124]

Obsidian and these newer tools share markdown + local files, but they're aimed at different assumptions about who reads and edits the vault. Obsidian's default is "human reads and curates; plugins optionally enhance." The AI-first cohort (Tolaria, Sig in the sibling comment, and several others) assumes the AI reads and writes as a first-class agent, which makes design choices like how the app reacts to files changing underneath it (cf. the Zettlr comment downthread) a core concern rather than an edge case.

Worth watching how each of these tools positions the AI: as a UX copilot inside the editor, or as an autonomous agent with file-system access via local CLI/MCP.

[fiatpandas]

It would be nice if you could “see” the AI in your vault making changes. Almost like a Google doc collab session. Even if you weren’t directly interacting with the agent, and it was making change thru a CLI/MCP, its presence would be highlighted in the frontend. And then it appears as its own contributor in the git history.

[tarr1124]

Git is great as the durable layer, but what fiatpandas is pointing at is a bit different — real-time awareness that the agent is active right now, not a retrospective diff.

I've been working on this split in a side project (https://github.com/rillmd/rill — vault layer on top of Claude Code). Git still handles the durable side for free, since the CLI agent just writes files and commits normally. The live side comes from Claude Code hooks (UserPromptSubmit / Stop / PostToolUse) appending to a plain activity-log.md that the Electron GUI tails. Cruder than Google Docs cursor presence, but cheap — and the log itself is just another markdown file in the vault, same data model as everything else.

One trade-off: going the other direction and letting the frontend detect edits via FSEvents-style watching runs straight into the reconciliation issues the Zettlr subthread is about. Hooks on the agent side are less elegant but sidestep the whole class.

[CrompyBlompers]

Respectfully, did you use an LLM to write this comment? You're responding to flatpandas here. Having "what flatpands is pointing at..." is similar to the output of an LLM if you were to link to that comment and get a generated summary.

[tarr1124]

I wrote it. English is my second language, so I reach for "what X is pointing at" constructions a lot — partly as a self-check that I've parsed the parent correctly. If any specific claim in there looks wrong or generated, happy to have it pointed out.

[CrompyBlompers]

Gotcha, thx for the context.

Typically we'd see the second person "you/your/you're" used and not the third person ("flatpands") here, since you (tarr1124) are directly responding to their comment, as if in conversation with them. ie: "what you're pointing at..."

Otherwise it reads like you're ignoring them and talking around them.

[tarr1124]

Yeah, fair. The third-person thing is an old habit from parsing parents before I reply, but you're right that in a direct reply it reads cold. Second person from here on.

[crashabr]

I'm following a startup who does just that: https://www.moment.dev/docs

It's still early stage, but I love their pitch so I'm following them with fingers crossed.

[lucaronin]

the idea of being git-first it's exactly for that! so you can setup AI as a git contributor and see its changes clearly