luigidemasi opened a new issue, #67: URL: https://github.com/apache/camel-kit/issues/67
> Imported from [luigidemasi/camel-kit#119](https://github.com/luigidemasi/camel-kit/issues/119), opened by [luigidemasi](https://github.com/luigidemasi) on 2026-06-28. > Closed by [luigidemasi/camel-kit#120](https://github.com/luigidemasi/camel-kit/pull/120), merged on 2026-06-29. --- ## Description IBM Bob 2 introduces native skills, subagents, parallel subagent/tool execution, updated custom mode groups, and a simplified Agent/Plan/Ask mode model. Camel Kit should add Bob 2 support as a new AI target instead of replacing the existing Bob support in place. The new target should be selected with: ```bash camel-kit init my-integration --ai bob2 ``` The existing `--ai bob` target should remain available as Bob 1 legacy support during the transition. This avoids breaking users who are still on Bob 1 or waiting for Bob Shell 2. ## Expected Behavior - `camel-kit init --ai bob2` is accepted by the CLI. - `--ai bob` continues to generate the current Bob 1 workspace. - `--ai bob2` generates Bob workspace files under `.bob/`, since Bob IDE reads `.bob/commands`, `.bob/skills`, `.bob/custom_modes.yaml`, and `.bob/mcp.json`. - Bob 2 generated skills use the shared Camel Kit skill architecture rather than Bob 1 monolithic gate replacement. - Bob 2 traits use Bob 2 native `spawn_subagent` behavior for isolated research, review, implementation, testing, and fix tasks. - Bob 2 custom modes use the Bob 2 tool group names, especially `execute` instead of the old `command` group. - Documentation and CLI help distinguish `bob` as legacy Bob 1 and `bob2` as Bob 2. ## Proposed Implementation - Add a new `bob2` agent descriptor. - Add a `Bob2Generator`. - Add Bob 2 templates under `templates/bob2/`. - Add Bob 2 traits under `templates/traits/bob2/`. - Add a Bob 2 dispatch template that names `spawn_subagent`, `explore`, `general`, and `fork_context`. - Keep the existing `bob` descriptor, generator, gate files, and tests initially. - Reuse the existing Bob MCP config path and template where possible. - Keep generated output under `.bob/...` for both `bob` and `bob2`; the difference is the Camel Kit generator target, not the Bob workspace folder. ## Acceptance Criteria - `bob2` appears in supported AI agent choices. - `camel-kit init --ai bob2` generates a valid Bob 2 workspace. - `camel-kit init --ai bob` still works unchanged. - `bob2` descriptor has subagent support enabled and does not advertise monolithic gates. - `bob2` generated custom modes use `execute`, `skill`, `subagent`, and `mode` where appropriate. - `bob2` generated skills retain shared `SKILL.md` content with Bob 2-specific traits appended. - `bob2` command stubs include Bob-compatible frontmatter such as `description`. - Tests cover the new `bob2` target without weakening legacy `bob` tests. - README/user guide/architecture docs describe the split between `bob` and `bob2`. ## Additional Context Bob 2 support should be added conservatively. The default can remain `bob` until Bob Shell 2 is available and tested, then the project can decide whether to make Bob 2 the default or rename/remove the legacy Bob 1 target. -- 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]
