Not a technique problem
Some problems are wiring, not thinking. An agent running in the background where you can’t see it. An MCP server that won’t connect. Keys, quotas, a billing page that swears everything is fine. The library names thinking patterns; this problem lives in how the tool is hooked up.
The first real visitor to this site typed: “agent is doing something and its running in the background and i dont know whats happening.” That’s a complete problem statement — and we routed it to a thinking technique. This page is the fix.
Step one: let your agent try. Wiring is usually agent-fixable. Connect your AI agent to this site’s MCP and describe the problem to it — it gets a debugging scaffold built from the library’s own techniques: map the dependency chain and work backward, test each link, claim nothing fixed without a passing check. It narrates as it goes, so you learn the wiring too.
Step two: if it’s still stuck — or the fix lives behind a billing page or account dashboard your agent can’t touch — you’ll talk to Tal Onn. He built this site and has wired agents, MCP servers, and observability setups for years. Fifteen minutes, on video. Bring the actual screen — we’ll look at it together.
Why free? Early days — every setup problem we see teaches us what to build next.
If yours turns out to be technique-shaped after all, you leave with the right page and the remaining minutes.
Booking asks three things: your name, an email, and what the meeting is about — one sentence there is plenty.
If it is a thinking problem
“It keeps making things up,” “it lost the thread,” “it agrees with everything” — that’s the library’s territory. Describe yours on the front page and get the named technique.
If the library is missing something
Suggest it on the board — and upvote it if someone already did.