Claus Ibsen created CAMEL-26787:
-----------------------------------
Summary: camel-jbang - let there be chaos: the playbook as an MCP
prompt, and camel cmd chaos-explore with the AI of camel ask
Key: CAMEL-26787
URL: https://issues.apache.org/jira/browse/CAMEL-26787
Project: Camel
Issue Type: Improvement
Components: camel-jbang
Reporter: Claus Ibsen
Assignee: Claus Ibsen
Fix For: 4.24.0
Step 6 of CAMEL-26760 ("let there be chaos"): the playbook, so an AI explores
chaos by itself for a time budget and reports at the end (one consent: the
exploration; the AI steers as autonomously as it can).
* The playbook, one text for both: the MCP prompt {{camel_chaos_explore}}
(budget, focus, the integration) and {{camel ask}}. It tells the model the
loop: read the report and the suggestions, run one experiment per call
({{chaos_experiment}}, CAMEL-26786) with a hypothesis, a short until= and an
expectation that decides it, read the verdict, go on while the time left
allows, finish, and report: findings (route, what broke, evidence, a hint; it
never changes the routes) and what was not tried.
* {{camel cmd chaos-explore [name] --budget=10m --focus=...}}: starts the
exploration itself (so the budget is the user's), runs the AI of camel ask with
the playbook, finishes the exploration when the AI is done, and prints the
journal and the AI's report.
First release: one agent and one integration. Routes fed over HTTP or files are
not fed by an experiment yet (send to a route id reaches its from endpoint only
for direct, seda and stubbed brokers). An eval against a local model follows.
_Claude Code on behalf of Claus Ibsen_
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)