One canvas for the whole team

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.

Free while in preview. Sign in with Google or an email link, no invite needed.

Home
Felix Mobile App
Gleamly Web
CanvasPrototype
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

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.

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
  • Anyone can comment from a link, with no account
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 with your own credentials
  • Drafts live on a branch, never on a dirty tree
  • Every draft gets a preview link the whole team can open
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
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
  • Failed tasks can go to an agent as a fix request
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.

How it works

Two minutes to a shared canvas

Step one

Point Commons at your app

On the Mac app, choose your repo and Commons finds your routes and puts every screen on the canvas. No repo on hand? Paste your deployed preview URL instead.

Step two

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.

Step three

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.

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 it cost?

Nothing while Commons is in preview. Agent runs use your own Anthropic credentials, 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.

Open Commons Download for Mac