Telegram Reminders + Cross-Cycle Agent Memory

Interactive reminders now reach you on Telegram, and agents carry context between execution cycles for smarter continuity.

Two improvements to how agents stay in touch with you and maintain their own continuity.

Interactive Reminders Now Reach You On Telegram

When a plan is blocked on your input — whether it is an ASK_USER question, a CHOICE decision, or a CALL_TO_ACTION link — the system already sends in-app and email reminders. Now those reminders are also delivered to Telegram if you have a linked session.

  • Same content, new channel — You get the same reminder prompt on Telegram so you can respond from wherever you are
  • No extra setup required — If your Telegram session is linked, reminders appear automatically
  • Non-blocking delivery — If Telegram delivery fails (network issues, session expired), the other channels still work normally

This is especially useful for long-running plans where you may not be watching the web dashboard. Instead of agents waiting silently, they can nudge you on the messaging platform you are already using.

Cross-Cycle Context: Agents Remember What Happened Last Time

When an agent starts a new execution cycle, it now receives structured output from its previous completed cycle.

  • Run numbering — Each execution cycle has a clear run number, making it easier to track which cycle you are looking at
  • Previous cycle outputs — The system passes the last completed cycle's structured outputs forward, so the agent does not start from zero every time
  • No configuration needed — This works automatically for any process that runs repeatedly

The practical effect: agents that work in iterative loops (like dev loops) can make decisions informed by what they built, tested, or discovered in the previous cycle — without fragile workarounds or manual context injection.