luigidemasi opened a new issue, #95: URL: https://github.com/apache/camel-kit/issues/95
> Imported from [luigidemasi/camel-kit#224](https://github.com/luigidemasi/camel-kit/issues/224), opened by [luigidemasi](https://github.com/luigidemasi) on 2026-09-09. --- Parent tracker: https://github.com/luigidemasi/camel-kit/issues/221 Website follow-up: https://github.com/luigidemasi/camel-kit-web/issues/45 ## Description Allow Camel Ship invoked from Google Antigravity to use that host's own native subagents for its AI stages, using the shared controller handoff defined in the parent tracker. The parent asks Ship for pending work, dispatches a native worker, and relays its structured result and artifacts. Ship retains state transitions, oversight, deterministic validation, and publication. ## Agent-specific work Use the existing `invoke_subagent` integration and generated roles. Preserve the parent-owned decision/report model, inherited permissions, and current MCP configuration. Keep bounded workers from requiring nested subagent dispatch; verify actual cancellation and recovery capabilities. Reuse the existing [dispatch template](https://github.com/luigidemasi/camel-kit/blob/9fa9771e15b3648b999883c4005de9f6383061b4/camel-kit-core/src/main/resources/templates/dispatch/antigravity.md) and [agent registry entry](https://github.com/luigidemasi/camel-kit/blob/9fa9771e15b3648b999883c4005de9f6383061b4/camel-kit-core/src/main/resources/agents/registry/antigravity.yaml). Preserve this target's established execution model and restrictions wherever native integration is unavailable or incompatible; do not replace it with an invented fallback model. ## Acceptance criteria - [ ] Integrate with the shared task/result and recovery contract; the shared controller work in the parent is a dependency. - [ ] Generate the correct Ship entry point for fresh and reinitialized workspaces, including standalone and JBang-plugin command prefixes. - [ ] Run a real native child through the registered entry point and complete the workflow with independently verified artifacts and deterministic validation. - [ ] Verify oversight pauses, resume after parent/child interruption, abort/timeout, idempotent repeated submissions, rejection of stale/conflicting results, and workspace/tool restrictions under the shared acceptance suite. - [ ] Persist and accurately report the execution mode; do not silently change backend during a run. - [ ] Keep unsupported/special execution behavior intact and document any concrete capability boundary. Generated files or mocks alone are not evidence of native support. - [ ] Pass focused regression/resource tests, the required full Maven wrapper/source checks, and the relevant hosted CI. - [ ] Update core help/docs and the linked website follow-up for the implemented behavior. **Website impact: required.** Document Google Antigravity's verified native Ship behavior, prerequisites, and recovery limits in the linked follow-up. -- 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]
