Skip to content

feat(routines): let a routine's result ask for someone, and stay quiet when there's nothing to report - #661

Draft
tjholm wants to merge 1 commit into
mainfrom
routine-result-mentions
Draft

tjholm wants to merge 1 commit into
mainfrom
routine-result-mentions

Conversation

@tjholm

@tjholm tjholm commented Nov 13, 2026

Copy link
Copy Markdown
Member

A routine's result now says how much it matters through the message itself, the way a Slack message does:

  • Nothing to report: the bot writes nothing after its last tool call. Nothing is posted, the run shows "Nothing to report", and Inbox leaves it out.
  • Needs someone: the result @mentions them. That notifies them even when the result stays in the routine's own thread, and their Inbox shows the run as "needs you". By default the bot mentions whoever made the routine or started the run.
  • Failed: unchanged.

Inbox now counts a run as unread only once it posts a result or fails, from when it ended.

This is a first cut that is easy to change. It adds no migration, setting or tool, and works out each run's status from what it posted. If testing shows bots don't reliably stay quiet or mention the right people, a heavier version can replace it: a stored importance the bot sets through a tool. The Inbox and notification changes carry over to that.

The docs will follow once the behaviour settles.

@cloudflare-workers-and-pages

Copy link
Copy Markdown

Deploying with  Cloudflare Workers  Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status Name Latest Commit Updated (UTC)
✅ Deployment successful!
View logs
sugabots-website 808ff53 Nov 13 2026, 03:08 AM

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