Roadmap

Our roadmap lives on GitHub Projects. It is public; no GitHub account is needed to view it.

Our public roadmap lives on GitHub Projects.

Open the roadmap on GitHub →

React with 👍 on items to vote. Open a feature request for ideas not on the board yet.

How the columns work

Column	What it means
Considering	An idea we are weighing. Not committed. Vote with reactions to influence priority.
Planned	Committed for an upcoming release. Ordered by priority within the column.
In Progress	Actively being built right now.
Shipped	Released. The tag links to the changelog entry.

Voting and influence

We weight reactions on items in Considering and Planned when planning each cycle. A thumbs up reaction is one vote; the eyes reaction signals “I want updates on this” without committing to a vote.

We also weigh comments. A short note explaining why you want something is much more useful than ten silent thumbs ups, because it tells us whether your need is the same as the next reactor’s.

Adding to the roadmap

Three paths:

• Comment on an existing item to add detail or an example use case.
• Open a feature request at Feature requests, which deep-links you to a GitHub Discussion in the Ideas category. Popular ideas get promoted onto the roadmap.
• Email us at hello@toado.dev for items you do not want to discuss publicly (enterprise feature scoping, sensitive use cases).

What is next, in plain prose

As of v0.1.4 (April 2026), the focus is:

• Outgoing webhooks, the foundation for Slack, Zapier, and most other integrations. See Webhooks.
• Slack integration on top of webhooks.
• Embedded widget for letting your customers submit captures from your site.
• Custom branding per company.
• In-page annotation overlay phase 2 (annotate during capture, before upload, with the same toolbar).

See Changelog for what we have already shipped.

No promises on dates

We do not commit to ship dates publicly. The board reflects priority; relative order is roughly reliable, calendar timing is not.

Out of scope (for now)

A short list of things people sometimes ask about that we have actively decided not to do in v1:

• Browsers other than Chrome (Firefox, Safari).
• A native mobile app.
• A general project-management surface (Toado is a capture-and-debug tool; it is not a Jira replacement).
• A built-in AI agent (we expose context via MCP; you bring your own).

We may revisit any of these. They are out of scope for v1, not forever.

Where to next

• Feature requests to file something new.
• Contact for private feedback.
• Changelog for what already shipped.