Assign bugs to teammates or to AI agents
Route any bug to the right owner (a teammate or an AI coding agent) from the same assignee control.
In BugMojo, a bug can be owned by a person or by an AI agent, and you set both with the exact same control. This is the polymorphic assignee: one field, two kinds of owner. This guide shows you how to assign a bug and how to decide when an agent should take it.
Assign a bug
Open your board and click a bug's title to open the bug detail page.
In the sidebar, click the Assignee field to open the picker.
Choose the Teammates tab to assign a person, or the Agents tab to assign an AI agent.
Select the name. BugMojo saves the assignment and notifies the new owner. To reassign, reopen the field and pick someone else.
When to hand a bug to an agent
Agents shine on well-scoped, reproducible bugs where the evidence is already captured. Good candidates have clear repro steps plus a session replay, console errors, or a failing network request the agent can read. Front-end exceptions, obvious stack traces, and broken API calls are strong first picks.
Common questions
Can I assign a bug to both a teammate and an AI agent?
A bug has one assignee at a time. You can reassign from a teammate to an agent (or back) whenever you like, and the full history stays on the bug.
What happens after I assign a bug to an agent?
An AI agent connected over MCP can read the bug's replay context, console and network logs, and repro steps, then act on it, for example proposing a fix in your codebase.
Which roles can assign bugs?
Owners, admins, developers, and QA can set or change an assignee. Viewers can see the assignee but cannot change it.
Related articles
- How AI agents work with BugMojoUnderstand the full loop, from a captured bug to an agent-proposed fix that a human verifies and closes.
- The bug detail page: a guided tourLearn where every part of a bug lives: replay, console, network, environment, activity, and comments.
- Boards and statuses: customize your workflowLearn how BugMojo boards, columns, and statuses work, then move bugs and shape a workflow that fits your team.
- Agent access, tokens, and the security modelUnderstand how an AI agent's access is scoped, what it inherits from you, and the guardrails that keep it in bounds.