Skip to content
os board.
Create a board
Agent-led feedback for product teams

Turn “it broke” into evidence engineering can use.

Give users a branded place to report bugs, propose features, and tackle paid product requests. OS Board asks the follow-ups, packages the evidence, and sends accepted work to Linear or GitHub.

Create your feedback board See it live on June
Public boardPrivate reportsRewards for accepted work

Your board can be discoverable. Individual reports stay private to your team by default.

From raw feedback to a decision-ready report
O
Open SoftwarePrivate report · Voice mode
In review
01
Raw report

“Voice mode dies when I switch microphones.”

02
OS Board asks

Does it still happen after restarting? Which microphone and macOS version?

03
Decision-ready evidence

macOS 15.5 · second microphone switch · reproduced 3/3 times

Ready for review$100 funded request
Not another form

The agent does more than summarize. It improves the evidence.

Every follow-up is chosen to make the report easier to reproduce, assess, and hand to engineering.

01Collect the missing context

Reproduction steps, environment, screenshots, recordings, affected workflow, and business impact.

02Find signal before review

Likely duplicates and sensitive security reports are flagged before they become another team inbox problem.

03Move accepted work forward

Turn a decision-ready report into a linked Linear or GitHub issue without reformatting it by hand.

Two reward modes

Thank useful work. Fund the work you need.

Keep everyday feedback open, then use explicit funded requests when participation and evidence quality really matter.

01Contribution tips

Reward a report after it proves useful.

Thank contributors for accepted bugs, strong reproductions, and thoughtful feature evidence. The amount remains up to your team.

Always-on intake · Team discretion
02Funded requests

Publish the work and reward up front.

Ask for a specific test, recording, or prototype with the deadline, evidence, acceptance criteria, and reserved reward visible before work begins.

“Stress-test microphone switching on macOS” $100 per accepted finding

After acceptance, contributors choose an available payout rail: dollars or supported tokens.

One account, two views

Both sides of the feedback loop.

Contributors manage their work. Teams review the evidence. The two views stay connected without mixing the jobs together.

ContributorTeam
Example workspace
J
Contributor dashboard

Know what happens after you submit.

Track reports, answer follow-ups, discover paid requests, and claim accepted rewards.

  • Voice mode stops after switching microphones Needs info
  • Pin a workspace to the menu bar Accepted
Open contributor dashboard
O
Team dashboard

A review queue, not another inbox.

Review evidence, request more detail, publish funded work, and move accepted reports into engineering.

  • Evidence completeness 92%
  • Likely duplicate Flagged
  • Decision Accept · Need info · Decline
Open team dashboard
Fits the workflow you have

Evidence in. Issues out.

Accepted reports can create or link engineering issues, while contributors keep seeing the status from OS Board.

OS BoardAccepted reportLinear or GitHubLinked issueContributorRelease update
Start with one board

Give your users a better way to help.

Collect private, decision-ready feedback on a branded page—and reward the contributions that move your product forward.

Create your boardExplore June’s board