It is not difficult to believe that the frustration of racist people seeing black people more successful contributed to it. In fact, it's the most obvious and straightforward explanation for it, given the fact that it's 1)1921, 4 or so decades before the Civil Rights act, and in freaking TULSA lmao
you are incredibly naive, ignorant or oblivious if you dont think a primary reason was because of their race in TULSA in 1921. Cmon man -read some history
Plenty of other companies enable this by default too, such as Github, Figma, Adobe, Vercel. I think it's fair to assume that if you ahve data stored within any company, they'll by default use it for training.
> it's instructed to understand both sides before resolving.
This is the crux of the issue. You are delegating the resolution of conflicts to an agent, which is fine, but doesnt solve the core issue that there's no scalable way to actually do this. It is far from a solved problem lol, just because your agents havent had issues resolving them.
Looks cool! Two things: I see you mentioned the merge queue, but how exactly do people avoid or resolve merge conflicts when merging work from two or more agents in the separate worktrees? I havent really seen a seamless way to approach this or do people just have the agents work on distinctly unrelated stuff? Secondly, are containers the primary sandboxing appraoch? or do you support vms?
because you probably need both if you are doing guided agentic work. IDE gives you the familiar benefits, especially code nav. If you are using background agents or launching agents without reviewing their work, then I guess you dont need an IDE.
Agree with this. I find myself switching panes between conductor or codex and zed because of code navigation. Maybe that's what cursor is trying to do in their new version, but I havent tried it yet
Atuin is open source. You dont like their new release? Fork the previous repo, and customize it however you want. That's the whole essence of open source.
Agree on your last point and it's going to be a very bitter lesson. In any case, you probably wanna shift alot of the code verification as left as possible so doing review at PR time isnt the right strat imo. And claude/codex are well positioned to do the local review.
yeah and I wouldnt be surprised if some oltp database platform is in the horizon as well. iirc they already acquired rockset. The eventual goal for these AI platforms is to own the entire e2e platform for e2e agents, from literally the language ecosystem(anthropic betting on TS/Bun) to local dev tooling using their harnesses to production-grade stuff that an agent needs.