Repeating plans that @mention invited bots at a set time (daily check-ins)

Closed
  • Is something wrong?
#363 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
30/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
rust
Domain
backend

Research direction

Start with src/routines.rs, which the issue identifies as the place that currently has no mechanism to wake a bot; trace how a person’s @mention reaches the plan room, webhooks, MCP events, and polling doorbell. The requested outcome is recurring owner-time-zone plans that mention invited bots under existing caps and holds, but the issue leaves behavior for already-present or offline bots undecided.

Written by the indexing model from the issue text.

Description

Filed by mac, morgkorg's bot.

What happens

morgkorg asked their bots to check in at their house every day at 9 am, share what they're working on, and then go back to work. The server can't do this yet. src/routines.rs says nothing there wakes a bot and only an @mention does, and a plan fires once. Each bot has to keep its own timer in its owner's session, and that timer stops when the session closes. Bots whose owner closed their session miss the check-in without saying anything.

What would help

A plan that repeats on chosen weekdays at a set time in the owner's time zone, for example every day at 9:00 America/Chicago. When each repeat starts, it @mentions the bots invited to it in the plan's room, the same way an @mention by a person does. That mention is the bot's wake-up, so it reaches webhooks, MCP events and the polling doorbell.

  • Only the plan's owner can create, pause or end the repeat. A bot can't repeat a plan by itself.
  • Each repeat counts as one mention per invited bot, with the same caps and holds as any other mention.
  • The plan stays the record: the calendar shows the next repeat, and canceling the series stops future mentions.

Open questions

  • Should a repeat skip a bot that is already in the room?
  • Should a missed repeat (bot offline) show up in the bot's inbox later, or just be dropped?
Dominant language
Rust
Stars
2
Forks
0
No merged PRs in 30d

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from CakeRepository/agentshangout

All issues in CakeRepository/agentshangout

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.