Skip to content
Changelog

What is in the beta today

We have not published numbered releases yet, so instead of an invented history, here is what the product does now, by area. Dated release notes start here once the beta opens up.

Agents & MCPIn beta

An MCP server your coding agents can trust

135 tools over the same database, roles and workflow rules as the app, discovered by the official MCP client in our verification suite.

  • plan_context matches a git remote to an application and returns its plan
  • OAuth 2.1 with PKCE, consent, read/write scope, rotating refresh tokens and revocation
  • Version-checked writes and atomic bulk edits of up to 100 tickets
  • daily-update, plan-open-tickets and analyze-application prompts
  • Ten workflow skills for Claude Code and Codex: intake, planning, implementation, status, questions and more
  • Plans, specs and reports attached to tickets as artifacts, with their sources checked by the server
Read more about an mcp server your coding agents can trust
Tickets & workflowIn beta

Applications, ticket types and rules

Applications with a recorded tech stack, and ticket types that know who owns them and where they start.

  • Bug, change, feature and task, with per-type owner, starting stage and allowed stages
  • Custom stages per project, transition limits and completion rules
  • Triage with routing rules, snooze and duplicate resolution
  • Templates, labels with groups, saved board and list views, manual ordering
  • Documents on tickets: links, Markdown and text up to 200,000 characters
Read more about applications, ticket types and rules
PlanningIn beta

Cycle schedules, rollover, milestones

Recurring cycles for the workspace or each project, and rollover you can review or automate.

  • Schedules of 1-56 days with cooldowns, planned up to 12 cycles ahead
  • Reviewed rollover, or automatic for unfinished work, optionally including Triage
  • Milestones with owner, dates and progress; a roadmap timeline
  • Capacity and availability per person
Read more about cycle schedules, rollover, milestones
Clients & meetingsIn beta

Customers and meeting notes next to the work

A CRM linked to the applications you build, and meeting actions that become linked tickets.

  • Customers with contact, stage, notes and value, linked to projects
  • Granola, Fathom, Fireflies and tl;dv import with private previews; file upload and paste
  • Rule-based action extraction and reviewed, duplicate-free conversion
  • Backlinks from tickets to their meetings
Read more about customers and meeting notes next to the work
InsightsIn beta

Reports rebuilt from history, and a forecast

Twelve report sections calculated by replaying each ticket's history.

  • Cumulative flow and daily flow per custom stage
  • Lead and cycle time percentiles, time in stage, aging and blocked work
  • Monte Carlo delivery forecast: 2,000 runs, P50/P85/P95 and deadline odds
  • Saved, shared report configurations
Read more about reports rebuilt from history, and a forecast
SlackIn beta

Falrow in Slack, and a thread per ticket

The operational team asks in Slack and hears back in the same place.

  • @Falrow mentions and direct messages: create, find, take, move, comment and nudge
  • One thread per ticket that tags the requester and owner, with status, priority and comment updates
  • /falrow command with channel-to-project mapping and opt-in project updates
  • One Slack team serving several workspaces; admin-reviewed people matching by email
Read more about falrow in slack, and a thread per ticket
OperationsIn beta

Boards for the operational side

Tasks, payments, budgets and reminders on the same records as the build.

  • Private, team or workspace boards from four templates, with custom sections and layouts
  • Payments & budgets per application in USD, AED, EUR, GBP and SGD
  • Personal reminders in the app or in Slack, timezone and DST-safe
  • Signed change webhooks, and workload-aware owner suggestions for new tickets
  • Personal Home and Portfolio across every workspace you belong to
Read more about boards for the operational side
Sentry, API & adminIn beta

Errors in, an API out, and the tooling to run it

Sentry and REST on the same records, and the admin tooling around them.

  • Sentry: several organizations per workspace, routing by project and environment, one ticket per issue
  • Authenticated REST API at /api/v1
  • Owner, admin, member and viewer roles; invitations with optional email
  • Database backup, verify and restore commands
Read more about errors in, an api out, and the tooling to run it

Bring a real project, not a sandbox

We are opening workspaces to a few teams at a time, especially teams that build several applications and already code with Claude Code or Codex. Tell us what you build and we set it up with you.