Design, implement, and verify Apache Camel integrations with AI coding assistants.
Camel-Kit adds structured AI-agent workflows to your assistant that guide you through the full integration lifecycle — from designing the integration, through implementation and testing, to runtime verification. It works across multiple AI agents and produces production-ready Apache Camel routes.
Inspired by GitHub Spec-Kit, adapted for the Apache Camel ecosystem.
Entry: /camel-start (routes migration, planning, execution, validation,
debugging, or greenfield work based on context)
Greenfield: /camel-brainstorm → /camel-plan → /camel-execute → /camel-validate
├── implements (camel-implement)
├── verifies (camel-verify, internal)
└── tests (camel-test)
Migration: /camel-migrate → /camel-plan → /camel-execute → /camel-validate
Utilities: /camel-ship (Technology Preview — delegate to the local Ship controller)
/camel-knowledge (documentation Q&A)
/camel-debug (standalone troubleshooting)
| Command | Purpose |
|---|---|
/camel-start |
Entry point — routes migration sources to migrate, approved designs to plan, ready plans to execute, generated routes to validate, broken projects outside a pipeline to debug, and other work to brainstorm |
/camel-brainstorm |
Interactive design session — produces business requirements and a design spec |
/camel-migrate |
Migration from MuleSoft, Microsoft BizTalk, legacy Camel, or JBoss Fuse to modern Camel |
/camel-plan |
Reviews approved design, creates a detailed implementation plan with wave analysis for parallel execution |
/camel-execute |
Orchestrated execution — probes the environment, implements tasks in dependency waves, runs adversarial/spec/quality reviews, and performs applicable smoke and runtime verification |
/camel-validate |
Final static quality gate or standalone project check — covers schema, endpoints, quality, security, anti-patterns, and constitution compliance without modifying routes |
/camel-debug |
Standalone troubleshooting outside a pipeline for broken routes, build failures, startup errors, and runtime exceptions |
/camel-ship |
Technology Preview. Thin harness entry point for the local Ship controller, which owns the end-to-end run and configurable oversight (always, smart, never) |
/camel-knowledge |
Documentation Q&A — semantic search over Apache Camel docs, CVE advisories, release notes, and component catalog |
| Requirement | Purpose | Install |
|---|---|---|
| Java 17+ | Runtime | SDKMAN, Adoptium, or your package manager |
| JBang | CLI launcher for camel-kit | See below |
| Camel JBang | camel run, camel run --check for route execution and validation |
jbang app install camel@apache/camel |
| Camel JBang test plugin | camel test run for Citrus integration tests in the verify loop |
camel plugin add test |
| Docker | Conditional: external-service probes and full Citrus/Testcontainers verification | Install Docker Engine or Docker Desktop |
Camel JBang and its test plugin are needed for the complete execution and verification loops. Docker-dependent checks are reported as skipped when Docker is unavailable; design, planning, and checks that do not need containers still work.
Technology Preview: Camel Ship is still being stabilized. Its behavior and interfaces may change, and it is not recommended for production use. For the established staged workflow, start with /camel-start.
The optional Ship controller requires Linux and supports Camel Main projects with YAML DSL routes. Its default backend requires Pi and Node. Bob 2, GitHub Copilot CLI and Claude Code can use their own read-only native subagents through the generated Ship skill; the controller writes their proposals and validates the result. See Bob native Ship, Copilot native Ship and Claude Code native Ship. The maintained versions are Pi 0.84.2 or 0.83.0 with Node 22.22.2; unverified versions run only with --accept-experimental, while explicitly incompatible versions remain rejected. See camel-ship for the complete contract.
camel-kit init checks Java, JBang, Camel JBang, and the Camel test plugin. Missing tools produce warnings but don't block initialization; Docker and Ship prerequisites are checked when those workflows run.
This guide describes Camel Kit 0.4.1, paired with Knowledge MCP 0.0.2. Ship remains a Technology Preview and is not recommended for production use.
| Channel | Install source | Version |
|---|---|---|
| Release | Tagged JBang catalog or Maven Central plugin | 0.4.1 |
| Development | Default GitHub JBang catalog or a source build | 0.4.2-SNAPSHOT |
Both command surfaces provide init, doctor, doc, graph, plan, nextId, and ship,
and all eight AI targets documented below. Pin the release when you need reproducible installation.
The unqualified GitHub alias follows development; hosted snapshots are mutable and may lag main.
# Install JBang (if not already installed)
curl -Ls https://sh.jbang.dev | bash -s - app setup # Linux/macOS
iex "& { $(iwr -useb https://ps.jbang.dev) } app setup" # Windows PowerShell
# Install the release globally
jbang app install camel-kit@luigidemasi/camel-kit/camel-kit-0.4.1
# Verify: prints 0.4.1
camel-kit --versionjbang run camel-kit@luigidemasi/camel-kit/camel-kit-0.4.1 init my-integration --ai claudeIf you already use Camel JBang, install Camel Kit as a plugin:
camel plugin add kit \
--gav io.github.luigidemasi:camel-jbang-plugin-kit:0.4.1 \
--description "Design Apache Camel Integrations with AI"
camel kit init my-integration --ai claudeTo upgrade from 0.3.1, reinstall the plugin at 0.4.1. The retired bob and gemini
targets are replaced by bob2 (the default) and antigravity; see the
migration instructions. Back up customized generated files before reinitializing with --force.
Camel Main, Camel Spring Boot, and Camel MCP now default to 4.22.1; the supported
older LTS patch remains 4.18.4. Spring Boot uses 4.1.1, matching the published Camel
Spring Boot release. Quarkus retains its independently aligned platform versions.
Camel 4.22.1 maps to Forage 1.6.1, including its InfluxDB 1 and 2 client factories for
Camel Main and Spring Boot. The existing 4.22.0 to Forage 1.6.0 mapping remains.
Version 0.4.1 updates shared generation and review guidance to prefer verified declarative
bean construction after Forage and component configuration. Knowledge MCP 0.0.2 aligns endpoint validation
with the Camel 4.22.1 catalog.
Reinstall the standalone CLI with jbang app install --force camel-kit@luigidemasi/camel-kit/camel-kit-0.4.1,
or rerun the plugin installation above. To apply the updated guidance to an existing project,
commit or back up customized generated files, then run camel-kit init --here --ai <your-agent> --force
(or camel kit init --here --ai <your-agent> --force). This rewrites generated assets.
jbang app install --force camel-kit@luigidemasi/camel-kitThis installs the latest deployed 0.4.2-SNAPSHOT. Build from source for a specific revision.
Build from source to use the current snapshot without waiting for the published snapshot artifact:
git clone https://github.com/luigidemasi/camel-kit.git
cd camel-kit
./mvnw clean install -DskipTests
# Install the development version globally via JBang
jbang app install --name camel-kit --force \
camel-kit-main/src/main/jbang/main/CamelKit.java
# Or install the matching Camel plugin from the local Maven repository
camel plugin add kit \
--gav io.github.luigidemasi:camel-jbang-plugin-kit:0.4.2-SNAPSHOT \
--description "Design Apache Camel Integrations with AI"
# Verify
camel-kit --helpTo also build the Knowledge MCP server (documentation search, CVE tracking, component catalog):
git clone https://github.com/luigidemasi/camel-kit-knowledge.git
cd camel-kit-knowledge
./mvnw clean install -DskipTestsThe examples below use the 0.4.1 release.
# 1. Create a new project (choose your AI assistant)
camel-kit init my-integration # IBM Bob 2 (default)
camel-kit init my-integration --ai claude # Anthropic Claude Code
camel-kit init my-integration --ai bob2 # IBM Bob 2
camel-kit init my-integration --ai antigravity # Google Antigravity
camel-kit init my-integration --ai codex # OpenAI Codex CLI
camel-kit init my-integration --ai copilot # GitHub Copilot CLI
camel-kit init my-integration --ai pi # Pi
camel-kit init my-integration --ai qwen # Qwen
camel-kit init my-integration --ai opencode # OpenCode
# 2. Override configuration if needed
camel-kit init my-integration --ai claude -p "camel.main.version=4.18.4"
# 3. Open in your AI assistant
cd my-integration
# 4. Start designing
/camel-start
# For GitHub Copilot CLI, ask Copilot: "Use the /camel-start skill."
# Run /skills list if you need to inspect available project skills.
# For Codex CLI, trust the repository, then run $camel-start.
# Use /skills to inspect project skills and /mcp to inspect MCP servers.
# For Pi, install the MCP adapter, trust the project, then run /skill:camel-start.
# pi install npm:pi-mcp-adapter@2.11.0init generates the row selected by --ai; these are alternative target layouts, not one combined project tree.
| Agent | Init Flag | Primary Generated Assets | MCP Config |
|---|---|---|---|
| Anthropic Claude Code | --ai claude |
CLAUDE.md + .claude/commands/ + .claude/skills/ |
.mcp.json |
| IBM Bob 2 (default) | --ai bob2 |
.bob/custom_modes.yaml + rules + shared .bob/skills/ + scoped .bob/agents/ + .bob/personas/ |
.bob/mcp.json |
| Google Antigravity | --ai antigravity |
AGENTS.md + .agents/skills/ + .agents/agents/ + .agents/camel-kit-personas/ |
.agents/mcp_config.json |
| OpenAI Codex CLI | --ai codex |
AGENTS.md + .agents/skills/ + .codex/agents/ |
.codex/config.toml |
| GitHub Copilot CLI | --ai copilot |
.github/copilot-instructions.md + .github/agents/ + .github/skills/ |
.github/mcp.json |
| Pi | --ai pi |
AGENTS.md + .pi/skills/ + .pi/prompts/ + guard extension/policy |
.mcp.json via pi-mcp-adapter |
| Qwen | --ai qwen |
QWEN.md + .qwen/commands/ + .qwen/skills/ + .qwen/agents/ + .qwen/camel-kit-personas/ |
.qwen/settings.json |
| OpenCode | --ai opencode |
AGENTS.md + .opencode/commands/ + .opencode/skills/ + .opencode/agents/ + .opencode/camel-kit-personas/ |
opencode.json (default) |
All supported targets use shared markdown skills with agent-specific traits and native configuration.
See Antigravity setup and migration from Gemini or Bob v1.
- 4-step orchestrated pipeline — brainstorm or migrate, plan, execute, then validate. Execute performs the environment probe, dependency-wave implementation, adversarial/spec/quality reviews, and applicable smoke and internal runtime verification before the final static validation gate. Learn more →
- Local Ship controller (Technology Preview) —
/camel-shipdelegates to the configuredcamel-kit shiporcamel kit shipcommand. The controller, rather than the AI harness, owns run state, stage transitions, validation evidence, and guarded publication, withalways,smart, andneveroversight. Learn more → - Environment probe — validates the target environment (dependency resolution, Docker services, runtime startup) before implementation begins. Mechanical failures are auto-fixed; architectural failures trigger re-planning. Learn more →
- Wave analysis — the plan analyzer uses structured task metadata, logical dependencies, and file overlap to group independent tasks into parallel execution waves.
- Deterministic staleness detection —
doc check,doc stale, anddoc unstaleCLI commands manage pipeline artifact validity via structured YAML frontmatter, with--cascadefor automatic downstream propagation. Learn more →
- 3-phase verification loop — build, run Citrus integration tests with Testcontainers, report results. Error taxonomy classifies failures and routes fixes to the right skill (implementation, test re-generation, or re-planning). Learn more →
- Multi-platform migration — migrate from MuleSoft 3.x/4.x, Microsoft BizTalk, legacy Apache Camel 2.x/3.x, or JBoss Fuse to modern Camel 4.x with YAML DSL. Learn more →
- 9 parsers + 2 post-processors — build a queryable property graph of your codebase covering Java classes, Camel routes (XML, YAML, Java DSL, Groovy), Maven dependencies, configuration properties, MuleSoft flows, DataWeave scripts, and BizTalk orchestrations. Learn more →
- DI-aware analysis — detects
@Inject,@Autowired,@Value,@ConfigProperty,@Component,@Serviceannotations and traces dependencies across interface boundaries. Inspired by Chinthareddy, "Reliable Graph-RAG for Codebases" (2026). Learn more → - Migration context —
graph migration-context <routeId>performs a bounded local graph traversal (breadth-first, depth 3 by default, capped at 50 related nodes) and reports detected routes, components, services, artifacts, properties, and inferred-node warnings. It neither queries the Knowledge MCP nor guarantees a complete dependency chain. Learn more → - PropertyBindingSupport analysis — understands Camel's
#class:,#bean:,#autowiredproperty syntax that instantiates and wires beans fromapplication.properties. Learn more →
- MCP integration — real-time catalog queries, route validation, security analysis, documentation lookup, and Citrus test-generation metadata via MCP servers. Learn more →
- Knowledge layer — hybrid BM25 + vector search over Apache Camel documentation, component catalogs, release notes, and CVE advisories ingested from
apache/camel-website, with best-effort NVD enrichment and a CIRCL fallback during index rebuilds. The target-specific MCP tool contract is defined in the workflow manifest. Learn more → - DataMapper — automatic data transformation with two engines: XSLT for complex schema-driven mappings, Groovy for simple field-level transformations. Learn more →
- 8 AI targets — Camel-Kit supports Claude Code, IBM Bob 2, Google Antigravity, OpenAI Codex CLI, GitHub Copilot CLI, Pi, Qwen, and OpenCode. Agent-specific traits adapt the shared skills to each target. Learn more →
Workflow examples and migration samples live in camel-kit-examples:
- User Guide — workflows, migration, verification, DataMapper
- Command Reference — CLI options, AI-agent workflows, graph subcommands
- Architecture Guide — skills, MCP, graph intelligence, pipeline internals
- Contributing — development setup, how to add skills
Workflow contributors should treat camel-kit-core/src/main/resources/workflow/camel-kit-workflow.yaml as the source of truth for command, skill, stage, artifact, and MCP tool metadata before updating generated templates or reference docs.
See Releasing for the maintainer publication procedure.
Apache License 2.0 — see LICENSE.
See CONTRIBUTING.md.
Camel-Kit is built on ideas pioneered by the GitHub Spec-Kit team. We are grateful for their open approach to spec-driven development with AI assistants.