Facio Blog

Practical notes on human-reviewed AI agents.

Payload-powered product notes, security writing, HITL patterns, and operational guidance from the Facio runtime: long sessions, Placet approvals, audit trails, memory, providers, channels, tools, and Docker-first operations.

Showing 31-35 of 236 articles.

Human-in-the-loop

HITL and the Latency Tax: Why Every Second of Review Waits Has a Cost the System Doesn't Acknowledge

Jul 17, 2026Human-in-the-loop

HITL and the Latency Tax: Why Every Second of Review Waits Has a Cost the System Doesn't Acknowledge

Every HITL review waits. The customer's request sits in the queue. The latency is real — the customer perceives it, the SLA measures it, the business pays for it. But most HITL systems treat the latency as external to the HITL design. The latency is internal. The latency has a cost. The cost is a tax on every decision the reviewer makes. Here is why the latency tax is the most underrated cost in HITL.

Engineering

MCP Spotlight: Sentry MCP Server — The Official Error-Tracking Bridge With Release-Aware Stack Traces, Agentjacking Defense, and the Production-Debugging Default for Agents

Jul 16, 2026Engineering

MCP Spotlight: Sentry MCP Server — The Official Error-Tracking Bridge With Release-Aware Stack Traces, Agentjacking Defense, and the Production-Debugging Default for Agents

The official Sentry MCP Server by Sentry — ~15 focused tools covering issues, events, stack traces, releases, breadcrumbs, performance traces, alerts. Release-aware debugging (know which release introduced which bug), stack-trace summarization, agentjacking defense. The production-error-tracking default for AI agents in 2026.

Product

Facio's Per-Tool Credentials: How AI Agents Authenticate Without Becoming a Credential Vault

Jul 16, 2026Product

Facio's Per-Tool Credentials: How AI Agents Authenticate Without Becoming a Credential Vault

An AI agent that calls a hundred APIs needs credentials for each one. The naive approach — give the agent one master credential with broad access — is a security catastrophe waiting to happen. The slightly less naive approach — let the agent store credentials in environment variables or config files — is also bad. The discipline Facio applies is per-tool credentials: each tool has its own narrowly-scoped credential, never seen by the model, replaced on rotation, and audited per call. The agent gets access; the security team gets controls.

Security

The Insider Threat Inside the AI Agent: Why Behavioral Analytics Is the Only Way to Catch the 2026-Class of Agent Compromise

Jul 16, 2026Security

The Insider Threat Inside the AI Agent: Why Behavioral Analytics Is the Only Way to Catch the 2026-Class of Agent Compromise

Exabeam's April 2026 Agent Behavior Analytics launch named the threat: the rogue AI agent operating with insider access. Every individual action is authorized; the maliciousness is in the pattern. Behavioral analytics is the only detection method that operates at the pattern level.

Human-in-the-loop

HITL and the Paradox of Choice: Why Fewer Options Make Reviewers More Accurate

Jul 16, 2026Human-in-the-loop

HITL and the Paradox of Choice: Why Fewer Options Make Reviewers More Accurate

Every HITL interface gives the reviewer four options: approve, reject, modify, escalate. Add "ask for context" and "defer" and "flag for policy review" and "request rollback preview" — and the reviewer's accuracy drops. The paradox of choice in HITL: the more options the reviewer has, the worse the decisions get. Less is more. Here is why, and how to design the choice architecture that maximizes reviewer accuracy.