Tracking Agents in Span

Last updated: May 19, 2026

Agents are AI tools that write code or review pull requests on their own — think GitHub Copilot, Cursor in agent mode, Claude Code, Devin, or Codegen. Span treats each agent as a first-class entity alongside People and Teams, so you can see what your agents are actually contributing to your engineering output.

Setting up an agent

Head to Settings → Agent Management to get started.

Let Span find them for you

If Span spots agent-like accounts in your connected GitHub, GitLab, or Azure DevOps, you'll see a banner that says "We've detected X agent(s) in your data." Click See all to open the Detected Agents dialog, then hit Add on any card to pre-fill the Create Agent form. Easiest path if you already have agents running.

Or create one yourself

Click Create Agent in the top right and walk through the modal:

  1. Pick a tool. Choose from the supported list (Copilot, Cursor, Claude Code, and others) or select Other for a custom agent. Tools that are already assigned won't show up in the dropdown.

  2. Use default configuration (optional, supported tools only). If you'd rather not think about it, check this box and Span will fill in the capabilities and VCS usernames with our recommended defaults. Those fields will lock.

  3. Add a name and description. For supported tools, the name is auto-filled and locked at creation. If you picked Other, you'll need to enter a name; the description is up to you.

  4. Choose capabilities. Pick one or both: Code Generation and Code Review.

  5. Map VCS accounts. For each connected platform, enter the bot username(s) the agent uses to open PRs or leave reviews. You can add more than one per platform if the agent shows up under multiple accounts.

Click Create and you're done — you'll see a confirmation toast.

Editing or deleting an agent

Open the ⋮ menu on any row in the Agents table.

  • Edit lets you update the name, description, capabilities, and VCS usernames. Heads up: the tool type is permanent, so if you picked the wrong one, you'll need to delete and start over.

  • Delete removes the agent for good (with a confirmation prompt first).

Seeing what your agents are up to

Go to Organization → Agents in the sidebar to see all your configured agents in one place. Click any agent to open its detail page, where you'll find:

  • A metrics dashboard with standard development metrics attributed to that agent (PRs merged, code reviews, and so on).

  • An activity log showing the agent's contributions over time.

There's an agent selector dropdown at the top of the detail page so you can jump between agents without going back.

A few things worth knowing

  • Tool type is permanent. Once you create an agent, you can't change the tool. Pick carefully, or delete and recreate if you need to.

  • One agent per supported tool. Copilot, Cursor, and the others can each only be assigned to one agent at a time.

  • Attribution depends on VCS usernames. Span ties metrics to the usernames you enter, so they need to match the bot accounts exactly — otherwise activity won't get picked up.