multica-mentioning

Mention links in issue comments trigger specific actions based on type: agent mentions enqueue a run for that agent, squad mentions enqueue a run for the squad leader, while member and issue mentions render safe links without enqueuing any runs.

Using @all in a comment initiates a broadcast behavior that explicitly suppresses the assignee's automatic trigger, ensuring that the broadcast mention does not cause duplicate or unintended agent runs for the assigned entity.

To trigger an agent delegation, create a real mention link to an agent within an issue comment. The parsing logic identifies this agent mention and enqueues a run specifically for that agent to execute the delegated task.

Runtime guardrails prevent triggers for archived or private agents and squads, blocking unintended runs. The system also includes edge-case guards for pending tasks to ensure mentions do not enqueue actions on inactive or restricted entities.

Mentioning a squad member or an issue renders a safe reference link without enqueuing a run because these mention types are designed for visibility and context rather than task delegation or triggering agent execution.

Yes, the mention rule contract operates with no external dependencies, relying solely on internal parsing patterns and enqueuing logic to map comment mentions to agent, squad, member, issue, and broadcast actions.