Replies: 2 comments
|
@mhenke originally wrote: This was generated by AI during triage. There is no scheduler in the plugin. Every timer we have is internal polling or a delay for shutdowns and retries. OpenCode hooks fire on user actions like sending a message or running a tool, not on a clock. A recurring callback would be new. A few things to settle: what should trigger the callback (a timer, a condition, or a manual command)? Does it need to survive a process restart? And what is the concrete use case you have in mind? |
|
@mhenke originally wrote: This was generated by AI during triage. There is no scheduler in the plugin. Every timer we have is internal polling or a delay for shutdowns and retries. OpenCode hooks fire on user actions like sending a message or running a tool, not on a clock. A recurring callback would be new. A few things to settle: what should trigger the callback (a timer, a condition, or a manual command)? Does it need to survive a process restart? And what is the concrete use case you have in mind? |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Originally tracked in issue #470.
Description
Allow orchestrator to schedule longer interval callbacks, minutes
Extra context
No response
All reactions