--- name: recording-library description: Find and organise OpenRecorder takes, locate separate camera/screen originals, or open the local recording library when the user asks to work with OpenRecorder recordings. --- Use `openrecorder_home` to inspect the library; it returns the library state and the local origin, never an access link. Hosts that render MCP Apps show the library inline (in a window titled OpenRecorder); where a host cannot, or the client is a terminal (Claude Code CLI), use the browser. Posters and playback in an inline window depend on the host allowing them; if they show “Preview can’t load here”, open the library in the browser. To use it in a browser, call `openrecorder_action` with `op: open-library`: the recorder opens its private owner link itself and returns `opened: true`. Never ask for, construct or paste an owner link, and never use one as a share link. Use `openrecorder_action` with `op: state` for current recordings and their IDs. Match the user's title, folder or date; clarify genuinely ambiguous matches before changing a take. Use the returned IDs, never guessed paths. For original media, inspect the take's `files`: `recording.webm` / `recording.mp4` is the combined video, `screen.webm` / `screen.mp4` is the screen source, and `camera.mp4` / `camera.webm` / `camera.mov` keeps the full unmirrored camera frame. Missing originals cannot be recreated by changing a setting. For new native takes, `capture.json` records timing and the three encoded videos share the capture clock; older takes may only have approximate callback timing. Use `open-file` or `reveal` for the chosen take. Rename, move, favorite and archive through `update`. Archive preserves files and revokes links, including a link that is still starting. Sharing is protected and explicit. Only when the user asks to share a take, call `share` with `id` and `minutes` of 15, 60 or 480 (there is no default), or `0` only if the user explicitly asks for a link with no end time (it still ends when OpenRecorder quits, the share is revoked, the recording is archived or the tunnel drops; the entry then carries `never: true` and no `expiresAt`). It returns at once with `status: starting`; read `state` until the entry's `status` is `ready` (with `url`, `accessCode` and `expiresAt`) or `failed` (with `error`). Give the user the link and the access code together as the two things a guest needs, and say the code is required to watch. Only the selected combined video can be reached; originals, the library and the owner API cannot. Wrong codes are limited to five per minute across the link. The link expires at `expiresAt`, stops on `unshare`, Archive or Quit, and works only while this computer stays awake and online. Bytes a guest already received cannot be recalled. Sharing needs the optional `cloudflared` tool; if it is missing the share fails with a clear message and local use is unaffected. Do not create a share to inspect or test anything. Recording is started only by the person. There is no floating toolbar: the person records from the OpenRecorder menu-bar or tray icon, from the capture controls on their own Home page, and the camera bubble is the only floating element. `open-library` opens Home in the browser and starts only the library, never the recorder app. `open-studio` is the person's "new recording": it opens the recorder app, idle and ready, and never records, opens a device or leaves a Record press waiting. It returns at once; if `openrecorder_home` reports `backend.current: false` the running library is another version and is never replaced by ordinary use, so say that the new recorder features wait until whoever manages the installation updates it, and do not try to restart or replace it yourself; otherwise read `recorder` in `state` (`ready: true` once the app has reported; `opening`, `not-running` or `not-responding` otherwise) before telling the person it is ready, then tell them to press Record themselves. If it did not become ready, say so and offer to try again; do not call it repeatedly, and do not click anything on their screen. **MCP cannot record.** Nothing you can call starts a recording, turns the camera or microphone on, restores remembered inputs, chooses a source or checks 60 fps; the owner-only capture commands are not in the tool list and are refused for agents. The server also lists an app-only tool (`openrecorder_ui`) for the library window itself: it is hidden from you by the host, needs a session key you do not have, and you must never call it, guess its key, or try to drive the Record button. Those are the person's own controls, which ask for access only when they use them. The existing MCP `stop` action can stop the current take when the person explicitly asks; it never starts capture or turns inputs on. 60 fps is a request until it has been measured on the person's computer for the kind of take they make (display, camera, microphone and originals all matter); a synthetic encoder check does not qualify it. Do not describe it as qualified or unavailable on your own. A frame rate the person chose, or one stored by an earlier build, is theirs: never change it. After a take that stopped early, say only that it stopped early and its files were kept, and point to its Technical details; do not suggest a lower frame rate as a fix. Do not click permission buttons or start a recording merely to inspect the library. A synthetic media test does not establish that camera, microphone or screen capture works. Report the actually verified state. These limits apply to calls made through the MCP tools. They are not a sandbox: an agent with unrestricted shell or computer-use access as the same user is outside what this tool can enforce. For local installation diagnostics, run the packaged native executable with `--doctor`. It checks the bundled media helper without opening capture hardware; a source checkout can use `scripts/doctor.py`. Video editing belongs to the user's selected editor; this plugin supplies recordings and file locations. The native engine writes MP4 using hardware H.264 when the local probe succeeds, with an explicitly available software fallback. Raw camera files keep the full unmirrored frame; shapes and mirroring affect the combined video. Whole-monitor capture on Wayland can include desktop overlays; use window capture for an isolated screen source. Multi-monitor coordinate mapping and Windows hardware are not universally qualified. State exactly which host and capture path were tested.