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


##########
docs/modules/ROOT/pages/ship.adoc:
##########
@@ -201,6 +201,13 @@ certification.
   custom agent, which declares `commandExecutionPolicy: "off"`, `inheritMcp: 
false` and only read and search tools.
   Unlike the general `camel-worker` and `camel-reviewer` agents, the Ship 
worker does not inherit MCP servers.
   The skill respects Antigravity's permission prompts and sandbox settings.
+
+| Qwen Code
+| `/camel-ship` from the generated skill in a session that exposes the 
`camel-ship-worker` named agent, which declares
+  `approvalMode: default`, an explicit read-only `tools:` allowlist and 
`disallowedTools: [agent]`. The skill never
+  uses `fork` or `fork_turns`; dispatch is through the named-agent mechanism. 
If `--backend qwen-native` is requested
+  and dispatch is unavailable the skill stops without starting a run. 
Generated skill and worker assets verified on
+  Qwen Code 0.25.3 (parser/command-loader probe); live child execution 
acceptance is pending.

Review Comment:
   Thanks for the detailed feedback — you're right that the parser/loader probe 
confirms asset loading but doesn't exercise a real native workflow. Ship's 
requireLinux() constraint means I'd need an authenticated Linux environment 
with Qwen Code to run the full acceptance which I don't have set up at the 
moment. 



-- 
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