# Can two people's AIs build at the same time without getting in each other's way?

Checked 2026-11-15 against GilbApp d5296208bbffa2ab70076e6194f5537c4be1ddf7.

Yes, if each works on its own part. Two changes to the same record or the same code can clash, so agree who builds what.

## Deeper

A project is kept in its own vault, the store for its records, so two people build together by sharing that vault. Each person signs in with their own account and can use their own AI, on their own subscription. The answer [Can several people work on the same project?](http://support.gilb.com/help/can-several-people-work-on-the-same-project) shows how to share the project and give the other person's AI access.

In the vault. Several people can work in the vault at the same time. When two change the same record, GilbApp often notices, and the person who saves second sees a message such as "This record changed elsewhere. The latest is shown; your change to a field that was also changed there was not saved." Then make your change again. For some changes GilbApp does not check, and the later change stays. Jackfruit, the vault agent, looks for a record of the same type and name before it writes, and uses it instead of making a second one, so two AIs asking for the same record do not make two.

In the code. Each person's AI writes code in a folder on that person's own computer; GilbApp's chat does not reach the files on your computer unless you choose a code folder while Claude Code is connected. The answer [How do I let my AI build in a folder on my computer from GilbApp's chat?](http://support.gilb.com/help/how-do-i-let-my-ai-build-in-a-folder-on-my-computer-from-gilbapps-chat) shows how. Two people's code comes together only through a shared store for code, such as GitHub, a website where programmers keep and share code. When your AI coder keeps your app's code with Git, the program programmers use to keep versions of their code, the rules it follows say that two people, each with their own coding AI, share the code this way, to keep their AIs from overwriting each other's work:
Each AI works on its own branch, a separate line of changes named after the person whose computer it runs on.
No AI changes the main version, the branch that holds the checked code, directly; a change joins it only through a pull request, a request to add a branch's changes that can be checked first.
No AI deletes or overwrites another person's branch, and each starts a new branch from the latest main version.
The same rules say every code store keeps a copy on GitHub. No setup step needs a GitHub account; when building starts, the git rules of Agent.Coder, the agent that writes your app's code, keep a copy of the code on GitHub, so your AI may ask you to make a free GitHub account then. The answer [Do I need a GitHub account?](http://support.gilb.com/help/do-i-need-a-github-account) tells more. Ask your AI which account it will use before a second person starts building. Tell your AI to make the GitHub copy private, unless you want everyone to see your code.

The plan. Agree who asks Kai-Zen, the planning agent, to change the plan, and who builds which part. Before it does anything, Kai-Zen reads the project's setup, its specs and its last round of work, so it starts from what the others saved.

Telling the AIs apart. GilbPlatform keeps every earlier version of a record, with when each fact, one value in one field, was written and who wrote it. What an AI connected with "▸ CONNECT AI" writes is written as its AI vault; what an AI writes from GilbApp's chat is written as the person who uses it. GilbApp has no screen for that history today; the answer [How do I see a record as it was before \(its history\)?](http://support.gilb.com/help/how-do-i-see-a-record-as-it-was-before-its-history) says more.

This answer is written for a computer screen.

Source: Standard Rule\_Code\_git-workflow \(read 13 November 2026, from Agent.Coder.Contextual: read when creating a repo, branching or opening a PR\): RuleGitworkCollisionSafety \("Two or more collaborators, each running their own coding agent, share these repos. These rules guarantee their agents never overwrite each other's work."\), RuleGitnsPerPerson \(&lt;owner\>/&lt;short-feature\>\), RuleGitmainNoDirectPush, RuleGitmergeViaPr, RuleGitdelNotOwned, RuleGitrebaseRefreshMain, RuleGitremoteRemoteRequired \(a GitHub remote for every repo\). Jackfruit.Find \(read 13 November 2026\). GilbApp 49b1ae53 \(https://gilb.com/app/version.json, read 13 November 2026\): src/components/records/RecordDetail.tsx:1235 \("This record changed elsewhere. The latest is shown; your change to a field that was also changed there was not saved."\). Live help pages, sentences shared word for word: Can several people work on the same project? \(several people at the same time; GilbApp often notices; some changes not checked; Kai-Zen reads the project first; history and who wrote it; AI vault versus chat\); Do I need a GitHub account? \(GitHub and Git glosses\); How does Kai-Zen put a change live? \(GilbApp's chat does not reach the files on your computer unless you choose a code folder while Claude Code is connected\); How do I see a record as it was before \(its history\)? Code-folder exception: GilbApp 49b1ae53 \(https://gilb.com/app/version.json, read 13 November 2026\), src/components/agent/AgentChat.tsx:677-692 and :1084-1090 \("Choose a code folder", "Code in", Claude Code only\); live answer How do I let my AI build in a folder on my computer from GilbApp's chat?
