YEA

Appearance

Use it from Claude Code ​

The bridge exposes YEA services as an MCP server, so every MCP client can use them now. Tool results are Lens.

Claude Code plugin (bundles the MCP server and a skill that teaches consent etiquette):

text
/plugin marketplace add yea-protocol/yea
/plugin install yea@yea

Any tool, one command. This creates an agent key and registers the bridge (plus a short agent-instructions block) with every AI tool it finds:

sh
npx @yea-protocol/cli install                    # or --target claude-code,cursor,codex,gemini,vscode,windsurf,claude-desktop
npx @yea-protocol/cli add https://shop.example/yea   # add services; the bridge picks them up on restart
npx @yea-protocol/cli doctor                     # check keys, grants, services, registration

It never auto-approves yea_commit or yea_undo in your tool. When a commit needs consent, the bridge asks you: in the client's UI via MCP elicitation, or through yea approve <code>, which shows the exact action and needs an interactive terminal. The model can't approve for itself.

Keep the principal key away from the agent ​

Your principal key signs your policy and your approvals, so everything rests on it. yea install therefore creates only the agent's key. Create the principal on another device or OS user and send the agent a grant:

sh
# on your phone/laptop/other user (holds the principal key)
yea init && yea grant --to <agent key> --svc shop.example --risk low --per 25USD --spend 100USD --exp 30d
# on the agent's machine
yea grant-import <token>

To try things quickly on one machine, use yea install --with-principal. Be aware that an agent with shell access (Claude Code has it) could then read the key. Pair --per with --spend: a per-action cap alone can be dodged by splitting a purchase, and --spend bounds the total.

What the model gets ​

Four generic tools (yea_ask, yea_intent, yea_commit, yea_undo) and each service's brief. It needs no YEA documentation: in a real session, Claude Sonnet 5 read Lens cold, moved a meeting within policy, stopped at a purchase over its limit, and asked the human to approve it.

Try it without running anything ​

The hosted demo runs the example calendar and shop for you, with a private copy per agent key. To wrap an API you already have, see Wrap any REST API.