PeekLet your coding agent see your screen.
Peek's MCP server and the peek command give Claude Code, Codex and Cursor your captures, already read and masked. Your agent can even ask you to point at something.
# connect Claude Code, Codex and Cursor $ peek setup --dry-run $ peek setup # later, in your agent's terminal $ peek last $ peek capture --app "Google Chrome" --focus "is the checkout button visible?" # undo everything setup changed $ peek setup --remove
Connect once.
- 01
Install the command
Settings › Agents › Install
peeklinks it to~/.local/bin/peek. - 02
Connect your agents
Settings › Agents › Connect Claude Code, Codex & Cursor, or
peek setup, adds Peek's MCP server and a skill to each agent. - 03
Change your mind any time
Setup backs up every file it edits.
--dry-runshows the plan first;--removeundoes it.
9 MCP tools
Reading captures is free, so any agent can use Peek. Starting a capture from the agent is Pro.
| Tool | What it does | Plan |
|---|---|---|
get_latest_capture | The most recent capture, described and masked | Free |
list_captures | Recent captures | Free |
get_capture | One capture by id | Free |
capture_screen | Captures the whole screen or one app | Pro |
ask_user_to_select | Asks you to drag over an area | Pro |
describe_capture | A full description of one capture | Pro |
start_timed_capture | Captures on a timer while something happens | Pro |
stop_timed_capture | Stops a timed capture | Free |
timed_capture_status | Whether a timed capture is running | Free |
The peek command
The same captures from any terminal or script. Text output is shaped for a terminal agent unless you ask for another format.
$ peek last # latest capture $ peek last --format chat --json $ peek select --focus "the failing test output" # Pro $ peek last --scp devbox # Pro $ peek last --tmux work:0.1 # Pro $ peek watch start --every 10 --for 300 # Pro $ peek health
Session context
Prooff by defaultSettings › Agents › Connect captures to my agent session. When you capture while working with a coding agent, Peek reads that agent's own history on this Mac, so the description can say how the screenshot relates to your task.
| Agent | Where Peek reads it |
|---|---|
| Claude Code | ~/.claude/projects/ |
| Codex | ~/.codex/sessions/ |
| Cursor | The focused chat of the window's workspace |
| Gemini CLI | ~/.gemini/tmp/ |
| OpenCode | Its local database or storage files |
| Aider | .aider.chat.history.md in the project |
| VS Code Copilot Chat | Its chat sessions in workspace storage |
What is read and sent
- Only a session active in the last 30 minutes, 10 for the desktop apps.
- At most your last 4 requests, the files the agent touched and its last reply, each clipped and masked.
- Peek first checks on your Mac that the screenshot shares something concrete with the session. If not, nothing from the session is sent.
Questions
The app and the command talk over a Unix socket that only your user can open. Nothing listens on the network.
Which agents does setup connect?
Claude Code, Codex and Cursor. Any agent that can run a command can use peek last.
Do I need Pro for my agent to read captures?
No. Reading captures with peek last and the MCP tools is free. Pro lets the agent start captures and ask you to point.
How do I undo setup?
peek setup --remove. Setup backed up every file it edited.
Does session context send my whole chat?
No. At most your last 4 requests, the touched files and the agent's last reply, clipped and masked, and only when they match the screenshot.
Give your agent eyes.
Reading captures is free. Every Pro feature is free for 14 days.