Put recurring checks on a routine
Create the recurring instruction once, review its schedule and run history, and return to the completed result in Briefs.
For operators, founders, and independent workers who repeatedly check the same source, reconcile the same inputs, or prepare the same update.
The situation
The check is small enough to postpone and important enough to regret missing, so it keeps borrowing attention and still sometimes slips.
Proven in 0.16.91
Published 2026-08-05. Verified against public release source commit ff4ce85f5e4a7219d728a6ea0f177697f12aad0e.
- Routines can be created, searched, edited, paused, resumed, run, and deleted.
- Routine details include schedules and run history.
- Briefs is the current-release destination for finished scheduled work.
Depends on your setup
A real check succeeds only when its required websites, files, credentials, or connected tools are available and permitted.
Try one real task
Copy this into Kryden and replace anything in brackets.
“Every weekday at 9:00 AM, check [source], summarize what changed since the last run, and put anything that needs my decision at the top. Do not take follow-up actions without asking.”
When Kryden is not the answer
Kryden is not a monitoring guarantee or a substitute for an alerting system with contractual uptime. A routine also needs reliable access to every source it checks.
Give the work somewhere to continue.
Download the current public release for Apple Silicon macOS 12+ or Windows x64 10+.
Questions this choice usually raises
Can I change or pause a routine?
Yes. Release 0.16.91 includes edit, pause, resume, run, and delete controls for routines.
Where do routine results appear?
Finished scheduled work lands in Briefs. Failed runs can also be shown rather than presented as successful results.