Jinal-Sarvaiya commented on code in PR #149:
URL: https://github.com/apache/camel-kit/pull/149#discussion_r4478317023


##########
kit/camel-kit-core/src/main/resources/templates/traits/opencode/camel-execute.append.md:
##########
@@ -8,9 +8,9 @@
 primary executor session -> leaf agent
 ```
 
-The executor may dispatch only the generated `implementer`, `migrator`, 
`planner`, `researcher`, `reviewer`, and `tester` agents. Every leaf denies 
`task`, so it cannot create another child. This generated one-level topology 
does not require a development-only configuration key.
+The executor may dispatch only the generated `implementer`, `migrator`, 
`planner`, `researcher`, `reviewer`, and `tester` agents. Every leaf denies 
`subagent`, so it cannot create another child. This generated one-level 
topology does not require a development-only configuration key.
 
-OpenCode's `task` tool requires the exact lowercase agent name in 
`subagent_type`. It does not accept a per-call `steps` argument; each generated 
agent definition owns its limit. Foreground is the default. Keep every 
implementation, research result, and review gate in the foreground by omitting 
`background`.
+OpenCode's `subagent` tool requires the exact lowercase agent name in `agent`. 
It does not accept a per-call `steps` argument; each generated agent definition 
owns its limit. Foreground is the default. Keep every implementation, research 
result, and review gate in the foreground by omitting `background`.

Review Comment:
   Migrated both references in `dispatch/opencode.md` from 
`task`/`subagent_type` to `subagent`/`agent`, matching the trait updated in 
034d4cc1. The dispatch template is the shared template appended to all non-Ship 
skills, so it must use the same API contract as the trait.



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to