---
title: "Visual context"
description: "Save screenshots in your repo so Claude Code or Codex can read them when you ask."
url: https://www.bigshot.pics/how-to-use/visual-context
---
# Visual context

Licence

Bigshot saves each capture in your repo with your notes, the source app, and the text in the image. When you next prompt Claude Code or Codex, the agent finds the screenshots itself. You don't paste paths or attach files.

## Set up a Project

1.  Open Settings › Projects and click **Add Project…**
2.  Choose your repo folder. Bigshot checks it without changing anything.
3.  Leave **Share captures with agents automatically** on, and the steps that add `.screenshots/` to `.gitignore` and instructions to `AGENTS.md` or `CLAUDE.md`.
4.  Click **Create Project**. It becomes the active Project.

Captures now go to `.screenshots/` in the repo. The folder stays out of Git.

## Ask your agent

Capture the problem, mark it up if it helps, then ask in your own words.

Look at my last screenshot and fix the spacing I marked.

The one with the error dialog — where does that message come from?

A capture is available on the agent's next prompt. Nothing is sent into a running conversation, so you can take several and ask about them together.

## Group screenshots with a tag

1.  Expand the island and open the tag pill.
2.  Type a name, like `checkout`, and press Return. It becomes the active tag.
3.  Capture as you go. Every new capture gets the tag.

Read the screenshots tagged checkout and list what's broken.

## Add text from the image

Turn on **Extract text (OCR)** in the Project's settings. Bigshot reads the text in each capture on your Mac and adds it to the index, so the agent can search your code for an error message or a label. Agents treat it as evidence to check against the image, not as instructions.

## Let an agent fix it

Press **⌃⌥B**, select what's wrong, and write what should change. Bigshot starts Claude Code or Codex in your repo with the screenshot and your instructions, on a new branch. You approve its requests as it works and review the commit when it's done. Bigshot never pushes or merges.

**More:** [Projects and screenshot context](https://www.bigshot.pics/docs/projects), [Hooks](https://www.bigshot.pics/docs/hooks)

[PreviousCapture](https://www.bigshot.pics/how-to-use/screenshot-tool)[NextMoodboards for agents](https://www.bigshot.pics/how-to-use/moodboards)