Mastra Factory Wants the Issue Tracker to Be the IDE
Mastra, the team that came out of Gatsby and went through Y Combinator, launched Mastra Factory as Product Hunt's number one yesterday with 405 upvotes. It is an open-source, agent-powered software delivery environment, which is a mouthful for a simple claim: the unit of work is an issue, and the thing that picks it up is not you.
What it actually bundles is persistent coding agents, repository workspaces, issue intake, planning, implementation, and pull request review, all in one web app. Read that list again and notice that the editor is not on it. Every step a human normally does between reading a ticket and merging a PR has been given to an agent that stays alive across the whole arc rather than dying at the end of a chat session. Their tagline is from issue to production, run by agents.
Persistence is the part that separates this from the last two years of demos. A chat-shaped agent forgets the plan when the window closes; a factory-shaped one keeps a workspace, a plan, and a review thread attached to the ticket. That is also why the fleet-control tools have been multiplying, from Herdr going multi-machine (https://clauday.com/article/f99c62c2-f0ff-486e-a796-8cd16b4d2e07) to Switch putting agents in Slack. The bet everyone is making at once is that you will soon be supervising several long-running agents, not typing to one.
The open question is review. If agents do intake, planning, implementation, and PR review, the only remaining human checkpoint is merge, and the honest version of this product is a very good queue of things to approve. Worth trying for exactly that reason: https://mastra.ai/
← Back to all articles
What it actually bundles is persistent coding agents, repository workspaces, issue intake, planning, implementation, and pull request review, all in one web app. Read that list again and notice that the editor is not on it. Every step a human normally does between reading a ticket and merging a PR has been given to an agent that stays alive across the whole arc rather than dying at the end of a chat session. Their tagline is from issue to production, run by agents.
Persistence is the part that separates this from the last two years of demos. A chat-shaped agent forgets the plan when the window closes; a factory-shaped one keeps a workspace, a plan, and a review thread attached to the ticket. That is also why the fleet-control tools have been multiplying, from Herdr going multi-machine (https://clauday.com/article/f99c62c2-f0ff-486e-a796-8cd16b4d2e07) to Switch putting agents in Slack. The bet everyone is making at once is that you will soon be supervising several long-running agents, not typing to one.
The open question is review. If agents do intake, planning, implementation, and PR review, the only remaining human checkpoint is merge, and the honest version of this product is a very good queue of things to approve. Worth trying for exactly that reason: https://mastra.ai/
Comments