extendo-cli
v0.0.1
Published
CLI for interacting with Extendo backends
Readme
Extendo CLI
Human-in-the-loop decisions for AI agents.
Extendo lets your agents ask humans for structured decisions — approvals, choices, reviews, prioritization — delivered as rich UI via mobile push notifications. The human responds on their phone; the agent gets structured JSON back and continues.
# Agent asks for deploy approval → user sees a yes/no card on their phone
npx extendo-cli artifact create ops deploy \
--type yes_no --title "Deploy to prod?" \
--prompt "All 847 tests pass. Ship it?" \
--wait --json{ "payload": { "decision": true } }No Slack threads. No email. No "reply YES to confirm." Purpose-built UI for each decision type.
Quickstart
1. Get the Extendo app
Extendo is an iOS app. Install it on your iPhone or iPad via TestFlight (invite link coming soon).
2. Connect to the public backend
Visit public.extendo.sh to get an API token. Scan the QR code with the Extendo app on your phone to add the backend.
npx extendo-cli auth add public https://public.extendo.sh <your-token>Note: The public backend is the fastest way to try Extendo, but for production use you'll get a better experience hosting your own infrastructure — tighter integration with your agents, lower latency, and full control. See extendo-backends for self-hosting on Cloudflare Workers or inside a Tailnet.
3. Add the agent skill (optional)
If you use Claude Code, install the skill so Claude knows how to use Extendo automatically:
npx skills add github:extendo-cliThis works with any agent framework that can run shell commands — the skill is just documentation, and npx extendo is the CLI.
What can it do?
Messaging
Send messages to a human and wait for replies:
npx extendo-cli new project "Starting the auth refactor. I'll check in when I hit a decision point."
npx extendo-cli send project my-thread "Found 3 approaches. Creating a decision artifact."
npx extendo-cli wait project my-thread --timeout 300Structured Decisions
Create artifacts that render as purpose-built UI on the user's device. The agent blocks (or polls) until the user submits.
| Type | What the user sees | Use case |
|---|---|---|
| yes_no | Approve / Reject buttons | Deploy gates, destructive action confirmation |
| multiple_choice | Radio buttons or checkboxes | Model selection, strategy choice |
| checklist | Per-item approve/reject switches | Expense review, PR file-by-file approval |
| ranking | Drag-to-reorder list | Sprint prioritization, migration ordering |
| categorize | Kanban board (iPad) / collapsible sections (iPhone) | Bug triage, task bucketing |
| document_review | Per-paragraph annotation | RFC review, contract review |
| dag | Interactive directed graph | Architecture diagrams, dependency visualization |
| progress_grid | Colored status matrix | Sprint trackers, migration dashboards |
Decision Gates
Block an agent workflow until a human decides:
# Create a conversation thread for context
THREAD=$(npx extendo-cli new ops "Requesting deploy approval for v2.3.1" --json | jq -r .endpoint.name)
# Create a linked yes/no gate — blocks until the user taps Approve or Reject
RESULT=$(npx extendo-cli artifact create ops deploy-v2 \
--type yes_no \
--title "Deploy v2.3.1 to production?" \
--prompt "CI green. 847 tests pass. No regressions." \
--conversation "ops:$THREAD" \
--wait --json)
if [ "$(echo "$RESULT" | jq -r '.payload.decision')" = "true" ]; then
echo "Deploying..."
else
echo "Aborted."
fiCLI Reference
Messaging
npx extendo-cli new <category> "message" # Create a new thread
npx extendo-cli send <category> <name> "message" # Send to existing thread
npx extendo-cli read <category> <name> # Read messages
npx extendo-cli wait <category> <name> --timeout 300 # Block until reply
npx extendo-cli threads # List all threads
npx extendo-cli thread update <cat> <name> --title "..." --note "..."Both send and new accept --context <text> or --context-file <path> to inject system context.
Artifacts
npx extendo-cli artifact create <cat> <name> --type <type> --title <title> [options]
npx extendo-cli artifact get <cat> <name> [--wait] [--timeout <s>] [--json]
npx extendo-cli artifact update <cat> <name> --payload <json> | --payload-file <path>
npx extendo-cli artifact list [--status <status>] [--json]
npx extendo-cli artifact delete <cat> <name>Auth
npx extendo-cli auth add <name> <url> <token> # Add/update a backend
npx extendo-cli auth list # Show configured backends
npx extendo-cli auth default <name> # Set default backend
npx extendo-cli auth remove <name> # Remove a backendGlobal Flags
All commands accept: --json, -b <name> / --backend <name>, --url <url>, --token <token>
Documentation
- SKILL.md — Full skill reference (loaded automatically by Claude Code)
- references/artifact-reference.md — Complete artifact type guide with result shapes and jq snippets
- extendo-gate.md — Decision gate patterns for agent workflows
Architecture
Extendo is three components:
| Component | What it does | Repo | |---|---|---| | extendo-cli | CLI + agent skill. Sends messages and creates artifacts via HTTP API. | You're here | | extendo-backends | Cloudflare Workers that store threads, artifacts, and send push notifications. | extendo-backends | | Extendo iOS app | iPhone/iPad app that renders artifacts as native UI and sends responses back. | Private (TestFlight) |
Agent (CLI) ──HTTP──▶ Backend (CF Worker) ──APNs──▶ iOS App
▲ │
└────── HTTP response ────┘License
MIT
