Free while in preview · no invite needed

Design on the product,
not pictures of it.

Commons puts your running app on a shared canvas. Your team comments on the real screens, hands feedback straight to a coding agent, and the reasoning stays attached to the work instead of scrolling away in chat.

Sign in with Google or an email linkFull canvas in the browserv0.2.154 · Apple silicon

Screenshot placeholder
Home
Felix Mobile App
Gleamly Web
PrototypeCanvasFlow
dev · :4310 · main
Narrate
Share
Home /
Send money /send
Goals /savings
KC
MS
The ask box holds its position no matter how long the answer runs, so beginning a question feels like focus, not a screen change. commit 4cf2699thread
Works with Next.js Vite Expo React SvelteKit GitHub Vercel Figma Slack Claude Code

Mocks go stale the moment code lands.

When agents can ship a change in minutes, the design file is out of date by lunch. Commons moves the conversation onto the thing that actually runs, so feedback lands where the work is and nobody reviews a screenshot of last week.

What it does

Comment on it. Draft it. Prove it.

One canvas showing the app that actually runs, for the whole team that argues about it.

Thread
Kyle
Maya
Comment

Pin feedback to the real screen

Click anywhere on the live app to start a thread anchored to that screen and route. Guests join from a link, no account.

Agent
running
✓ Read the screen and thread
✓ Drafted on its own branch
● Building the preview…
Draft

Turn a thread into a working draft

Hand a comment to your coding agent. It picks up the screen, the route, and the conversation, and reports back with a preview link.

Tests
12 sessions
Send to a saved contact 92%
Set up a recurring transfer 41%
Prove

Test with real people, results on the canvas

Send one link. Testers use your live app in the browser, and success rates, heatmaps, and paths come back to the same screens.

Comment

Pin feedback to the live screen

Every screen on the canvas is your real app, rendered from a local dev server or a deployed preview link. Click anywhere to leave a comment anchored to that screen and route, not to a rectangle that used to look like it.

  • Threads, replies, and @mentions with your teammates
  • Live cursors and presence while you review together
  • Share links open the same canvas: guests browse, read, and comment with just a name
  • Figma frames land beside live screens, commentable like everything else
  • Screens keep themselves current: a deploy refreshes every snapshot
Screenshot placeholder
Thread
Home · /
Kyle
The balance reads as spendable but it aggregates linked accounts. Can we name it so nobody tries to send all of it?
Maya
Agreed. "Total across accounts" and keep the sendable figure separate.
⚡ Send to agent

Agents

Turn a comment into a working draft

Hand a thread to your coding agent and it picks up the whole context: the screen, the route, the conversation. It works on its own branch and reports back, so review stays a conversation instead of a ticket handoff.

  • Runs on your machine, or in your repo's own GitHub Actions with nobody's laptop awake
  • Drafts live on a branch, never on a dirty tree
  • Every draft gets a preview link the whole team can open
  • Connect GitHub once and preview links fill themselves in from your deploys
  • Your own Anthropic or OpenRouter key, set in the app, never in a terminal
Screenshot placeholder
Agent session
running
✓ Read src/screens/bank.tsx
✓ Renamed the aggregate label
✓ Split sendable balance into its own row
● Running the build…
Draft ready
commons/balance-label · 2 files changed. Open the draft preview to compare against main.

Narrate

The why, with receipts

Commons reads your comment threads, test results, and code history, then drafts the thinking behind each screen and cites where every claim came from. You approve what is right, and the rationale rides along with the work for whoever asks next quarter.

  • Citations back to commits, docs, threads, and tests
  • Honest labels when it is inferring rather than quoting
  • Nothing is published until a person approves it
Screenshot placeholder
Narrate
4 drafts to review
Pay opens straight onto a full height keypad because the amount is the first thing your thumb meets, not a menu. commit a91f22cdoc PLAN.md
The progress bars stay quiet on purpose, so the screen reads as encouragement rather than a performance dashboard. inferred
Approve EditReject

User tests

Test with real people, results on the canvas

Write tasks, send one link. Testers open your live app in the browser with no account and no install. Success rates, times, and the paths people took come back to the same canvas the team is already working on.

  • Click heatmaps drawn straight onto the screens
  • A and B variants against two preview links
  • Recruit real visitors with one script tag on your site
  • Failed tasks can go to an agent as a fix request
Screenshot placeholder
Tests
12 sessions
Send money to a saved contact 92%
Find the emergency fund balance 83%
Set up a recurring transfer 41%
Most misses land on the schedule row, not the amount field.

Flow

