Skip to content

Wake agents from verified workflow mentions - #6965

Draft
loganj wants to merge 6 commits into
larry/workflow-revision-foundation-v4from
larry/workflow-auto-mention-wake-v4
Draft

Wake agents from verified workflow mentions#6965
loganj wants to merge 6 commits into
larry/workflow-revision-foundation-v4from
larry/workflow-auto-mention-wake-v4

Conversation

@loganj

@loganj loganj commented Aug 27, 2026

Copy link
Copy Markdown
Collaborator

🤖 I’m Larry.

Summary

When a workflow-generated message explicitly mentions an agent, that agent can now wake automatically and handle the message once. The notification itself carries no instructions: the agent retrieves the exact workflow revision and generated message from the relay, verifies them, and only then executes the referenced workflow step.

Details

  • Emits an ephemeral, identifier-only notification for each unambiguously resolved mentioned channel member through the relay’s existing delivery path.
  • Restricts notification delivery and authority retrieval to the authenticated recipient with current relay and channel access, so removing a member revokes old notifications.
  • Ensures each workflow-generated message enters the agent harness only through the verified notification path, preventing duplicate turns while preserving ordinary relay-message dispatch.
  • Preserves existing sender policy by evaluating the verified author of the signed workflow definition, not the relay that generated the message.
  • Verifies the exact run, signed definition revision, generated message, recipient, referenced send_message step, and target channel before execution.
  • Keeps older runs compatible: they still send messages, but runs without a captured signed revision do not wake agents automatically.

Stack

  • Depends on Persist exact workflow revisions additively #6960, which captures the exact signed workflow revision for each new run.
  • This PR adds automatic mention waking only; manual owner-trigger behavior and legacy migration remain separate slices.

loganj and others added 4 commits August 27, 2026 17:46
Signed-off-by: Logan Johnson <loganj@squareup.com>
Co-authored-by: Larry <8cf5a83f590ec0955b11647d1c88f796a98e088c30a492c58e0e46c3026ae7a4@buzz.block.builderlab.xyz>
Signed-off-by: Logan Johnson <loganj@squareup.com>
Co-authored-by: Larry <8cf5a83f590ec0955b11647d1c88f796a98e088c30a492c58e0e46c3026ae7a4@buzz.block.builderlab.xyz>
Co-authored-by: Larry <8cf5a83f590ec0955b11647d1c88f796a98e088c30a492c58e0e46c3026ae7a4@buzz.block.builderlab.xyz>
Signed-off-by: Logan Johnson <loganj@squareup.com>
Co-authored-by: Larry <8cf5a83f590ec0955b11647d1c88f796a98e088c30a492c58e0e46c3026ae7a4@buzz.block.builderlab.xyz>
Signed-off-by: Logan Johnson <loganj@squareup.com>
@ryanshepps

Copy link
Copy Markdown

Need this!

Larry and others added 2 commits August 27, 2026 21:43
Persist recipient-gated identifier wakes, include them in default ACP mention subscriptions, and preserve safe channel wildcards.

Co-authored-by: Larry <larry@buzz.local>
Signed-off-by: Larry <8cf5a83f590ec0955b11647d1c88f796a98e088c30a492c58e0e46c3026ae7a4@buzz.block.builderlab.xyz>
Reject client-authored wakes, authenticate relay signatures before authority lookup, and preserve the storage-level FTS exclusion on brownfield databases.

Co-authored-by: Larry <8cf5a83f590ec0955b11647d1c88f796a98e088c30a492c58e0e46c3026ae7a4@buzz.block.builderlab.xyz>
Signed-off-by: Logan Johnson <loganj@squareup.com>
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.

2 participants