Website agent manager

coordigent.com shows your whole project in the browser: every agent, every teammate's included, what each one is changing, and what needs a person. Sign in with GitHub, Google or an email link and open your project. From a terminal, coord open opens it for you.

#Finding your way

A sidebar runs down the left: the project switcher, then Setup (until it is done), Overview, Agents, Activity, Messages, Repos, Team, Settings and Agent tools. The top bar has a search (/ focuses it) that looks through agents, an Invite button, and a bell with the Needs you count.

#Setup

A checklist walks you through getting started: install coord, coord login, connect a repo, start an agent and, for a project's owner, invite teammates. Each step ticks itself when Coordigent sees it happen. A teammate who joined sees the steps that are theirs. Until setup is done, the Overview shows the next step too.

#Overview

The project's front page, updated live as agents work:

• Needs you: agents that are Blocked or Waiting on you, each linking to its record.
• Live agents, grouped by person.
• Conflicts that are open.
• Recent files: the five files changed most recently, each opening that change in Activity.
• Recent messages.

#Agents

A table of every agent with its status, app, person, repo, branch, files and lines added and removed. Filter by Running (working or idle), Needs you, Ended or All. A row opens the agent's record.

#Activity

Each agent's own tree of the files it changed, with lines added and removed, and a diff viewer beside it. By file turns it round: one tree for the project, each file listing the agents in it. A file in conflict shows the conflict above its diff. The address names what is selected, so you can share a link to one agent's change to one file.

#Messages

Pick Everyone or one running agent, read the thread, and write a message. It reaches the agent at its next step, as a message from you.

#An agent's record

Open an agent to see everything about it on one page: its task, status, person, app, repo and branch; its handoff summary, when coord summarize wrote one; open conflicts, with Dismiss; its pull requests and plan; the files it edited with their diffs; the commands it ran, its commits, prompts and the messages it received. Agents editing in the same folders but not the same files are listed separately, as not a conflict. For an idle or ended agent you can copy the coord takeover command to pick up its work. The person who ran the agent, the project's owner and its admins can end an agent that is still listed as running. The owner and admins also have End idle agents, which ends the project's idle agents at once.

#Repos

Every repo in the project, with how many agents are working in each and when it was last active, and how to connect another. A project holds as many repos as you connect.

The project's owner has Remove… on each repo:

• Remove from project takes it out for everyone. Agents in it are no longer recorded or warned, and it leaves the website. Its history is kept: coord connect in the repo brings it all back.
• Delete all history deletes every agent, edit, commit, conflict, message and handoff in it, for everyone. You type the repo's owner/repo to confirm. It cannot be undone.

Connecting a repo happens on your machine, with coord connect or when an agent asks.

#Team and invites

The Team page lists everyone in the project with their role, their machines and when they were last seen. Below it you create invites and see the ones still open. Invite in the top bar does the same from any page. An invite is a link or a code, good for one person for 7 days. See Invite teammates.

Each person is an owner, an admin or a member:

The owner's role cannot be changed. When the owner leaves, the longest-standing admin takes over, or failing one the longest-standing member.

The project switcher lists every project you belong to, with its repos. New project creates an empty one and switches you to it; then connect the repos you want in it. You can leave a project when you belong to more than one.

#Visibility

What you see of other people's agents follows the project's visibility. Under the default, Coordination, prompts and diffs are shown only to their author; titles, branches, file paths and conflicts are shared. Under Full, everything is shared. Where something is hidden, the page says so and who can change it. The owner or an admin changes it in Settings → Visibility. More in Invite teammates.

#Settings

• Visibility: Coordination or Full.
• Slack: connect a Slack channel that mirrors agents, conflicts and messages. See Slack.
• Coordinator agent: turn on or off the agent that suggests how to resolve a conflict.
• Machines: how to install coord on another machine.

Agent tools lists the MCP servers, skills and hooks your project's agents reported using. It only displays them; nothing is installed from it.

#Next

See the CLI and the extension for the same picture where you work, or conflicts for what happens when two agents meet.