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 71-75 of 236 articles.

Engineering

MCP Spotlight: Fetch MCP Server — The Anthropic Reference for Safe HTML-to-Markdown Web Fetching With URL Allow-Lists and the Read-Only Default

Jul 5, 2026Engineering

MCP Spotlight: Fetch MCP Server — The Anthropic Reference for Safe HTML-to-Markdown Web Fetching With URL Allow-Lists and the Read-Only Default

The official Fetch MCP Server by Anthropic — one tool (fetch), read-only by design, HTML→Markdown conversion with raw/JSON modes. MIT-licensed, available as NPX package or Docker image. The read-only web access default for AI agents in 2026.

Product

Facio's Cost Guardrails: How AI Agents Stay Inside the Budget Without Surprising the Finance Team

Jul 5, 2026Product

Facio's Cost Guardrails: How AI Agents Stay Inside the Budget Without Surprising the Finance Team

AI agents burn money quietly. A misconfigured agent makes 10x the necessary API calls. A runaway agent loops on a problem for hours. A clever agent uses the most expensive model for every task because it doesn't know cheaper ones work. By the end of the month, the finance team is asking questions that the engineering team can't answer. Facio's cost guardrails give teams the structural discipline to predict, track, and cap AI agent spend before the invoice arrives.

Human-in-the-loop

The HITL Boundary Problem: Where Exactly Does the Agent Stop and the Human Start?

The HITL Boundary Problem: Where Exactly Does the Agent Stop and the Human Start?

Most HITL posts assume the boundary between agent and human is obvious. It's not. The boundary is contested, contextual, and constantly shifting. The agent does some preparation, the human does some finalization, the agent does some cleanup. Where exactly does oversight end and execution begin? The boundary problem is the deepest architectural challenge in HITL — and the one most teams don't even realize they're facing.

Engineering

MCP Spotlight: GitHub MCP Server — The Official, OAuth-2.0-Enabled Bridge to Issues, PRs, Code, Actions, and the Entire Software-Engineering Workflow

Jul 4, 2026Engineering

MCP Spotlight: GitHub MCP Server — The Official, OAuth-2.0-Enabled Bridge to Issues, PRs, Code, Actions, and the Entire Software-Engineering Workflow

The official GitHub MCP Server by GitHub — ~90+ tools covering the full software-engineering lifecycle (issues, PRs, code, Actions, discussions, search, security). OAuth 2.0 + GitHub App + Personal Access Token support, MIT-licensed. The software-engineering default for AI agents in 2026.

Product

Facio's Task Dispatch: How Hundreds of AI Agents Get the Right Work at the Right Time

Jul 4, 2026Product

Facio's Task Dispatch: How Hundreds of AI Agents Get the Right Work at the Right Time

A single AI agent is a workflow. A fleet of AI agents is a system. The fleet needs dispatch — a way to route incoming work to the right agent at the right time, balance load across agents, prioritize critical work over routine work, and ensure no agent gets overwhelmed. Naive fleets have no dispatch: every agent polls for work, work piles up at the busiest times, and the team ends up with a different problem than the one they were trying to solve. Facio's task dispatch is the structural discipline that turns agent fleets into systems.