Give your agent
a video editor.

Record, edit and export from a conversation. Connect your local agent to Screengaze and review the result in the editor.

Connect my agent See what you can ask

From request to video.

You explain what you need. Your agent uses Screengaze’s authorized tools to work on the recording.

See example requests

Prepare the take.

Choose what you want to record. Your agent can inspect sources and start and stop a capture with the required permissions.

Ask for the next adjustment.

Trim the open project with an instruction. Review the changes in the editor and keep shaping your recording.

Prepare the output.

Ask for an MP4 or GIF and review the file when the export finishes. Your mode and format limits still apply.

Connect your agent.

Guides for Codex and Claude Code · Local MCP

Your agent

Open Screengaze and paste the prompt into a local agent on your Mac.

View prompt

Connection prompt for Codex

Set up Screengaze on this Mac for use from Codex, including its MCP and the skill bundled in the application. I authorize you to register or update only Screengaze and install its skill for my user, preserving the rest of my configuration.

Locate Screengaze.app. The path selected in the guide is "/Applications/Screengaze.app"; check it and use the actual absolute path if different. Verify that it contains an executable Contents/Helpers/FrameStudioMCP and Contents/Resources/Automation/skills/screengaze/SKILL.md. Do not invent flags: the helper has no --install option.

Check whether screengaze is already registered using codex mcp get screengaze. Keep a correct configuration and avoid duplicates. Register or update only that integration using Codex's supported mechanism, stdio transport and user scope. For a new entry, the command with the selected path is:
codex mcp add screengaze -- '/Applications/Screengaze.app/Contents/Helpers/FrameStudioMCP'
Codex stores this personal configuration in ~/.codex/config.toml by default; respect any custom location. If the entry exists and differs, back up the configuration and update only [mcp_servers.screengaze].

Install the entire bundled skill folder in ~/.agents/skills/screengaze. If it exists, compare its contents and keep a backup outside skill directories before updating it. No official skill repository publication is required. Invoke it with $screengaze.

Verify registration using:
codex mcp list
codex mcp get screengaze
Also check the helper version and catalogue using --version and --list-tools with its actual path. The catalogue does not prove a connected session. If this conversation needs to reconnect or restart to load the integration, provide instructions and an exact, self-contained continuation message for the new session.

Open Screengaze and guide me to enable “Permitir conexiones MCP locales” under Edición y salida → Integraciones · Agentes, then approve “Permitir sesión” using its normal controls. The app buttons copy commands; they do not run installation. Do not enable frame or transcript sharing yourself. Distinguish client permissions, Screengaze approval and macOS permissions.

Once the tools are available, call only get_status with no arguments. It may return an unauthorized status: if approval is needed, tell me and repeat get_status after “Permitir sesión”. Do not open or modify projects, record or export.

Confirm separately: helper located, MCP registered, skill installed, session authorized and actual status query. Mark anything you could not verify as pending; do not confuse registration or the catalogue with an actual authorized call.

Do not download software or install other clients automatically. If the app, Codex, its CLI or local Terminal access is missing, explain the blocker and the specific next step.

You can also copy the text manually.

Different app location or manual setup

Your agent works. You stay in control.

The integration starts disabled. Authorize a session in Screengaze and choose what content you share with your agent.

Video is processed on your computer.

Screengaze captures, edits and renders in the native app. You can review the project in the same editor.

Access starts with you.

Enable MCP and approve the session. You can revoke that access from Integrations whenever you need to.

Sharing is a choice.

Frames and transcripts are shared separately and are off by default. If you share them, they may reach your agent’s model provider.

Understand permissions and privacy choices

Before you connect your agent.

What do I need to get started?

The current integration requires Screengaze and a local client with Terminal access on the same Apple Silicon Mac. The guide includes setup for Codex and Claude Code. Check the download page for release availability and compatibility.

Can the agent make a demo by itself?

Screengaze captures and edits. To click, type or navigate in the app you want to demonstrate, your agent also needs browser or desktop tools on that Mac.

What stays on my computer?

Screengaze captures, edits and renders locally, but your agent’s model may be remote. Images and words you choose to share may be sent to its provider. Frame and transcript sharing are off by default.

Do export limits change?

No. MCP follows the same free-mode and license rules as the app. Format and export conditions still apply.

Your next edit can start with a request.

Follow the guide to connect your agent and verify its access with a real status query before you start recording or editing.

Connect my agent Check availability

Give your agenta video editor.