Loading video...

Video Failed to Load

Go Home

THIS ANTHROPIC ENGINEER BUILT AN AI AGENT THAT REMEMBERS WHAT IT DOESN’T KNOW. IT MAPS EVERY BLIND SPOT, CHECKS THAT MAP BEFORE ANSWERING, AND REFUSES TO GUESS WHEN IT HITS A KNOWN GAP.

51,346 views • 1 month ago •via X (Twitter)

6 Comments

Mr.Bai 白先生's profile picture
Mr.Bai 白先生1 month ago

Wow, this is seriously futuristic! 😂 It looks like something straight out of the future!

Kshitij Mishra | AI & Tech's profile picture
Kshitij Mishra | AI & Tech1 month ago

wow thats awesome

Hussain Hashim | Building SundayBack's profile picture
Hussain Hashim | Building SundayBack1 month ago

@RoundtableSpace Honestly, this is the kind of thinking I wish I'd applied sooner. Mapping out what you don't know before launching something can save so many headaches down the line.

MASA's profile picture
MASA1 month ago

Active blind spot mapping is the cleanest way to stop hallucinations

Saeed Anwar's profile picture
Saeed Anwar1 month ago

Mapping known unknowns before answering is underrated. Most agents hallucinate instead of refusing, this is the right failure mode.

SHIP SAFE's profile picture
SHIP SAFE1 month ago

Refusing to guess is the right default. Ship Safe v10.0.0 marks unclear security paths as unresolved instead of turning weak evidence into a confident verdict.

Related Videos

i just built a 4-agent software team. everything runs from Telegram and gets managed on a kanban board. a project manager who plans the work, a backend developer, a frontend developer, and a tester. the PM reads a goal, breaks it into linked tasks, and assigns each to the right agent. the thing that makes them a team instead of four strangers is a shared kanban board. every task is a row that survives crashes, and when an agent finishes, it writes a summary of what it built and what the next agent needs to know. the next agent reads that summary before it starts. so the frontend developer never has to guess the API shape, and the tester knows exactly what to verify. the hardest part was not the coordination. it was building an agent that could actually act like a backend engineer. a backend engineer stands up a database, wires auth, manages storage, deploys functions, and keeps all of it consistent while the rest of the team builds on top. an agent doing this from scratch drowns. it burns its context window remembering which tables exist and which endpoint it created three steps ago, and the work degrades fast. so the backend agent needs a backend built for agents, not for humans clicking through a dashboard. that is where InsForge came in. it is an open-source, agent-native backend, and i added it to my backend developer agent as a skill. a skill is a step-by-step guide that teaches the agent how to do a specific kind of work. with InsForge installed, the agent stopped improvising infrastructure and followed a reliable path: create the project, define the database, set up auth, deploy functions. to test the whole team, i had them build a working Google Docs clone, AI features included. the backend agent spun up the full service on its own. database tables, user auth, document handling, and edge functions running real TypeScript, all in one dashboard. the frontend agent read that summary and built the UI on top of it, and the tester closed the loop. the result was a backend an agent could reason about end to end, instead of one it kept getting lost inside. if you are building an AI backend engineer, InsForge is worth a look, it's 100% open-source. InsForge GitHub: (don't forget to star 🌟) the full article on Hermes Kanban: Mission Control for your Agents is quoted below.

Akshay 🚀

123,101 views • 4 months ago