davsclaus commented on code in PR #29904:
URL: https://github.com/apache/camel/pull/29904#discussion_r4578304969


##########
design/cli-short-commands.adoc:
##########
@@ -326,15 +356,23 @@ daemon or a native front does not serve too, and the 
start of the daemon itself.
    readiness pushed over the WebSocket transport.
 . Keep the Java client. At 50-65 ms it answers under the 0.1 s at which a 
response feels instant, so the commands
   already feel native. A native client for the main platforms, with the Java 
client as the fallback, is optional.
-. Tell the agents. Speed alone does not change how an agent uses the CLI, so 
what agents read (the Camel CLI pages,
-  the instructions of the MCP server, the system prompt of the AI panel) says 
that the short commands are cheap to
-  call: look an option up instead of guessing it, asking only for the options 
needed (the `optionsFilter` of
-  `camel_catalog_doc`) as a whole doc page costs context, and validate every 
snippet before answering.
+. Tell the agents, and check for them. Speed alone does not change how an 
agent uses the CLI. So what agents read
+  (the Camel CLI pages, the instructions of the MCP server, the system prompt 
of the AI panel) says that the short
+  commands are cheap to call. Look an option up instead of guessing it, and 
ask only for the options needed (the
+  `optionsFilter` of `camel_catalog_doc`), since a whole doc page costs 
context. Telling is not enough for the checks:
+  told to validate every snippet, the local model wrote more code and 
validated none of it (see the motivation). So
+  the checks run without the agent's choice. The AI panel and `camel ask` mark 
the mistakes in the code of an answer
+  (CAMEL-26960). The MCP server already validates a file before 
`camel_write_file` writes it. An agent that edits
+  files with its own tools needs a hook that runs `camel validate yaml` on 
each edited route file, and the Camel CLI
+  pages show one. That hook runs on every edit, so it is where the daemon 
saves the most.
 . Measure the agents, not only the commands. The local-model benchmark runs in 
the AI panel of the TUI, whose tools
-  run in the process, so it measures the instruction, not the daemon: run it 
with and without the instruction, and
-  compare the pass rate, the calls and the invented options per answer, the 
compactions and the time of the model.
-  The daemon needs a benchmark that drives `camel` through a shell. Make the 
daemon the default only after a release
-  as opt-in, and when that benchmark shows the gain.
+  run in the process, so it measures the instruction and the checks, not the 
daemon. It compares the pass rate, the
+  calls and the invented options per answer, the compactions and the time of 
the model. The first run had the
+  instruction in the first message (see the motivation). The next run puts 
such a line in the system prompt of the
+  AI panel, where it may last past the first question (two jars that differ 
only in that line). A run after that uses

Review Comment:
   Split in b890c2a687a9.
   
   _Claude Code on behalf of davsclaus_



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