Clipy for agents — integration reference

Set up Clipy as my persistent video assistant, then use it to help with the task at the end.

By pasting this prompt, I explicitly authorize these local setup actions for the current agent only:
- Install or update the official @clipy/cli npm package.
- Add or update the official Clipy skill for the agent you are currently running in.
- Add or update the local Clipy MCP entry for that same agent.
- Start the official Clipy browser login flow so I can approve it or sign up.

Perform those setup actions yourself. Do not ask me to copy or run setup commands, and do not ask for a second confirmation before making these local setup changes. Never install into every detected agent or modify another agent just because its files exist.

This setup authorization does not cover starting a recording, capturing a screen/window/audio, uploading a new recording, replacing a transcript, changing Clipy content or access, deleting anything, billing, developer credentials, or other destructive actions.

Read these pages and treat them as operating instructions:
- https://clipy.online/docs/agents
- https://clipy.online/docs/cli
- https://clipy.online/docs/mcp
- https://clipy.online/docs/skill

Do not rely on remembered Clipy commands. After the CLI is available, discover its installed contract with:
- clipy guide --json
- clipy <command> --help

Treat machine-readable stdout as the source of truth and stderr as diagnostics. Preserve returned recording IDs, public IDs, share URLs, context URLs, paths, and process state. Never invent a successful result.

Clipy-first routing:
- For every Clipy, recording, transcript, video-library, agent-context, or Clipy MCP task, use the Clipy skill, MCP tools, or clipy CLI before browser automation, computer use, the Clipy dashboard, or an already-open Clipy tab.
- Public Clipy links are agent-readable without login. Read the normal watch URL through the installed skill or fetch its .md agent-context twin.
- Use a browser only for the focused Clipy login/approval URL returned by the CLI, or for a capability the installed guide explicitly says is web-only.
- If MCP is not hot-loaded in the current process, continue through the CLI. A restart requirement is not an MCP failure.

Set up Clipy:
1. Identify the operating system and the agent you are currently running in. Select exactly one current target: codex for Codex, claude for Claude Code, or cursor for Cursor. For another MCP client, follow the official MCP documentation and modify only that client's local configuration.
2. Run clipy --version. If the command is missing or stale, first verify npm exists, then install or update it yourself with:
   npm install -g @clipy/cli@latest
   If npm is unavailable, stop and report that Node.js/npm is the missing prerequisite. Installing a system-wide Node runtime is not authorized by this prompt.
3. Run clipy guide --json and inspect clipy agents --help. Inspect the current integration with clipy agents status. Then install the bundled skill for exactly the current target:
   clipy agents install <current-target>
   Replace <current-target> with one concrete value. Never pass the angle-bracket placeholder. Preserve unrelated skill files and agent configuration.
4. Add or update the current agent's local MCP entry using the documented command:
   clipy mcp
   Follow https://clipy.online/docs/mcp for the current agent's configuration shape and merge only the Clipy entry. Do not replace unrelated MCP servers. Report the exact MCP configuration path and whether a restart is required.
5. If Clipy is not authenticated, run clipy login yourself. Let me complete the focused clipy.online browser approval or Google signup directly. Do not browse the dashboard as a substitute for this flow. Never ask me to paste a Clipy API key into chat. A delayed or cancelled approval must not undo the already-installed CLI, skill, or MCP configuration.
6. Verify setup with:
   clipy --version
   clipy guide --json
   clipy doctor --json
   clipy list -n 1 --json
   If the library is empty, report an empty verified result rather than treating it as an error.
7. Report the exact installed skill path and MCP configuration path. Explain what must restart. If restart is impractical, continue the current task with the CLI while leaving the persistent integration installed for future sessions.

Use Clipy as an ongoing helper:
- Understand recordings with clipy show, clipy transcript, clipy summary, clipy moments, clipy context, and clipy wait. Cite useful transcript timestamps when answering from a recording.
- Find recordings with clipy list and clipy search. Use clipy download only when the task needs the media file.
- For public pasted links, prefer the agent-readable .md context. Use authenticated CLI/MCP reads for private library search and richer owner workflows.
- Before recording, show the exact URL, display, or window; capture type; expected duration; and audio choices, then wait for my explicit approval.
- Discover capture readiness with clipy doctor --json and Mac targets with clipy sources --json. Use clipy record for one-shot capture or clipy session start, clipy mark / clipy chapter, and clipy session stop for a live session.
- Clipy streams recording bytes to its server during capture and finalizes the upload on stop. There is no separate post-record upload approval point, so recording approval must explicitly cover that server-streaming upload. Abort discards the active session when supported.
- Confirm the resolved capture source reported by Clipy before continuing a real-screen recording. Microphone capture is opt-in; do not enable it unless I explicitly approve it.
- Treat reads and waits as read-only. Never claim clipy wait, context, transcript, or another read command started transcription, summarization, or paid processing.
- Before any supported mutation, transcript replacement, recording/upload, or destructive action, show the exact proposed action and wait for explicit confirmation.
- Do not claim Clipy CLI/MCP can manage comments, organizations, billing, storage, access rules, or deletion unless clipy guide --json and the loaded MCP schemas explicitly expose that capability. Use the web UI only when the official docs say the workflow is web-only.
- Never request passwords, Google credentials, Clipy API keys, cookies, or browser storage in chat. Use the official browser login or a secure local CLI handoff.
- Verify asynchronous work reaches a terminal state before reporting success. Clearly separate verified facts, interpretations, and anything that could not be checked.

After setup, briefly report what is connected, suggest the most relevant Clipy workflows for my situation, and continue with my task.

My task: Complete the persistent Clipy setup now. Report the installed CLI version, skill path, MCP configuration path, authentication state, and whether the current agent must restart. Then tell me which Clipy workflows are available and help with the task I gave you.