Repository navigation
Scheduled tasks: decide how schedules bind to a Squadron #273
Description
Activity
Jackson (2026-09-28): this is a gap to fill, not a divergence to keep. There are two ways to create a scheduled task:
- An agent schedules work for itself (
bindToCurrentThread=true). This works today, because the thread already has a Squadron home. - The person creates one in the UI (Settings → Automations). Its new thread has no Squadron, so every fire fails. That makes upstream's default scheduled tasks unusable in J5.
J5 should support the second path. The UI flow needs a Squadron choice (#38); the server then launches the new thread into that Squadron instead of refusing. Tracked as a divergence to retire in the register (
docs/j5/product/upstream.md, #329).- An agent schedules work for itself (
FORK.md case 12 refuses to create scheduled tasks that aren't bound to the current thread, because a new thread must have an explicit Squadron home. In #262, upstream now supports scheduled tasks across environments, with
bindToCurrentThread=falsecreating fresh threads, and routes them through its sharedScheduler.Design how an unbound schedule gets a Squadron home, for example the scheduling thread's Squadron or an explicit
squadron_id. Then retire the refusal, or keep it deliberately and say why in FORK.md.