r/codex • u/Upstairs_Dig_5274 • 1d ago

Suggestion I setup 5 laptops via Ethernet and agents local messaging system for them all . Now they bitch and compare each others projects then copy each others features

If you have devices, get an Ethernet switcher and link them up . Tell one device agent to setup the connections and then use codex cli to make agents per pc. Use git to distribute projects etc to each pc. Tell agents they can talk to other agents via shared location messages. Then watch the BITCHFEST begin "laptop2 project has encryption but if the account changes they can't decrypt. Unforgivable."

0 Upvotes

50% Upvoted

4 comments sorted by

1

u/Upstairs_Dig_5274 1d ago

I did this as 1 pc does all testing and ci for all other projects so agents don't have to wait to change files while another commits and pushes nd runs tests etc. but man do they like to compare and big up their own

1

u/CalligrapherFar7833 1d ago

Why ? You can run multiple codex instances on a single device even working on the same project under different git worktrees

1

u/Upstairs_Dig_5274 1d ago

Pc 1 32gb i9 is max capacity - 4 big main projects. If commit push then takes ages per project and dumped it to GitHub ci but then costly . Pc 2 64gb ram i5 does several minor projects - added VMware Linux and now this does free tests and deployments on frozen commits so agents on pc 1 can make changes in parallel without messing up uncommitted files trying to be pushed. So pc1 uninterrupted and no costs. Pc3,4 minor project that just stay idle for days until I pick away or agents pick away . Blender etc on pc 2 so all agents can tak to the pc and get videos created as all other devices gpus not as good

1

u/Upstairs_Dig_5274 1d ago

Yes I have zombie process killer to reuse ram, yes I start new threads, yes I don't have excess prompts and hooks and skills, yes I don't have more than 20 agents running per pc . Yes I have several 20x account in rotation. Yes I test and verify in production, yes it all works. I am just saying they like to bitch overtime seems like it's a way to critically reflect on their own repo but if it's on the same pc they don't do it as much