pull down to refresh
I was thinking... if I were to design an agent (I may, for me) I'd probably design an agent-making agent.
So you teach the top level thing to pick the right agent for the task at hand, and you start with a single agent that can build agents. Like skills but execute the skill(set) straight into the system prompt without the overhead of souls and identities and what not.
Instead of all the bloat, expose a local knowledge base that every agent can get access to (with RBAC if you plan on doing nasty private thoughts shit) and do proper process isolation. And if staying with go (is actually fun), I may have finally found a great use for go-plugin. Never thought I'd get to say that, lol. An agent is then an isolated plugin (easier to secure than a dll, and let's not speak to a .md file in userspace) and you just expose an interface over gRPC, and done-ish.
🤔 imma burn so many tokens and be obsolete before I'm even done... lol
I was wondering the same thing yesterday: what is the minimal, "boostrappable," agent I can use to build a bespoke swarm.
Then I came to the same conclusion: this is all bound to be obsolete in eight weeks. It's still, likely, a worthwhile study of how these systems operate before LLMs internalize it all.
Also, I overheard someone in the lab (I'd tag them but they didn't know I was involuntarily eavesdropping) describe achieving their desired bespokeness wrapping Codex, adding a few more tool schemas, auxiliary memory, and some multi-agent collaboration primitives. And TIL Codex is open source.
I somehow spent $6 on gemini flash just fucking with it for a few hours that day... madness