You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
start_time was added as required to swarm-orchestrate.ts and the MCP schema in swarm-tools/index.ts was updated, but the plugin wrapper template was never synced.
Additional finding: start_time is not just missing from the plugin bridge — it's missing from the entire worker lifecycle:
swarm_spawn_subtask doesn't generate or return a start_time
SUBTASK_PROMPT_V2 (Step 9, the swarm_complete example) doesn't mention start_time
No event in the spawn chain records a start timestamp for the worker to reference
So even if the plugin bridge exposed start_time, workers would have no value to pass. The parameter was added to swarm-orchestrate.ts but never wired through the spawn → work → complete lifecycle.
Suggested full fix: either
Have swarm_spawn_subtask include start_time: Date.now() in its return JSON (and update SUBTASK_PROMPT_V2 Step 9 to pass it through), or
Make start_time optional in swarm_complete and default to Date.now() (accepting inaccurate duration for workers that don't track it)
We hit this same bug independently and have a fix PR: #185 (makes start_time optional with Date.now() default across all 3 plugin wrappers + updated tests). Happy to get vouched if this would be useful to merge.
Confirmed on 0.63.2 (OpenCode 1.18.18, Windows): a swarm-worker following the spawn prompt had to retry swarm_complete 3 times discovering the undocumented required start_time (ISO string) parameter, since the generated spawn prompt/checklist doesn't mention it. Either defaulting start_time server-side (to the spawn/registration time) or documenting it in the worker prompt would remove that friction.
Activity
mrm007 commentedon Mar 1, 2026
Additional finding:
start_timeis not just missing from the plugin bridge — it's missing from the entire worker lifecycle:swarm_spawn_subtaskdoesn't generate or return astart_timeSUBTASK_PROMPT_V2(Step 9, theswarm_completeexample) doesn't mentionstart_timeSo even if the plugin bridge exposed
start_time, workers would have no value to pass. The parameter was added toswarm-orchestrate.tsbut never wired through the spawn → work → complete lifecycle.Suggested full fix: either
swarm_spawn_subtaskincludestart_time: Date.now()in its return JSON (and updateSUBTASK_PROMPT_V2Step 9 to pass it through), orstart_timeoptional inswarm_completeand default toDate.now()(accepting inaccurate duration for workers that don't track it)Krule commentedon Mar 22, 2026
We hit this same bug independently and have a fix PR: #185 (makes start_time optional with Date.now() default across all 3 plugin wrappers + updated tests). Happy to get vouched if this would be useful to merge.
danielacevedos commentedon Aug 14, 2026
Confirmed on 0.63.2 (OpenCode 1.18.18, Windows): a
swarm-workerfollowing the spawn prompt had to retryswarm_complete3 times discovering the undocumented requiredstart_time(ISO string) parameter, since the generated spawn prompt/checklist doesn't mention it. Either defaultingstart_timeserver-side (to the spawn/registration time) or documenting it in the worker prompt would remove that friction.