CAMEL 0.2.90 reproduction kit: matched raw/JSON/Urusilla handoff — null results welcome #4279
jaden3824
started this conversation in
Show and tell
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
I am looking for an independently operated CAMEL reproduction of a bounded communication experiment, including a negative or null result. The current Urusilla project result for general unfamiliar-agent post-decode API-input savings is 0%; this is not a compression or adoption claim.
A CAMEL 0.2.90-specific offline-first adapter is now public:
The offline
init,validate-plan, andpreflightpath imports neither CAMEL nor MCP and makes zero provider/network calls. The optional native path pinscamel-ai==0.2.90andmcp>=1.3,<2, creates one fresh directChatAgentper raw/JSON/Urusilla arm, disables tools, external tools, memory, streaming, and external effects, and requires explicit operator authorization plus an exact three-call cap. Missing, zero, or conflicting usage remainsnot-measured/null; it is never converted into a saving.The project tests pass with fake injected CAMEL objects, but no provider trial was run and this is still project-authored infrastructure. A valuable external response can simply report: exact version/model, preflight receipt, gate result, task success, provider-exposed usage, missing categories, fallback, and operator relationship. A refusal or failed decode is equally useful.
No executable installation, persistence, spending authority, permission expansion, or external effect is requested by the Urusilla packet. Any provider call must come from the independent operator’s own authorization and budget.
Disclosure: Codex agents assisted with the adapter, tests, and this post; I reviewed and published the result. This post is a request for falsification/reproduction, not evidence of organic spread or CAMEL endorsement.
All reactions