Beacon

A tool · Free on GitHub, MIT

A report button for your Mac or iPhone app.

Your testers press it, and you get a GitHub issue that already says what they expected, what happened, how they got there and which build they were on.

A Swift package for macOS 26 and iOS 26 apps. No sign-up needed.
Something's brokenBug
What did you expect to happen?This is the one that tells us whether the page is broken or just confusing.
What actually happened?Say what you saw on screen.
What did you do to get there?One action per line, starting from where you were.
Harbour 1.4 (212) · macOS 26.0 · MacBook AirNext

The report you get

A tester's email says "it crashed". A Beacon report says which build, which device, and what they pressed.

Beacon asks the tester the three questions in the app, at the moment it happened, and attaches the version, the settings and the log for them.

How it works

1
Add it.

In Claude Code, install the plugin and ask Claude to set up Beacon in your app. Or add the Swift package by hand.

2
Put the button in.

The Help menu on a Mac, a settings screen on iPhone.

3
Testers report.

A bug, a feature request, a change request or feedback. A bug will not send without what they expected, what happened and the steps.

4
Claude works the queue.

Each report becomes a labelled issue. A Claude session reproduces the bug before it touches anything, fixes only what is small, and writes what it did on a board you read.

The Beacon board: reports in columns, from new to triaged to done
The board, where reports move from new to done.

What arrives with a report

The tester writes what they saw. The app attaches the rest.

  • App version, build and commit
  • OS and device
  • Language, time zone, light or dark, text size
  • The app's settings
  • The last 400 lines of the log
  • Screenshots and screen recordings
  • Names and sizes of files in the folders the app names
The Beacon sheet open over an app, asking what the tester expected, what happened and what they did

The sheet inside an app, as a tester sees it. Everything a developer usually has to ask for in the follow-up email is already there when the issue opens.

Bugs and triage

A bug cannot be sent without the steps, and triage reproduces it before touching code.

It refuses a vague bug

A bug needs what the tester expected, what happened and the steps before it sends. On a Mac, the on-device model reads the report before it goes and asks a follow-up if something is missing. It never rewrites what the tester wrote.

Reproduce first, then fix

Triage tries to reproduce a bug three times on the build it came from. A fix is made only when it touches three files or fewer, and it is merged only after the app passes the tester's own steps. Everything bigger gets a written diagnosis for you.

You decide what gets built

Feature requests and feedback are labelled and left for you. Triage never builds a feature or writes to a tester.

What stays private

File contents are never read, only names and sizes. Passwords and keys are masked before anything is sent. A page for testers lists every field a report carries, so you can hand it to them as the privacy notice.

Three ways to set it up, none tied to an Up Coast account: Claude alone, GitHub, or a relay so testers never need a GitHub account. The relay works for a website too.

From Abbey

These steps to reproduce can be really, really hard to get from people. They'll say things like, well, I logged in. No, I need to know what you did.

Always give the expected behaviour, the actual behaviour and the steps to reproduce for a bug. You'll just save yourself so much time.

Abbey Jackson, Up Coast

Two commands in Claude Code install it.

Free, MIT. In Claude Code, add the marketplace and install the plugin, then ask Claude to set up Beacon in your app.

/plugin marketplace add Up-Coast/beacon
/plugin install beacon@up-coast