cli.calls_arguments
A jadpo calls command names an action it doesn't have, a call the log doesn't hold, or an answer without its operation.
Area 14, Tools; not declinable; the next step is usually the agent's.
Why Jadpo refuses it
jadpo calls reads the log of provider calls jadpo dev made, shows one by its id, or scripts the next answer of one operation it fakes. Each needs to know which call or operation, and it never picks one for you.
What it looks like
Nothing has run jadpo dev yet, so the log is empty, and the command asks for a call:
jadpo calls show call_31 error There is no call call_31
- reason
- The log keeps the last 500 calls
jadpo devmade, and holds none yet. - next
- Run
jadpo callsto see their ids (agent) - rule
- cli.
calls_ arguments - help
- https://jadpo.
dev/docs/errors/cli. calls_ arguments
(agent) at the end of the next: line means your coding agent can make the fix itself.
An action it doesn't have is refused with the ones it does:
jadpo calls replay error replay isn't something jadpo calls does
- reason
jadpo callslists calls, shows one or scripts an answer:list,showorscript.- next
- Run
jadpo callsto list the calls (agent) - rule
- cli.
calls_ arguments - help
- https://jadpo.
dev/docs/errors/cli. calls_ arguments
How to fix it
If you want to see the calls, list them first, then show one by the id the list gives:
jadpo callsjadpo calls show call_31
The list is empty until jadpo dev has made a call.
Related
Markdown for agents: /docs/errors/cli.calls_arguments.md.Built from Jadpo main at aee2e8f.