Build together, each with your own agent, without overwriting each other’s work.
Faundr tells every agent who else is in the project and which files they’re in. Everyone works on their own workbench, agents get a heads-up before touching a file someone else is editing, and work lands in the main project with tests passing.
Team up without stepping on toes. Two agents, one file, and someone’s work is gone.
Someone’s work gets overwritten.
Two people ask their agents to edit the same file. The last save wins, and the other change silently disappears.
With Faundr
- A heads-up before editing a file someone else is on
- Everyone on their own workbench
- Merges that run your tests
Two people build the same thing.
Nobody knows who picked up which task. By end of day, two agents have built the same button two different ways.
With Faundr
- Every task shows who’s on it
- Agents know who else is in the project
- The dashboard shows who’s doing what
Every agent plays by its own rules.
Everyone taught their own agent something different. The code becomes a patchwork nobody understands.
With Faundr
- Everyone gets the same rules
- Team decisions apply to every agent
- Update a rule and everyone gets it
Every agent knows what the others are up to. You don’t have to tell it anything.
Faundr tracks who’s working, on which workbench, and in which files. Each person’s agent gets that context at three moments. These are heads-ups only, so files stay open and nobody waits for a teammate to release one.
When someone joins, leaves, or switches files, your agent hears about it with your next prompt.
[Faundr] Team now: joined: Ben (Codex on ben-laptop on branch mesa/google-login): editing src/auth/google.ts. Avoid touching the same files without agreeing first; if you need to, tell the user.
Everyone builds separately. Faundr merges. Nothing reaches main without your approval.
Everyone works on their own workbench. When a task is done, /faundr:merge brings it into the main project, but only after you give the go-ahead.
- 1Everything saved to your workbenchYour changes stay on your own workbench, separate from the rest of the team.
- 2Check who else is hereIf someone is editing the same files, you’ll know before merging.
- 3Pull the latestThe agent pulls in whatever the team has already merged. Any conflicts stay on your workbench, away from everyone else’s work.
- 4Conflicts in plain languageIf both changes can stay, it keeps both. If not, it shows you both options and asks which one wins.
- 5Tests before shippingIf the merge broke something, it fixes it first. Broken code never goes out.
● You and Ben both changed free shipping, in different ways. Which one should win?
- YoursFree shipping on orders over $50.
- Ben’sFree shipping over $40, West Coast only.
you › go with Ben’s
Merged into the main project. Tests passing.
Ask a teammate’s agent, right from the dashboard. Skip the back-and-forth in DMs.
Write what needs doing and pick who it’s for. The request shows up in that person’s agent while it’s open. Need to reach everyone? Send a message instead, and it goes to the next agent anyone on the team has open.
Ask an agent
What needs doing
Buy button is broken on mobile
Assign to
Send request
● Casey sent a request from the dashboard: the buy button is broken on mobile. Want me to fix it now?
you › go ahead
Fixed and marked done in the dashboard.
Requests from teammates only run once the person at the keyboard approves.
Watch your whole team work, live. One room per person.
In the dashboard, everyone gets a room, and each open agent shows up as a robot at a desk, with a smaller robot for every subagent. You can see who’s thinking, editing, running a command, or waiting on a reply.
Alex’s room
In the dashboard now
Agents
- AI agentEditing · own workbench
- Subagent · ExploreThinking
Ben’s room
In the dashboard now
Agents
- AI agentRunning a command · own workbench
Casey’s room
Not in the dashboard
Agents
- AI agentNeeds you
Same rules for every agent. Everyone gets a clear role.
Team rules and decisions live in the project dashboard and reach everyone’s agent in every session. Update a rule and everyone picks it up in their next session.
[Faundr] Team rules (always follow them):
- Payments go through Stripe only. Never store card data in the database.
- App copy in plain language.
[Faundr] Technical decisions already made:
- Auth via Supabase, since we already use its database.
Team roles
- OwnerEverything, including deleting the organization and managing other owners.
- AdminManages org settings, invites and removes people, deletes projects.
- MemberCreates and edits projects, uses the plugin.
- Read-onlyCan view projects, nothing else.
Agents work alone. With Faundr, they work as a team.
On its own, each agent only sees its own user’s chat. With Faundr, every agent knows what the team is doing and follows the same rules.
FAQ
Can I lock a file so nobody else can touch it?
No. Faundr sends warnings and leaves files open, since locks jam up the team when someone forgets to release them. Everyone works on their own workbench, and merging handles the rest.
Can a teammate’s agent change my code without me knowing?
Everyone’s work stays on their own workbench until it’s merged, and merging only happens with the OK of the person at the keyboard. Requests from teammates need your OK too.
Can teammates use different AI agents?
Yes. The Office and the warnings show each person’s agent, whichever one they use.
Do I need to know git?
No. Faundr talks about a "workbench" and the "main project," and the agent runs the commands. Your project just needs to be on GitHub to merge work from two people.
Who can invite people?
Owners and Admins can invite people, remove them, and change roles. Members create projects and use the plugin. Read-only users can only view.