12 points chris_marino 1 hour ago 5 comments
The repo has more details. https://github.com/agent-cli-framework/aclif
chris_marino 1 hour ago | parent
tikimcfee 28 minutes ago | parent
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?
chris_marino 12 minutes ago | parent
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.
charlie_martin9 21 minutes ago | parent
chris_marino 17 minutes ago | parent
https://github.com/agent-cli-framework/aclif/blob/main/docs/...
https://github.com/agent-cli-framework/aclif/blob/main/.clau...