Write the problem hypothesis
For [team], moving data between [system A] and [system B] requires [manual work], causing [delay or errors].
You can name one user, one situation and one measurable consequence without proposing a feature.Feature: opt-in SAFARI_MCP_ALLOW_USER_TABS to act on the user's existing tabs (default off)
Evidence observed in achiya-automation/safari-mcp, a Coding project.
2 comments0 positive reactions22 days openProject Radar 82
Start free validation sprint4 guided steps · private notes · cloud sync
SOURCE EVIDENCE
Read original GitHub Issue ↗Start with what users actually said
Reporter context: Context The server has a deliberate tab-ownership model: once it has opened its own tab, it refuses to read/click/navigate/inject into tabs the user opened, and refuses to fall back to the frontmost ("user") tab if tracking is lost. The code is careful about this, and for the default case that's the right safety…Excerpted from the public Issue. Read the complete thread before interpreting it.
Interview five affected users
- Which systems must exchange data?
- What triggers the handoff?
- Which fields or permissions block it?
- How is it handled today?
- Who owns failures between systems?
Run the smallest experiment
Manually operate or prototype one high-frequency connection for one team before building a general connector.
A user completes the real cross-system workflow twice and asks to keep the connection active.Make a build decision
- Build: repeated pain and active commitment
- Narrow: pain is real but the audience or job differs
- Stop: weak frequency or no behavioral proof
Why this brief exists
Information has value only when it changes action. This page turns one public signal into a bounded validation exercise. It is a research aid, not proof of demand, investment advice or a product recommendation.