Fun agent I've been playing with - the idea is it only has access to a bash tool, and it's directed to create CLIs for use (with additional direction to make the CLIs composable, follow the Unix philosophy, etc).
It persists these CLIs and knowledge about them get injected into the system prompt dynamically, so each time it runs it gets access to a larger and larger toolset of composable CLIs.
One interesting dynamic that's emerged from this is I've started using these CLIs myself since they're the same interface for the agent or for me, and it's turned into kind of non-chat channel to interact with the agent.
One example - I'll add tasks throughout the day myself using the `tasks` CLI it made, then when I interact with the agent it'll run `tasks list` and see everything I've added, or use it to prioritize/update things for me. Later on when I run `tasks list` myself I see all the updates/priorities it set.
0 comments
—
Show HN: CLIs Are All You Need for Agents · HackerTrans
It persists these CLIs and knowledge about them get injected into the system prompt dynamically, so each time it runs it gets access to a larger and larger toolset of composable CLIs.
One interesting dynamic that's emerged from this is I've started using these CLIs myself since they're the same interface for the agent or for me, and it's turned into kind of non-chat channel to interact with the agent.
One example - I'll add tasks throughout the day myself using the `tasks` CLI it made, then when I interact with the agent it'll run `tasks list` and see everything I've added, or use it to prioritize/update things for me. Later on when I run `tasks list` myself I see all the updates/priorities it set.