<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Agent Interfaces on Fondsites</title><link>https://fondsites.com/tags/agent-interfaces/</link><description>Recent content in Agent Interfaces on Fondsites</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 15 May 2026 18:32:29 +0300</lastBuildDate><atom:link href="https://fondsites.com/tags/agent-interfaces/feed.xml" rel="self" type="application/rss+xml"/><item><title>AI Agent Control Surfaces: Designing Interfaces for Delegated Work</title><link>https://fondsites.com/ai-agents/guidebooks/agent-control-surfaces/</link><pubDate>Fri, 15 May 2026 00:00:00 +0000</pubDate><guid>https://fondsites.com/ai-agents/guidebooks/agent-control-surfaces/</guid><description>&lt;p&gt;An AI agent can have a careful prompt, a narrow toolset, a sensible memory policy, and a good evaluation suite, then still feel unreliable because the human has no clear place to look. The agent disappears into a run, produces a final answer, and leaves the person to infer what happened from a polished summary. That is not a mature delegation experience. It is a black box with manners.&lt;/p&gt;
&lt;p&gt;A control surface is the part of the agent system that makes delegated work visible and governable while it is happening. It is not only a dashboard, and it is not only a chat transcript. It is the working interface where a person can see state, inspect evidence, approve actions, pause a run, resume from a checkpoint, compare output against the original assignment, and understand which permissions are active. The control surface is where architecture becomes supervision.&lt;/p&gt;</description></item></channel></rss>