u/Mammoth_Towel8765

Hey guys,

my setup is replit, claude code, and codex all at once. i design the mockup in replit canvas, download the whole thing, hand it to claude code for the frontend, and codex does the backend.

the actual problem is keeping them in sync. codex changes something in the backend and now i have to go tell claude code to match it on the frontend. then claude code adds something to the frontend and i have to go back to codex to match it on the backend. the whole time i'm also re-feeding both of them the replit mockup so they don't drift off the design. i'm just sitting in the middle relaying messages between three agents that can't see each other, all day.

If you run more than one agent you probably know exactly this loop.

so i built a thing to get myself out of the middle. it's basically a shared room you drop your agents into so they sync with each other directly instead of routing every change through you.

They can message each other and hand off work, there's a shared board so codex can finish the backend and pass it straight to claude code.

They can notify each other, ask questions, send requests, and share the same context like an actual human team. i can also hand one of them a spec and it splits the work into tasks for the others.

It fixed my exact problem. what i honestly don't know is whether this loop is a real thing for other people or if my workflow is just weird.

So the gut check i actually need: if you run more than one agent, is keeping them in sync an actual pain for you, or have you already got a way around it that i'm too dumb to have found? and if it is a pain, what does your setup look like.

It's live and free to start if you want to poke at it, link's in the comments so this isn't just an ad. built it solo so it's rough, tell me where it falls apart.

Hey guys,

my setup is replit, claude code, and codex all at once. i design the mockup in replit canvas, download the whole thing, hand it to claude code for the frontend, and codex does the backend.

the actual problem is keeping them in sync. codex changes something in the backend and now i have to go tell claude code to match it on the frontend. then claude code adds something to the frontend and i have to go back to codex to match it on the backend. the whole time i'm also re-feeding both of them the replit mockup so they don't drift off the design. i'm just sitting in the middle relaying messages between three agents that can't see each other, all day.

If you run more than one agent you probably know exactly this loop.

so i built a thing to get myself out of the middle. it's basically a shared room you drop your agents into so they sync with each other directly instead of routing every change through you.

They can message each other and hand off work, there's a shared board so codex can finish the backend and pass it straight to claude code.

They can notify each other, ask questions, send requests, and share the same context like an actual human team. i can also hand one of them a spec and it splits the work into tasks for the others.

It fixed my exact problem. what i honestly don't know is whether this loop is a real thing for other people or if my workflow is just weird.

So the gut check i actually need: if you run more than one agent, is keeping them in sync an actual pain for you, or have you already got a way around it that i'm too dumb to have found? and if it is a pain, what does your setup look like.

It's live and free to start if you want to poke at it, link's in the comments so this isn't just an ad. built it solo so it's rough, tell me where it falls apart.

Hey vibecoders,

my setup is replit, claude code, and codex all at once. i design the mockup in replit canvas, download the whole thing, hand it to claude code for the frontend, and codex does the backend.

the actual problem is keeping them in sync. codex changes something in the backend and now i have to go tell claude code to match it on the frontend. then claude code adds something to the frontend and i have to go back to codex to match it on the backend. the whole time i'm also re-feeding both of them the replit mockup so they don't drift off the design. i'm just sitting in the middle relaying messages between three agents that can't see each other, all day.

If you run more than one agent you probably know exactly this loop.

so i built a thing to get myself out of the middle. it's basically a shared room you drop your agents into so they sync with each other directly instead of routing every change through you.

They can message each other and hand off work, there's a shared board so codex can finish the backend and pass it straight to claude code.

They can notify each other, ask questions, send requests, and share the same context like an actual human team. i can also hand one of them a spec and it splits the work into tasks for the others.

It fixed my exact problem. what i honestly don't know is whether this loop is a real thing for other people or if my workflow is just weird.

So the gut check i actually need: if you run more than one agent, is keeping them in sync an actual pain for you, or have you already got a way around it that i'm too dumb to have found? and if it is a pain, what does your setup look like.

It's live and free to start if you want to poke at it, link's in the comments so this isn't just an ad. built it solo so it's rough, tell me where it falls apart.

Hey guys,

my setup is replit, claude code, and codex all at once. i design the mockup in replit canvas, download the whole thing, hand it to claude code for the frontend, and codex does the backend.

the actual problem is keeping them in sync. codex changes something in the backend and now i have to go tell claude code to match it on the frontend. then claude code adds something to the frontend and i have to go back to codex to match it on the backend. the whole time i'm also re-feeding both of them the replit mockup so they don't drift off the design. i'm just sitting in the middle relaying messages between three agents that can't see each other, all day.

If you run more than one agent you probably know exactly this loop.

so i built a thing to get myself out of the middle. it's basically a shared room you drop your agents into so they sync with each other directly instead of routing every change through you.

They can message each other and hand off work, there's a shared board so codex can finish the backend and pass it straight to claude code.

They can notify each other, ask questions, send requests, and share the same context like an actual human team. i can also hand one of them a spec and it splits the work into tasks for the others.

It fixed my exact problem. what i honestly don't know is whether this loop is a real thing for other people or if my workflow is just weird.

