Roadmap
What we’re building next. The usual disclaimer, meant sincerely: this is direction, not a delivery contract. Order and shape can change as early-access users bend it.
Live now
Cycles
Coming, not shipped yet: Time-boxed planning on top of the board, so “what are we doing this week” is a view, not a meeting. A cycle is a view over the board rather than another container, and work joins the current cycle the moment someone (or some agent) starts it. The week rolls over on its own: unfinished work carries forward, finished work stays as the record of that week.Scheduled automations
Coming, not shipped yet: Recurring, unattended work (“groom the backlog every morning”) under the same contracts and review gates as everything else. Every automation ships switched OFF and names what it will do before you turn it on, because unattended and metered is a combination that should never be a default.Next to build
Cycle planning
Coming, not shipped yet: When a cycle rolls over, Masaro drafts the next one: keep what still matters, drop what quietly stopped mattering, add what should fill the rest. A proposal you approve or dismiss, never an edit it makes for you, and off until you ask for it.In design
Designed, not built. The mechanics for these are written down in detail and no code exists yet, which is a real distance from shipping, so we say it plainly instead of filing them under “next.”
GitHub integration
Coming, not shipped yet: Tasks that link to branches and PRs, so “In Review” on the board and “review requested” on GitHub stop being two facts you reconcile by hand. Until it exists, agents connected over MCP already read and write tasks while they work in your repository.Linear sync
Coming, not shipped yet: For teams already living in Linear: import an existing workspace, then keep issues mirrored, so a team can move over without a hard cutover and agents can work Masaro-structured tasks without anyone leaving their tracker.Direction beyond that
Further out and deliberately vaguer, because it is. No design, no dates, no promises: these are the problems we think are worth solving next, not commitments.
- Richer verification: tightening the loop between acceptance criteria and actual checks, so “met” carries more proof and less assertion.
- More of the agent lifecycle on the board: deeper visibility into what agents did and why, beyond the progress feed.
What we won’t do
Bloat the board into a project-management theme park. Masaro stays fast, keyboard-first, and opinionated about one thing: teams (human and AI) build the right thing when done is defined and everyone can see it. Features that don’t serve that loop don’t ship.
Want something moved up? Tell us once you’re in. Early-access feedback is most of how this list gets ordered.
Help decide what ships next.