Fully agree, very icky surveillance vibes. In particular:

> DeltaDB breaks your work into a stream of fine-grained deltas. Where Git captures a snapshot at each commit, DeltaDB captures every operation in between and gives each one a stable identity.

I was curious about giving Zed a try, now that it has an emacs keymap. Not anymore. This is such a horribly invasive feature, I absolutely do not want my colleagues reviewing every single intermediate edit, down to the keystroke, that went into the commits I publish for review.

Before I put a PR up for review, I'll sometimes edit my commit history a little bit in magit to make it more linear and digestible--maybe update descriptions, squash some adjacent commits together, etc. This just throws that whole aspect of the job out the window and says "hey, colleague, hoover up this firehose of deltas and enjoy it".

And what the hell does this even mean?

> What we're really after is simple: the conversation with the agent becomes the only conversation you need to have.

Lmao. No. Wrong.

▲

fridder 4 hours ago | parent | next [-]

The more I think about it and your comment the more I wish it was local only. It could be useful to analyze your editing habits and interactions with AI but I want that for my own benefit not random coworkers

	▲	slackpad 3 hours ago \| parent \| next [-]
		Yeah I really would not want all my convos synced up like this. I've been working on a personal version of something like this but it keeps all your conversations and notes in a separate Git repo that you control that's totally separate from the project repo - it's entirely designed for personal use: https://github.com/modulecollective/moe
	▲	jcgrillo 2 hours ago \| parent \| prev [-]
		I would probably only use these data if I had some script I could run in it for analysis, and even then optimizing my AI chats is probably pretty low value.. certainly not enough to justify the cost of analysis, unless there's something that provides actionable insights with almost zero time investment. Producing code edits itself is such a small fraction of the job I'm really not convinced these are valuable data. Mostly the effort and time goes into reading and understanding code, not producing or transforming it.

▲

selicos 2 hours ago | parent | prev [-]

This seems like a perfect audit feature to flip back and train a model. Or ensure your human worker is working during business hours.