So the gut check i actually need: if you run more than one agent, is keeping them in sync an actual pain for you, or have you already got a way around it that i'm too dumb to have found? and if it is a pain, what does your setup look like.

It's live and free to start if you want to poke at it, link's in the comments so this isn't just an ad. built it solo so it's rough, tell me where it falls apart.

Hey guys,

my setup is replit, claude code, and codex all at once. i design the mockup in replit canvas, download the whole thing, hand it to claude code for the frontend, and codex does the backend.

the actual problem is keeping them in sync. codex changes something in the backend and now i have to go tell claude code to match it on the frontend. then claude code adds something to the frontend and i have to go back to codex to match it on the backend. the whole time i'm also re-feeding both of them the replit mockup so they don't drift off the design. i'm just sitting in the middle relaying messages between three agents that can't see each other, all day.

If you run more than one agent you probably know exactly this loop.

so i built a thing to get myself out of the middle. it's basically a shared room you drop your agents into so they sync with each other directly instead of routing every change through you.

They can message each other and hand off work, there's a shared board so codex can finish the backend and pass it straight to claude code.

They can notify each other, ask questions, send requests, and share the same context like an actual human team. i can also hand one of them a spec and it splits the work into tasks for the others.

It fixed my exact problem. what i honestly don't know is whether this loop is a real thing for other people or if my workflow is just weird.

So the gut check i actually need: if you run more than one agent, is keeping them in sync an actual pain for you, or have you already got a way around it that i'm too dumb to have found? and if it is a pain, what does your setup look like.

It's live and free to start if you want to poke at it, link's in the comments so this isn't just an ad. built it solo so it's rough, tell me where it falls apart.

Hey founders,

my setup is replit, claude code, and codex all at once. i design the mockup in replit canvas, download the whole thing, hand it to claude code for the frontend, and codex does the backend.

the actual problem is keeping them in sync. codex changes something in the backend and now i have to go tell claude code to match it on the frontend. then claude code adds something to the frontend and i have to go back to codex to match it on the backend. the whole time i'm also re-feeding both of them the replit mockup so they don't drift off the design. i'm just sitting in the middle relaying messages between three agents that can't see each other, all day.

If you run more than one agent you probably know exactly this loop.

so i built a thing to get myself out of the middle. it's basically a shared room you drop your agents into so they sync with each other directly instead of routing every change through you.

They can message each other and hand off work, there's a shared board so codex can finish the backend and pass it straight to claude code.

They can notify each other, ask questions, send requests, and share the same context like an actual human team. i can also hand one of them a spec and it splits the work into tasks for the others.

It fixed my exact problem. what i honestly don't know is whether this loop is a real thing for other people or if my workflow is just weird.

So the gut check i actually need: if you run more than one agent, is keeping them in sync an actual pain for you, or have you already got a way around it that i'm too dumb to have found? and if it is a pain, what does your setup look like.

It's live and free to start if you want to poke at it, link's in the comments so this isn't just an ad. built it solo so it's rough, tell me where it falls apart.

Hey guys,

my setup is replit, claude code, and codex all at once. i design the mockup in replit canvas, download the whole thing, hand it to claude code for the frontend, and codex does the backend.

the actual problem is keeping them in sync. codex changes something in the backend and now i have to go tell claude code to match it on the frontend. then claude code adds something to the frontend and i have to go back to codex to match it on the backend. the whole time i'm also re-feeding both of them the replit mockup so they don't drift off the design. i'm just sitting in the middle relaying messages between three agents that can't see each other, all day.

If you run more than one agent you probably know exactly this loop.

so i built a thing to get myself out of the middle. it's basically a shared room you drop your agents into so they sync with each other directly instead of routing every change through you.

They can message each other and hand off work, there's a shared board so codex can finish the backend and pass it straight to claude code.

They can notify each other, ask questions, send requests, and share the same context like an actual human team. i can also hand one of them a spec and it splits the work into tasks for the others.

It fixed my exact problem. what i honestly don't know is whether this loop is a real thing for other people or if my workflow is just weird.

So the gut check i actually need: if you run more than one agent, is keeping them in sync an actual pain for you, or have you already got a way around it that i'm too dumb to have found? and if it is a pain, what does your setup look like.

It's live and free to start if you want to poke at it, link's in the comments so this isn't just an ad. built it solo so it's rough, tell me where it falls apart.

Hi guys, the opportunity is simple:

​

Most small and midsize businesses know AI matters, but they have no idea where to start, what tools to use, what workflows to automate, or who to trust to implement it.

​

We do not need to build everything ourselves.

​

The model:

​

1. Consult with businesses

2. Build their AI strategy and roadmap

3. Identify the highest ROI workflows to automate

4. Broker the technical implementation to trusted dev/automation agencies

5. Get paid through consulting fees + referral/implementation commission

​

I bring deep AI knowledge and can help businesses across different categories understand how AI can actually improve operations, sales, support, admin, marketing, and internal workflows.

​

I’m looking for someone who has SDR experience, business connections, or knows how to get in front of SMB owners and decision makers.

​

This is not a “let’s build an app and hope people come” idea. It is a services-first business with a clear path to revenue.

​

If you have sales experience and want to build this with me, please DM. (US based)