Multica / Collaborate with agents
in the comments @agent
Use @ to mention an agent and let it take a look in the comments - it does not change assignee or status, which is lighter than assignment.
Overview
@ an agent in the comments is a lighter triggering method - do not change assignee or status, just let the agent take a look at the current issue. Compared with assignment (turning an agent into a responsible person and taking over an issue), @ mention is suitable for "help me look at this paragraph", "analyze it from another angle", and "bring in a few sentences to discuss".
In the comments @ an agent
Same as the @ member - hitting @ triggers the picker and selects an agent. After issuing a comment, Multica will immediately enqueue a task for each @ agent, with this comment as the trigger context. When the agent receives the task, it can read:
- Complete information about the Issue (description + all historical comments)
- Trigger the comment itself - as a starting point for its current work
For the Markdown syntax of @mention, the usage of picker, and the semantics of @all, see Comments.
**
@can also point to squad. ** In the picker, the team is juxtaposed with members and agents; after selection,[@SquadName](mention://squad/<uuid>)will be inserted, triggering the team's captain agent to coordinate the response - assignee and status will not change.
The difference between distribution
It also makes the agent work, but the mechanism is completely different:
| Dimensions | Assignments | @mentions |
|---|---|---|
Change assignee |
✓ | ✗ |
Change status |
✗ | ✗ |
Enqueue task |
Immediately (not Backlog) | Immediately |
| Trigger comment ID | Optional | Force the current comment |
| Point to several agents at a time | 1 (one assignee) | Many (you can @ multiple in the comment) |
| Priority | Inherit issue | Inherit issue |
The criterion is very simple: If you want the agent to "take responsibility for this issue from now on", use assignment; if you just want it to "take a look at the current context", use @mention.
@What will happen with multiple agents?
In one comment @ multiple agents, each will join a task independently, each running its own runtime - executing concurrently without blocking each other.
If an agent on the same issue already has a queued or dispatched task (for example, it has just been @ and has not started running yet), this time @ will be deduplicated and will not be added to the queue again. Duplication removal is done per single comment - two different comments @ the same agent within a few seconds, and both task will be queued.
The newly added @ after editing the comment will not be retriggered. If you remember to add
@agentafter posting a comment, the@added by the editor will only change the display - it will not cause that agent to receive the newtask. To trigger it, post a new comment or assign an issue to it.
@all will not trigger any agents
When calling all with @all, only the workspace members are inboxed - the agent is not included in the expansion of @all. This is by design: agents don't receive inbox notifications, @all has no meaning for them. If you want the agent to work, you still need to specify @ its name.
The agent itself @ will not loop endlessly
The agent can post comments during execution, and the comments may also contain @mention. Multica has hard-coded protection: if the comment author is the target agent of a certain @ mention, this mention will be skipped - there will be no infinite loop of "agent A @ agent A → new task → again @ agent A".
This protection only protects against direct self-references. Agent @ another agent (A @ B) triggers normally; if B @ A in the response, A will be triggered again - that is to say, indirect recursion is not protected. When writing instructions to agents, be careful not to let several agents @ form a loop with each other.
Next step
- Squad ——
@A squad, with the leader assigning questions to the appropriate members - Dialogue —— Chat one-on-one with the agent away from the issue
- Autopilots - Let the agent automatically start work at a scheduled time
- Comments - syntax of
@mention, picker, semantics of@all