> 5. What features will gitdot not have?

> AI.

> We view AI as an implementation detail — and do not think that using it is necessarily good.

> In fact, we think it makes many products worse by acting as a bandaid for poor design.

> That isn’t to say we are blind to it, but that we will be judicious in our use of it instead.

Not sure I follow. What feature are the developers referring to? I understand that AI will power tools that may or may not fit a particular use case. How is AI a feature and what does it mean to be anti-AI?

I'm honestly lost for words over how you can write something like this while the web app's source code is clearly heavily integrated with Claude Code.

https://gitdot.io/bkdevs/gitdot/files

yeah thanks for digging in, this was a bit ambiguous.

so take this to mean - 1) no AI copilot in the app and 2) no training on your data nor selling of it.

our take on AI is that we should focus on building tools that help address its limitations; one of the things we're particularly keen on is building stacked diffs into reviews as a primitive, so it's easier to review a large AI-generated (or assisted) PR. (e.g., diff 1 for API changes, diff 2 for backend wireup, diff 3 for front-end changes)

i think to do that, we're going to try and hook into the subscriptions that people already have and are paying for: Claude, Codex, rather than package our own, but some of that is a bit hacky to do.

hope that's clearer and thank you for asking

That's not really anti-AI. Anti-AI would mean avoiding it as a value regardless of practicality.

That sounds more like anti-enshittification.