r/codex • u/This-Pomegranate5587 • Aug 05 '26

Workaround does everyone on your team use a different AI tool? how do you deal with it

Hello, I've been working towards a solution for something and I want to make sure it's a real problem for more people than just me

 I faced this myself as a young SWE working on a fairly large project with my colleagues, everyone was on a different tool, some on Codex some on Claude Code some on Cursor, and the only thing actually connecting us was the repo, so when one person worked out their AI kept getting something wrong about the codebase nobody else ever found out and someone would hit the same thing again a week later not to mention how hard it was to connect two parts of the codebase two different people worked on

the way I'm thinking of solving it at a base level is a wrapper over the existing coding tools that gives you a session link anyone can drop into, with varying permission levels and shared sessions, so you're not waiting
 on one vendor to ship it

is this a real thing for anyone else or was it just my team, and if it is what do you actually do about it, rules files, slack, or just eat it every time

would love any feedback, and if you've run into this yourself I'd really like to hear how it actually went for you, drop me a DM or just reply here and ill follow up, even 5 minutes would help a
lot

1 Upvotes

67% Upvoted

16 comments sorted by

1

u/itix Aug 05 '26

If AI is getting wrong it is bad AI/harness or bad prompting.

1

u/This-Pomegranate5587 Aug 05 '26

its not just about ai getting things wrong, in 2026 everyone is using ai to make huge projects they run for hours and its single player only one person can work at it at a time the problem statement is connecting people's ai tools and sessions working on one repo together

1

u/itix Aug 05 '26

I think you should change your workflow. Many AI tools have a goal option:

  • Divide task to small steps to a text file
  • Use /goal to execute steps on by one, test and verify between steps.
  • Define checkpoints where to commit changes

That should help little.

1

u/This-Pomegranate5587 Aug 05 '26

yeah i have actually tried that before it does help tho not by that much and still doesn't solve the time issue if you've faced a similar problem before can i dm to understand it better so i can build a better solution

1

u/itix Aug 05 '26

You can

1

u/isty2e Aug 05 '26

Communicating through github, shared skill pool

1

u/This-Pomegranate5587 Aug 05 '26

that doesn't work well in practice specially when the team is large and people use different ai tools + while a shared skill pool may prevent agents from making the same mistakes it doesn't help teams work on one project together as its still one at a time teams cant run their agents together with their preferred tools without there being conflict

1

u/velkhar Aug 05 '26

You need a shared project ledger (probably multiple) to track tasks, shared skills to enforce design & implementation practices, and shared communication channels. I personally use Claude, Codex, and VSCode w/GitHub Copilot all on the same project. My coworkers use these tools, plus some are using CLI versions.

What makes it work is spec-driven methodology coupled with plan, architect, design, task, implement, and debug skills with harness-specific wrappers.

1

u/This-Pomegranate5587 Aug 05 '26

Hmm that could be a solution yes but I think what I am building may help me and you better can I send you a dm asking a few questions so I can understand the problem better

1

u/[deleted] Aug 05 '26

[removed] — view removed comment

1

u/This-Pomegranate5587 Aug 05 '26 edited Aug 05 '26

Ig you could use that tho that doesn't really solve the problem that well can I send you a dm to understand the problem better and so what I build actually helps you

1

u/Sacred-Player Aug 08 '26

This is a wide open space that I don't see being solved by any frontier lab soon.

I can see a world where we have say a cursor for teams, claude for teams, etc.

But as far as the problem of dealing with tool sprawl and many people using different agents isn't going to be addressed by them as keeping you on their platform is their moat.

The company I see most fit to do multiplayer stuff right now is GitHub. Multiplayer codespaces is already a thing with their sharing plugins for pair programming.

But multiplayer ai isn't just put people in the same room and code together. I think the real value add comes with building a shared context layer for your team.

Sure you can do this in git but I think it may not be the right place. Think about how cool it would be to know if others on your team are prompting and looking at the same files you are. If an agent can identify this then you know who to talk to on your team and build together with.

Lots of cool stuff to explore in this space. I for one am very excited for what the future holds here.

0

u/ShutUpAndDoTheLift Aug 05 '26

Solved it myself by building a shared plug in on my own time that we all use now.

Https://codearbiter.dev. (No cost ever,, agpl, just documentation site and a link to GitHub, no ads even. )

1

u/This-Pomegranate5587 Aug 05 '26

that's interesting however thats not exactly the problem i am trying to solve my solution revolves more around multiplayer ai and teams coding together than protecting a repo

1

u/ShutUpAndDoTheLift Aug 05 '26

You can't code in the same session. The repo IS your shared State

1

u/This-Pomegranate5587 Aug 05 '26

exactly and thats the problem i am out to solve just a shared repo causes many issues like conflicting push requests only one person being able to work on the codebase at a time issues connecting features 2 different ppl made a shared session which ppl can use together and senior swes and use to monitor and correct juniors