Skip to content

Allow native group replies to mention humans without waking Runs - #911

Open
Y1fe1Zh0u wants to merge 1 commit into
dataelement:mainfrom
Y1fe1Zh0u:fix/group-at-human-mentions
Open

Allow native group replies to mention humans without waking Runs#911
Y1fe1Zh0u wants to merge 1 commit into
dataelement:mainfrom
Y1fe1Zh0u:fix/group-at-human-mentions

Conversation

@Y1fe1Zh0u

Copy link
Copy Markdown
Collaborator

Summary

  • allow at to stage valid human and Agent participants together
  • persist every structured mention in the public message
  • run Agent-only budget/cycle checks and create child Runs only for Agent targets
  • update Runtime guidance and bidirectional visible-mention validation for humans

Verification

  • 232 passed across group handoff, model step, finish protocol, group message, delivery, node executor, tool step, and checkpoint side-effect tests
  • Ruff check passed on all changed files
  • git diff --check passed

Context

Run 00228936-d7c2-4287-881a-34f09987275d failed with invalid_group_at after staging one Agent and one human participant. The lower-level group message service already treats human mentions as public-only, but Runtime preflight incorrectly required every staged participant to be a wakeable Agent.

Native group replies already persist human mentions without dispatching work, but the Runtime at preflight rejected every non-Agent participant. Split public mention validation from Agent handoff validation so mixed human and Agent targets remain atomic while child Runs are created only for wakeable Agents.

Constraint: Human mentions must remain visible without creating child Runs.

Rejected: Strip human IDs during model repair | loses structured mention metadata and contradicts group message behavior.

Confidence: high

Scope-risk: narrow

Directive: Keep public mention targets distinct from wakeable Agent targets.

Tested: 232 scoped Runtime and group delivery tests; Ruff check on changed files.

Not-tested: Browser rendering and live 3010 mixed-mention E2E pending deployment.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant