登録して招待リンクを共有すると、動画再生報酬と紹介報酬を獲得できます。

Magnus Müller
@mamagnus00
Founder of @Browser_use (W25)
参加 August 2014
356 フォロー中    11.1K ファン
Open source is here one of the biggest advantages. If you don't have to hide your harness, your user-facing agent can have full access to its own codebase, and if there's a bug, it can just, in real time, fix it. But if you are closed-source, then you need to hide your implementation, and the agent has no context and cannot fix it on the fly.
もっと見る
HOW TO FIX YOUR AI AGENTS (it's called "self-healing agents") If you've run AI agents, you know they BREAK constantly. The FIX is something called a "self healing" agent! A normal agent hits a dead end and just stops, leaving you a half finished mess and that's why output sometimes isn't ideal. BUT, a self-healing one hits the same wall and thinks "okay, that didn't work, let me try another way" HOW TO BUILD SELF-HEALING AGENTS (4 steps): 1. Make it check its own work. After each step, the agent asks "is this what I expected?" instead of assuming it worked and moving ahead. 2. Have it name what broke. Not just "it failed," but which kind: the tool timed out, returned an error, came back empty, or gave a wrong answer. Wrap your tool calls so the error gets passed back to the agent, because it can only fix a failure it can actually see. 3. Match the fix to the failure. Glitch, retry it. Tool down, switch to a backup. Keeps failing, break the task smaller. Anything risky like money or deleting data, stop and ask you. 4. Make it log every fix. It writes down what broke and what worked, so it stops repeating the same mistake in a session, and you get a list of what to fix at the root. That's it. Now, you've got agents that fix themselves.
もっと見る