Ref Tools

Ref's pitch is narrow and clear: it manages the reasoning layer above task trackers, not the tasks themselves. The homepage contrasts itself with Jira, Linear, and Notion directly, and the product surface backs that up — a multiplayer plan editor with Mermaid diagrams, images, and HTML prototypes, comments and approvals on the plan, and the ability to launch external agents such as Cursor or Devin and then review and merge code on your behalf. Strengths that show up in the scrape: plans live in the cloud rather than in one engineer's terminal, so persisted plans survive across sessions and machines; agents can be launched from the doc; Ref researches across every repository you connect so plans reflect multi-repo reality; and you can annotate a plan directly — circle a diagram, strike a paragraph — with Ref converting that into actionable feedback for teammates and agents. Enterprise plumbing is present too: SSO via Okta and Google Workspace, OAuth for MCP connections, SOC 2 compliance maintained with Vanta, plus a Trust Center and Privacy & Security pages. Weaknesses and open questions: the scrape gives no changelog, release notes, or developer docs this run, so we can't speak to release cadence, API surface, or how quickly agent-compatibility keeps up with new tools. Ref is explicit that it is a plan-and-context layer — if your team won't maintain a shared planning doc, the product has nothing to work with, and general project management still belongs in Linear or Asana. A solo developer with one agent gets coordination overhead rather than leverage. Where it fits: engineering leads scaling agent adoption across a team, especially anyone who has felt the pain of plans being hard to read and share, unclear direction, and agents making critical decisions with no visible reasoning. Where it doesn't: non-technical teams, lightweight task tracking, and groups that want orchestration entirely outside a document.