LocalBridge

Who it is for

LocalBridge for journalists

If your day involves checking a story against every source you have open, the bottleneck is not the assistant. It is the twenty minutes spent assembling context before you can ask anything.

What slows journalists down

  • The same event is reported four ways and the differences are the story.
  • Pasting articles one by one loses which outlet said what.
  • Deadlines leave no time to re-read six tabs before filing.

The workflow

  1. 1. Open every report of the event in one window, including the primary source.
  2. 2. Send them together so each claim stays attached to its outlet.
  3. 3. Ask for the contradictions and the unsourced claims, not a summary.

Pages journalists send most

  • News articles: the headline, byline, date and article body.
  • Financial filings: the filing text, section headings and tables that render as HTML.
  • Reddit threads: the post body and the comments that are expanded on screen, with scores where shown.
  • Forum threads: the original post and the visible replies in order.

Common questions

Why would journalists need this rather than just pasting?
Pasting works for one page. The work described here is checking a story against every source you have open, which means the question only makes sense once several pages are in front of the assistant at the same time.
Does it work with the tools journalists already use?
It reads whatever your browser renders, so anything you can open in a Chrome tab and read yourself can be sent, including tools you are signed in to.
Is anything sent to LocalBridge servers?
No. Page text travels from your browser to the assistant you picked. We never receive it, and we do not keep copies.
What does it cost?
A one-time licence, not a subscription. You bring your own Claude or ChatGPT account, on whatever plan you already have.

Keep reading

Get LocalBridge

One click sends your open tabs into Claude or ChatGPT. One-time licence, no subscription.

See how it works