Scheduled tasks support inspired by Claude Code /loop — feedback wanted

[grinev]

Hi everyone!

I recently added scheduled tasks support to OpenCode Telegram Bot, inspired by Claude Code’s /loop command (re-running prompts on an interval while a session is open).

In our bot, the goal is a bit different: make recurring and delayed coding tasks practical from Telegram, with minimal setup.

How it works is described here: https://github.com/grinev/opencode-telegram-bot#scheduled-tasks

Quick highlights:

• tasks are created from the currently selected project and model
• scheduled runs currently use the build agent
• runs are executed outside active chat session flow (so they do not interrupt current session work)
• minimum recurring interval is 5 minutes
• default max is 10 tasks (configurable via TASK_LIMIT)

I’d really like your feedback:

1. Is this useful in its current form?
2. What real workflows would you use it for?
3. What is missing for your daily usage?
4. Can this now be a practical lightweight alternative to OpenClaw for OpenCode-focused workflows?

Thanks — any examples, ideas, or criticism are very welcome.

[shanekunz]

@grinev This is a great idea.

It could also be useful for:

• My original idea on OpenClaw was to give an agent loop a ton of tasks and have it iterate on those tasks via spawning opencode instances throughout the night. My results were bad, but I think with a lighter opencode loop harness like this and something like https://github.com/steveyegge/beads I would like to try the idea again.
• Daily project reports based on what PRs are open in my project and due dates on my Linear board (via opencode mcps).
• Persistent daily code reviews and code quality clean up.

The only thing I suggest is that when it posts the results of the cron, it gives you the title or summary of the cron prompt you've set up so you know what cron the response relates to, and not cluttering your telegram messages with tool calls for background crons. On the fork, I would probably just have a single dedicated group topic for the crons for that project.

[grinev]

@shanekunz it works as you described, for scheduled task you see only final message, no tool calls

[shanekunz]

@grinev sweet, will merge in the changes now.