Projects and repos

A project is the shared space a group of people works in, and a repo is a git repository registered inside that project. Everything Coordigent shows you, from agents to conflicts, belongs to a repo in a project.

#The model

Coordigent uses one model everywhere: Project → Repo → Agent → Files.

• A project holds people and the repos they registered.
• A repo is a git repository, named by its origin remote (for example acme/api).
• An agent is one running coding tool working in a repo. See Agents.
• Files are what agents edit. See Files in use.

Without an account, Coordigent still works on your own machine. A project is what lets your teammates' agents see yours.

#How a project starts

You get a project the first time you sign in. If nobody invited you, Coordigent creates one for you, named after you, and you own it. If you signed in from an invite link, you join the project that invited you instead.

You can belong to several projects and switch between them. On the website, the project switcher lists your projects and ends with New project, which creates an empty project that you own and switches you to it. Your other projects stay as they were.

#How a repo joins a project

Once your machine is logged in, the first agent you run in a new repo puts one question on your Needs you list: whether to connect the repo. In VS Code, Set up registers the repo into the project you are looking at; Always for my repos does that for every new repo from now on; Not now leaves it. To connect one without waiting, run this inside it:

A project holds as many repos as you connect, all in the same project. An invite grants the project, so a teammate sees every repo in it, including ones connected later. To keep a repo apart, create a New project first and connect it there. More in Connect a repo.

Until a repo is connected, agents running in it coordinate on your machine only, and your teammates do not see them.

#How a repo leaves

• For you alone: coord unenroll in the repo stops Coordigent for you there, on this machine. The project and your teammates are untouched; coord connect turns it back on.
• For everyone: the project's owner runs coord repo remove in the repo, or uses Remove… on the website's Repos page. Its history is kept and the owner's coord connect brings it back; --delete-history deletes it for good.

Both are described in Connect a repo.

#Teammates and roles

Any member can invite people. An invite code is eight characters, works for one person and expires after 7 days. See Invite your team.

Each person is an owner, an admin or a member. The owner and admins can change the project's visibility, change roles, remove teammates, revoke invites and end anyone's agent. Only the owner can remove a repo. Everything else, including invites and Slack settings, is open to everyone. When the owner leaves, the longest-standing admin becomes owner, or failing one the longest-standing member. You cannot leave your last project. The full table is on the website page.

#What teammates can see

Every member sees every agent, file in use, conflict and handoff in the project's repos. Under the default visibility, prompt text and diffs reach only their author; titles, file paths, branches, commits and conflicts stay visible to the whole project. The owner or an admin can share everything instead in Settings → Visibility. Transcripts are never uploaded. More in Security.

#Next

• Connect a repo
• Invite your team
• Agents