Agents Aren't Coworkers, Embed Them in Your Software
1–10 of 24 posts
Re: Agents Aren't Coworkers, Embed Them in Your Software
#2not yet coworkers*
Re: Agents Aren't Coworkers, Embed Them in Your Software
#3> Give an agent the right interfaces and it becomes less conversational and more ambient. It no longer needs to constantly ask, explain, summarize, and negotiate. It can stay in the background, react to changes, and make steady progress with less supervision and less noise. That is closer to Weiser’s vision: calm technology, but for machines.
I tend to agree quite a bit.
I created a ambient background agent for my projects that does just that.
It is there, in the background, constantly analysing my code and opening PRs to make it better.
The hard part is finding a definition of "better" and for now it is whatever makes the longer and type checker happy.
But overall it is a pleasure to use.
Re: Agents Aren't Coworkers, Embed Them in Your Software
#4> Agentic management software is all the hype today: What started with Moltbot and OpenClaw now has a lot of competition: ZeroClaw, Hermes, AutoGPT etc.
Moltbot is OpenClaw, AutoGPT was born significantly before. I just couldn’t read after the first paragraph, I’ve lost the trust entirely, whatever/whoever wrote it.
Re: Agents Aren't Coworkers, Embed Them in Your Software
#5> Give an agent the right interfaces and it becomes less conversational and more ambient. It no longer needs to constantly ask, explain, summarize, and negotiate. It can stay in the background, react to changes, and make steady progress with less supervision and less noise. That is closer to Weiser’s vision: calm technology, but for machines. I tend to agree quite a bit. I created a ambient background agent for my pr…
Just take a look at the pull requests / issues opened of a repository that’s popular with LLM agents, to understand how well that works.
If there’s one take away it’s that these agents need more, not less, oversight. I don’t agree at all with the “just remove a few tools and you can remove the human from the loop” approach. It just reduces the blast radius in case the agent gets it wrong, not the fact that it gets it wrong.
Re: Agents Aren't Coworkers, Embed Them in Your Software
#6> Agentic management software is all the hype today: What started with Moltbot and OpenClaw now has a lot of competition: ZeroClaw, Hermes, AutoGPT etc. Moltbot is OpenClaw, AutoGPT was born significantly before. I just couldn’t read after the first paragraph, I’ve lost the trust entirely, whatever/whoever wrote it.
It’s marketing. They’re selling some change management solution, so obviously they advocate for showing AI agents only changes, rather than the full context.
Doesn’t mean it’s a good idea, though.
Re: Agents Aren't Coworkers, Embed Them in Your Software
#7> Agentic management software is all the hype today: What started with Moltbot and OpenClaw now has a lot of competition: ZeroClaw, Hermes, AutoGPT etc. Moltbot is OpenClaw, AutoGPT was born significantly before. I just couldn’t read after the first paragraph, I’ve lost the trust entirely, whatever/whoever wrote it.
Hermes agent dates back to at least September last year too, pre-dating Moltbot/OpenClow by a couple of months https://github.com/NousResearch/hermes-agent/commit/17608c11...
Re: Agents Aren't Coworkers, Embed Them in Your Software
#8I'd pay more for deterministic, explainable, and fast software without agents. The value of computers is that they do tasks repeatably, reliably, and at blinding speed.
This stuff is negative value.
Re: Agents Aren't Coworkers, Embed Them in Your Software
#9> Give an agent the right interfaces and it becomes less conversational and more ambient. It no longer needs to constantly ask, explain, summarize, and negotiate. It can stay in the background, react to changes, and make steady progress with less supervision and less noise. That is closer to Weiser’s vision: calm technology, but for machines. I tend to agree quite a bit. I created a ambient background agent for my pr…
Just take a look at the pull requests / issues opened of a repository that’s popular with LLM agents, to understand how well that works. If there’s one take away it’s that these agents need more, not less, oversight. I don’t agree at all with the “just remove a few tools and you can remove the human from the loop” approach. It just reduces the blast radius in case the agent gets it wrong, not the fact that it gets it…
Yeah, but my projects are personal and not popular.
I crafted the AI loop to do exactly what I would be doing by manually.
Out of 10 PRs, 6 to 7 gets merged. The other simply get closed.
Re: Agents Aren't Coworkers, Embed Them in Your Software
#10[dead]