Hacker News new | ask | show | jobs
by fiatpandas 60 days ago
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.
3 comments
tarr1124 60 days ago
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.

link
CrompyBlompers 59 days ago
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.
link
tarr1124 59 days ago
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.
link
CrompyBlompers 59 days ago
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.

link
tarr1124 58 days ago
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.
link
crashabr 60 days ago
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.

link
lucaronin 60 days ago
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
link