Back to Signal Feed
CodeTracked since May 19, 2026

Summon extension now supports @mention-based agent calls

In Goose PR #9325, the summon extension was updated to trigger subagent calls from @agent mentions or natural references in chat text, so users can invoke an agent without using a separate summon command format.

aaif-goose/goosesummon extension@agent mentionsubagent invocation

What Happened

  • In Goose PR #9325, the summon extension was updated to trigger subagent calls from @agent mentions or natural references in chat text, so users can invoke an agent without using a separate summon command format.
  • In Goose PR #9325, the summon extension was updated to trigger subagent calls from @agent mentions or natural references in chat text, so users can invoke an agent without using a separate summon command format.
  • 1 evidence item attached for review.

What is Different

Before

Scattered source updates, isolated context, and manual follow-up across multiple feeds.

Now

Added mention-aware dispatch logic in the summon extension so @agent handles and name-like references are parsed as actionable invocation signals, reducing the need for explicit command syntax.

Why Track This

Why It Matters

Developers and operators using Goose can now route tasks to the intended subagent just by mentioning it in ordinary language, which should reduce friction and command friction in workflows, while the key risk to watch is accidental activation from non-command @text in normal conversation. This change extends summon routing from strict command paths to mention/heuristic matching, so monitoring should focus on false-positive triggers, incorrect agent selection, and any unintended execution from casual references.

Impact

Developers and operators using Goose can now route tasks to the intended subagent just by mentioning it in ordinary language, which should reduce friction and command friction in workflows, while the key risk to watch is accidental activation from non-command @text in normal conversation. This change extends summon routing from strict command paths to mention/heuristic matching, so monitoring should focus on false-positive triggers, incorrect agent selection, and any unintended execution from casual references.

What To Watch Next

  • Watch whether aaif-goose/goose becomes a repeated pattern.
  • Track follow-up changes around Agent Orchestration Platforms.
  • Compare future signals against this evidence trail.
  • Re-check risk flags: false_positive_agent_activation, wrong_agent_dispatched_from_name_match.
Open Topic TimelineOpen Technical EventOpen Original Sourcefalse_positive_agent_activation / wrong_agent_dispatched_from_name_match / unexpected_trigger_in_plain_chat / chat_mention_edge_cases

Supporting Evidence