Bring your coding agents into every step of building software. Thraft keeps every decision, and why, as you go.
Todaythe whole loop, free, on your MacWith Workspaceyour team, by invite
The whole loop runs on one Mac: plan, audit, tickets, build notes, completion, and memory. Scroll, and the window follows one change through it. Finance finds refunds issued twice by hand every Friday, and you want that to stop.
You say what you want in a line, and your agent drafts the plan from it and from what the project already knows. You answer its open question by picking one of the answers it drew, and send your notes as one batch. The next revision answers every note.
Run the audit until it holds. Each round reads the plan against the code, finds what a builder would trip on, and revises it. The run ends on a report, least confident first, and you mark the plan ready.
The work order drafts one ticket for each slice of the plan, and each draft names the blocks it covers. You settle the drafts and push them to your tracker, or keep them on Thraft's own board.
Your agent builds ticket by ticket. When the code disagrees with the plan, it leaves a build note on the block, with a proposed edit and how sure it is. You accept it, and the plan changes on purpose, in the open.
When every ticket is done, you complete the plan and it freezes. A conformance pass then checks each criterion against what was built, and marks which hold and what proved it.
Completed plans feed the Memory: every decision, by domain, with where it came from. When a later plan reverses one, the Memory shows both, and marks the change until you have read it.
Write the target and what done looks like. What nobody can answer yet stays as questions in fog. Each answer becomes an item, each item drafts a plan, and the goal's progress is those plans, live, not a status someone wrote.
Every turn runs on this Mac, on your own sign-in and the models you already pay for. The agents you run reach the plan through Thraft's MCP: they move tickets, leave build notes, and close bugs. Thraft never runs a turn on a server, and never meters AI.
A workspace brings the people around you into the same loop. Your team's work speaks for itself upward, and you stop writing a status nobody can verify. Workspaces open by invite.
Join the waitlistMarta runs Finance. She sends her ask from the agent she already uses, through the MCP, and it lands in one pile for the whole workspace, with who sent it and why now. Lena, the product manager, accepts it into a project.
Lena, Inês, Rui, and Sam open the same plan, each on their own Mac. A role picks where you land: the product manager on the open question, the lead on the tickets, the engineer on the build note, QA on what holds. It never hides anything.
Marta follows the plan as a guest. When it completes, her Inbox says what she gets and links to the decision behind each part of it. An ask that is parked or declined says why, and what would change the answer.
The whole loop is free on one Mac, today. Workspaces open by invite, so join the waitlist and say how big your team is.
Know why you built it, not just how.
0041Refund reasonsopen2 settled · 3 open20m ago0037Flag double refundsticketed3 done · 1 in review5h ago0031Refund totals by dayticketed4 done · 2 in progress1d ago0036Export to the ledgersettled9 settled · 2 findings2d agoBO-312· your agentlow confidenceF2· round 1standsscripts/refunds.py sums by order. So today a partial refund and a full one read as one order refunded twice.D1Hear about refunds from Stripe's webhookmediumround 1R3A missed event is retried, not droppedhighround 113 findings · revised 2 blocks21 finding · answered with no change3nothing that blocks · the audit holdsI2Refund totals by day0031building · 4 of 6I3Flag double refunds0037building · 4 of 5I4Reconcile by charge·to draft · from Q3DraftI1Refund reasons0034completedRFD6 decisions1 reversed since you readfrom 0037, 0052, 0061D2Billing5h agoField kit1d agobackoffice4d agowarehouse1w ago