intendant-cli

Operates a running Intendant daemon via the ctl CLI for sessions, displays, computer-use, and federated peers.

14|Updated Mar 2, 2026
One-click install
npx skills add https://github.com/intendant-dev/Intendant --skill intendant-cli-intendant-dev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: intendant-cli
Source: https://github.com/intendant-dev/Intendant/tree/main/skills/intendant-cli
Command: npx skills add https://github.com/intendant-dev/Intendant --skill intendant-cli-intendant-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about intendant-cli

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I control an Intendant daemon from the command line?▼

Use the intendant ctl subcommands, starting with ctl --help, ctl status --json, and ctl whoami. Supervised sessions have $INTENDANT and INTENDANT_MCP_URL injected, so run "$INTENDANT" ctl ... to reach the exact controller binary.

How do I take a screenshot or click on a remote peer machine?▼

Use the global --peer flag to route any ctl subcommand to a federated peer over mTLS, for example ctl --peer dell display screenshot or ctl --peer dell cu actions. The peer's IAM profile decides whether screenshots, element reads, or input actions are granted.

Can I use cliclick, osascript, or xdotool for desktop input instead?▼

No. Desktop input must go through ctl cu actions or the MCP execute_cu_actions tool so actions run under the owner's approval settings. Sideloaded input tools bypass those approval gates and are explicitly disallowed.

Why did my screenshot or computer-use action fail even with a display grant?▼

An Intendant display grant does not imply OS-level permissions. Run ctl display status to check per-layer readiness — screen recording, accessibility, display availability, and input backend — and relay the listed fix steps to the user.

What is the difference between ctl ask and ctl ask --park?▼

ctl ask blocks and prints the user's answer to stdout, suited for destructive or hard-to-reverse choices. --park files the question as a durable agenda item and returns immediately, delivering the answer back to the session later.

What happens if the Intendant CLI cannot be resolved?▼

If $INTENDANT, PATH, and the cli-path descriptor under the Intendant state root all resolve nothing, Intendant is not installed on the machine and the skill does not apply. If the CLI resolves but the daemon does not answer, the daemon is down — a different condition to report.