Pull requests to ChatGPT
How to send pull requests to ChatGPT
You have pull requests open and a question that spans all of them. This walks through what ChatGPT actually receives, what it will not get, and how to phrase the question so the extra context earns its place.
What gets captured
From pull requests, LocalBridge takes the PR description, review comments and visible diff text. Page furniture such as navigation, sidebars and cookie notices is dropped before anything is sent, which keeps the batch small enough for ChatGPT to reason over rather than skim.
ChatGPT works best when the pages arrive as one clearly numbered block followed by your question.
Step by step
- Step 1
Open the pages you care about
Put the pull requests you want answered in one browser window. Leave out everything unrelated: irrelevant pages cost context and pull the answer off topic.
- Step 2
Tick the tabs to send
Open LocalBridge and tick each tab. It reads the PR description, review comments and visible diff text, and drops navigation, sidebars and cookie banners.
- Step 3
Send to ChatGPT
Click the ChatGPT button. The pages arrive as a numbered list, each with its title and URL, so you can refer to source two by name.
- Step 4
Ask the question that needed all of them
Follow the context with something only the full set can answer. For example: "Review these changes and list the risky parts first."
Where it falls short
Large diffs are truncated, so send the PR page plus the file you care about.
Published 2026-09-15. If OpenAI changes how ChatGPT handles pasted context, this guide is updated rather than left to drift.
Common questions
- Does ChatGPT read the whole of each page?
- It reads what LocalBridge captured: the PR description, review comments and visible diff text. Each page is capped so one long document cannot crowd out the rest of the batch, and chatgpt works best when the pages arrive as one clearly numbered block followed by your question.
- What does not come through from pull requests?
- Large diffs are truncated, so send the PR page plus the file you care about.
- Do I need to be signed in for pull requests behind a login?
- Yes. LocalBridge reads the page exactly as your browser already renders it, so if the tab shows the content, it is captured. It never logs in for you and never stores credentials.
- How many pull requests can I send at once?
- Up to eight tabs per send, trimmed so the batch stays inside a comfortable context budget. For bigger sets, send them in themed batches and ask one question per batch.
- Is the page content stored anywhere?
- No. The text goes from your browser to the assistant you chose. LocalBridge does not keep a copy and does not send page content to our servers.
Keep reading
- Send pull requests to ClaudeThe same pages, sent to Claude instead.
- Send release notes to ChatGPTSame workflow, applied to release notes.
- Send documentation pages to ChatGPTSame workflow, applied to documentation pages.
- Send github issues to ChatGPTSame workflow, applied to GitHub issues.
- What a context window isWhy batch size and page length decide answer quality.
Get LocalBridge
One click sends your open tabs into Claude or ChatGPT. One-time licence, no subscription.
See how it works