The whole app as a map, drawn from real use

Screens laid out by how deep they sit in the journey, joined by the paths people actually took. Nobody maintains it: the edges come from recorded sessions, so the map is a record rather than a diagram someone last touched in March.

  • Screens nobody ever reached are parked where you cannot miss them
  • Error, empty, and loading states sit beside the happy path
  • A browser crawl can go find those states in your deployed preview
  • Nothing a crawl finds joins the map until a person approves it
Screenshot placeholder
Flow
3 states to review
✓ Home → Send money → Confirm
✓ Home → Goals
◇ Recurring transfer · never reached
Crawl found 3 states
Send money: empty amount, declined card, offline. Approve the ones that are real.
Approve Reject

Add your first project in a couple of minutes.

Free while in preview. No invite, no install for the browser.

Open Commons

How it works

Two minutes to a shared canvas

Point Commons at your app

Connect GitHub and your deployed repos appear as projects on their own. Or point the Mac app at a repo: routes are found and every screen lands on the canvas. A monorepo asks which app you meant. No repo, no GitHub? Paste a preview URL.

Bring the team in

Teammates sign in on the web and see the same screens with no install. For anyone outside the team, share a link that needs no account at all.

Comment, draft, ship

Feedback becomes a thread, a thread becomes an agent draft, and the draft becomes a preview link anyone can open before it merges.

Who it's for

Three jobs, one canvas

The people who argue about a product rarely share a tool. Designers work in a file, engineers work in the repo, and PMs work in whatever screenshot reached them last. Commons is the same live app for all three.

Product designers
Critique the build, not a picture of it
  • Pin a comment to the real screen at the real breakpoint
  • Figma frames sit on the same canvas as live screens
  • Hand a thread to an agent and get a draft with a preview link
  • Rationale drafted with citations, published only when you approve it
  • Heatmaps and task results from real testers land on the screens
Engineers
Feedback that arrives with its context
  • Point at the repo: routes are found and each screen runs from your dev server
  • Agents run on your Mac or in your repo's own GitHub Actions
  • Drafts land on a branch, never on a dirty tree, never merged for you
  • A monorepo asks which app the project is instead of guessing
  • Comments carry the route and the commit, so nothing arrives as "the thing looked wrong"
Product managers
See the state of it without asking anyone
  • No install and no terminal: the full canvas runs in the browser
  • Share a link with execs and customers who have no account
  • Flow view draws every path real testers actually took
  • Task success rates, times, and where people gave up
  • Preview links keep themselves current from your deploys

Access

The right door for each person

One product, three levels of access. Nobody installs anything they do not need, and nothing is shared wider than you chose.

Your team
Signed in, in your workspace
  • Every project on the canvas
  • Comment, narrate, run tests
  • Mac app adds local dev servers and agents
Anyone signed in
Their own workspace
  • Bring their own projects
  • Sees nothing of yours until invited
  • Free to try in the browser
Stakeholders and testers
A link, no account
  • One project, view and comment
  • Design rationale travels with it
  • Perfect for usability sessions

Questions

The honest answers

Do my teammates need the code to use this?

No. Whoever has the repo runs it locally and everyone else sees the same screens through a deployed preview link. Designers, PMs, and stakeholders never touch a terminal.

Will it touch my repository?

Only when you ask. Commons never works on a dirty tree, never merges for you, and never stores git credentials. Agent drafts live on their own branch and you decide what happens next.

Is it Mac only?

The desktop app is macOS today, and it is what you need to run dev servers and agents locally. Everything else, including the full canvas, works in any modern browser.

Does it replace Figma?

No. Figma is where you explore what does not exist yet. Commons is where the team works on what already runs. Most teams use both, and the handoff between them gets shorter.

What does connecting GitHub actually give you?

Your deployed repos appear as projects on their own: the next production deploy of a repo Commons has never seen becomes a project, preview link and all. Deploy events keep those links current, and agents get a place to run when no laptop is awake. Commons reads only the repos you picked during install, matches them only inside the workspace that installed it, and never recreates a project a person archived or deleted. You can run everything without it and paste preview URLs by hand.

My repo has a web app and a mobile app in it.

Commons asks which one the project is rather than picking for you. They are two projects: add the repo twice and choose a different app each time.

What does it cost?

Nothing while Commons is in preview. Agent runs use your own Anthropic or OpenRouter key, so you are never billed through us for model usage.

Put your product on the canvas.

Open Commons in the browser and add your first project in a couple of minutes. Bring the people who have opinions about it.

Free while in previewNo invite neededv0.2.154 · Apple silicon