Zumino

Let your users
shape what you build.

Open a public board for your product and let anyone request features, report bugs, and vote on what matters next — in any language, every request brought to a close.

Public product boards

Share a board by link. Anyone submits features, bugs, and proposals; votes surface what matters, and every request moves along a roadmap everyone can see — Open, Planned, In progress, Done.

Vote & discussRoadmap statusesAuto-translated

Feature requests

48 open
TopNewAll types
  • 128
    FeatureIn progressmobile

    Dark mode for the mobile app

    #42Aiko·2d6
  • 74
    BugPlannedexport

    CSV export drops the last row

    #39Mikhail·5d2
  • 23
    Improvement

    Keyboard shortcut for quick search

    #31Sam·1w
31Closed
  • Votes sort the board — the loudest ask rises.
  • Status carries each request along the roadmap.
  • Feature, bug, improvement or idea.
  • Written in any language, read in yours.

Boards your coding agents can use

Every board is reachable over a plain REST API, so an agent working in your repository can read the roadmap before it plans, file a bug with the stack trace it just saw, triage what comes in, and move an entry to done when the fix ships.

  • Claude Code
  • Codex
  • Cursor
  • GitHub Copilot
Your boards

Named because they are common, not because the list is closed — it is ordinary HTTP, so curl, a CI job, or a script of your own works just as well.

Personal tokens

A token acts as you: it reaches exactly the boards you reach, writes under your name, and loses access the moment you leave a workspace. Nothing new to administer.

One command, one skill

npm i -g @zumino/cli gives your agents a command they already know how to use, and zumino skill install teaches them what the words mean. Every response says whether the CLI is still current, so it cannot drift from the API without saying so.

Read-only when you want it

Mint a token that can report but never write. Anything that is not a read is refused before the request body is even parsed.

A versioned contract

/api/v1 is documented field by field and pinned by tests, and every capability the web app has is reachable over it — a test fails if one is not. Fields may be added; the ones you already read will not move.

Coming soon

The AI-native team layer — designed for, and on the way.

MCP for agents

The REST API is live today. MCP is next — connect an agent without writing a single HTTP call.

Requests → roadmap

Promote a public request straight into an internal issue and close the loop.