标签：#ha

In November 2025, an engineering team deployed a market research pipeline using four LangChain agents. Due to a logic failure, the "Analyzer" and "Verifier" agents got stuck in a recursive ping-pong loop. Because every individual API call was perfectly valid, the system appeared healthy on their dashboards. 11 days later, they discovered a $47,000 API bill . This is the hidden cost of building autonomous AI: infinite hallucination loops . When an agent encounters an error or fails to reach a termination condition, it will ruthlessly retry, burning through tokens in milliseconds. Why Built-in Controls Fail If you build with LangChain or LangGraph, you are likely relying on two things for cost control: max_iterations : An application-layer limit. LangSmith : An observability dashboard. The problem with max_iterations is that it requires every developer to perfectly hardcode it into every agent. Furthermore, iterations do not equal cost, a single iteration with massive context bloat can still cost a fortune. The problem with LangSmith (and all observability tools) is that they act as a witness, not a circuit breaker. By the time your dashboard alerts you that a spike occurred, the money is already gone. To safely deploy agents to production, you need Agent Runtime Governance , a network-layer firewall that physically drops the HTTP request the exact millisecond a budget hits zero. Enter Loopers . What is Loopers? Loopers is an open-source, baremetal reverse proxy for AI agents. It sits on your critical path between LangChain and your LLM provider (OpenAI, Anthropic, etc.). It uses atomic Redis Lua scripts to reserve budget before the request is sent to the provider. If the agent exceeds its budget, Loopers fails closed and instantly severs the connection, guaranteeing zero budget leakage. Here is how to implement Loopers into your LangChain workflow in less than 5 minutes. Step 1: Spin up the Loopers Firewall Loopers is incredibly lightweight (~40MB RAM) and runs via D

At first, approvals sound simple. Show a button. Let someone click approve. Continue the workflow. But real approvals are much harder than that. Nod has to answer important questions: Who requested this approval? Who approved or rejected it? Was the person allowed to decide? Did the approval expire? Was the callback delivered? Can we prove what happened later? That is why Nod stores approvals as real state, not temporary UI. Each approval has a status: pending approved rejected expired canceled Only one final decision can win. If two people click at the same time, Nod must safely accept the first valid decision and reject stale attempts. Slack also needs careful handling. Nod verifies Slack signatures, checks the approval and channel, and stores an actor snapshot for the audit log. After a decision, Slack messages can be updated so old buttons are no longer useful. Webhooks also need trust. Nod signs every callback so customer apps can verify it before continuing. const event = nod . webhooks . verify ({ rawBody , headers : request . headers , secret : process . env . NOD_WEBHOOK_SECRET ! , }); We learned that approvals are not just a product feature. They are a security system. A good approval layer needs: Authorization Idempotency Expiration Webhook signing Retry logic Audit logs That is what Nod is built around.