What problem does it solve? Agents working on an Intendant-managed machine need a single, approval-gated way to control sessions, capture screenshots, drive the desktop, ask the user questions, and reach federated peer machines without loading broad MCP tool schemas into context. ## Core Features & Use Cases - Daemon control via intendant ctl: status, whoami, session notes, approvals, agenda items, memory claims, and managed-context rewind, all discoverable through subcommand help. - Desktop and browser operation: display screenshots, virtual display creation, computer-use action batches with observation modes, UI element tree reads, and CDP-backed browser workspaces — always routed through Intendant so the owner's approval settings apply. - User interaction and federation: blocking or parked structured questions (ctl ask), fire-and-forget notifications, shared display surfacing, and --peer routing to message, delegate tasks to, or directly drive another machine's agent and screen. - Use Case: An agent needs the user to pick between two landing page designs — it runs ctl ask with --preview-html options, blocks for the answer, then screenshots the result and posts a before/after session note. ## Quick Start Ask the agent to run intendant ctl status and then take a screenshot of the current display to confirm the daemon is reachable.