Simple discovery of the provider's default schemas is possible without any credentials (since they are built into the binary). If you want it to fetch customizations of your specific instance, give it credentials to your org. The repo has more details. https://github.com/agent-cli-framework/aclif |
I've had nothing but success with converting daily work into "notes" that then translate into runnable, deterministic application CLIs to completely sidestep "what do I need to say to you to make you do the thing??"
I'm interested in how this spreads across enterprise flows, because the issue is always discovery and usability.
How deep do you usually go with CLI composition and layering? Do you tend to find a flat list of commands and sub command help works most? Have you experimented with connecting CLIs Linux-pipe-style as if it was a dynamic application in the OS?
It is used internally for what we call 'compiled workflow agents' where no inference is necessary. An agent composer determines the exact command at design time. That is part of a discovery loop that can introspect the service to construct the command.
Huh? It shouldn't. Am I misunderstanding, or is this referencing poor practices?
"Using the same tool every time prevents this"
What does this mean? I looked at the project, im not sure what this means.
https://github.com/agent-cli-framework/aclif/blob/main/docs/...
https://github.com/agent-cli-framework/aclif/blob/main/.clau...
What's not clear about that?
Who are we talking about? What's their role? (What agent? What is the job to be done?)
What is the status quo? What's the problem with the status quo? What else has been tried? What's the consequence of not solving the problem? What more important problem do you need to work on that you're blocked because of this problem? What's the ideal solution? What's the current offer? Why would someone say no to any given solution? How have you addressed those problems?