CLI today

CLI

Agent Intros' official command-line interface for working your network from the terminal.

AgentIntros is CLI-first today with local API, SDK, MCP, and webhook scaffolds for integration development. Graph-backed production behavior is still separate from these local routes.

Overview

Agent Intros' official command-line interface for working your network from the terminal. This page explains the shipped intros command line tool in the AgentIntros model, with the trust boundary kept explicit: agents can discover, draft, and prepare work, while people approve relationship-bearing actions.

When to use it

Use it when an agent needs to reason about the shipped intros command line tool without losing the human relationship context.
Use it when the workflow should preserve double opt-in, review, and auditability by default.
Use it when you want network work to be queryable and repeatable instead of buried in ad hoc notes.

Canonical flow

The CLI commands below are available today through the published `intros` package.

CLIbash

npm install -g intros
intros init
intros new "Investor Intro Agent" \
  --role "Warm intro router" \
  --goal "Find trusted paths to fintech investors"
intros list
intros show investor-intro-agent
intros request create \
  --subject "Founder raising seed" \
  --target "fintech investors" \
  --api-url http://localhost:3000

Reference

Command	Purpose
intros init	Create intros.config.json.
intros new	Create a local agent intro brief.
intros list	List saved intro briefs.
intros show	Print a saved intro brief.
intros request create	Create an API-backed intro request against the local scaffold.
intros request list	List API-backed intro requests.
intros request show	Print one API-backed intro request.
intros webhook create	Register a webhook endpoint.
intros webhook list	List webhook endpoints.
intros webhook sign	Sign a webhook payload.
intros webhook verify	Verify a webhook payload signature.
intros mcp-config	Print MCP server configuration for intros-mcp.
intros version	Print the installed CLI version.

Operational guidance

Require human approval before any intro is sent or any connector is represented as having opted in.
Use client-supplied idempotency keys for local scaffold write calls and keep the same contract when graph-backed persistence is added.
Keep shared context minimal, specific, and relevant to the requested introduction.

Copy for Cursor / Claude

AgentIntros docs note for CLI: treat CLI, local API routes, SDK helpers, MCP tools, and webhook signing as local developer scaffolds. Realtime, source sync, hosted approvals, graph-backed persistence, and follow-up automation remain planned. Never bypass approval or double opt-in when building workflows around introductions.

CLI