Thread

1. chris_marino · 1789664638 · focus · HN ↗

   We found after deploying many enterprise agents that letting the model choose tools at run time can cause problems. The agent holds the credential and sometimes chooses the wrong tool. Using the same tool every time prevents this.

   1. tikimcfee · 1789666626 · focus · HN ↗

      Absolutely in love. I'll be testing this after the daily grind.

      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?

      1. chris_marino · 1789669657 · focus · HN ↗

         The command structure is provider/topic/command. Taken literally from the oclif framework, with the provider simply being a topic namespace. Haven't needed to pipe anything since in our deployments, the agent makes a call to the gateway via a command API so a pipe wouldn't be possible between commands

Unofficial Hacker News client; not affiliated with Y Combinator.