Agent Roles

Every automation agent node has a role.

That role is not cosmetic. It changes the operating expectation for the node and helps the flow editor default to the right behavior.

The three roles

Role	What it should do	Best starting events	What it should not be
`triage`	Read the event or thread, classify it, respond, or decide what happens next	`mention`, `issue_opened`, `issue_comment`	A code-review surrogate
`review`	Inspect changes and produce findings about correctness, security, regressions, or risk	`pr_opened`, `pr_comment`, `push`, `ci_failure`	A generic discussion bot
`edit`	Apply code changes after an earlier step already decided that mutation should happen	Follow-up node after `review` or a decision branch	A first-pass analyzer

triage is the right role when the agent should understand context before it acts.

Typical cases:

Think of triage as “understand the event, then steer.”

review is the right role when the agent should inspect code or diffs and report what is wrong or risky.

Typical cases:

This is also the only role that exposes auto-fix behavior in the current flow editor.

edit is the role you use after the graph has already decided to change code.

That usually means:

This keeps analysis and mutation separate, which makes the graph easier to debug and safer to reason about.

When you add a new agent node, Mogplex chooses a default role based on the start event:

That default is a starting point, not a rule, but it captures the intended product model.

The most common mistake is using review for work that is really thread or issue response.

If the main question is “what is happening here and what should happen next,” that is usually triage.

If the main question is “what is wrong with these changes,” that is usually review.