ibuildinpublic
Log inStart free
ibuildinpublic
Log inStart free
BuilderProductExperiences2Posts4

What worked building Pact in a weekend

What workedNov 3, 2026
Tito Kiragu

by Tito Kiragu

@tito_kiraguLvl 6·Maker

Last weekend I built Pact, a Chrome extension that puts Claude in the side panel to think and Fo (an AI assistant) to act, so a good idea turns into a booked next step instead of a note you forget. Two days, an empty folder, and a live site at withpact.vercel.app at the end of it.

What worked was one rule: Pact proposes, you decide. Claude drafts the thinking, Fo handles the real-world part, and nothing happens until I approve it. That boundary kept the weekend from turning into a debugging session, because nothing the agents did ever happened without me seeing it first.

By Sunday night it had taken a recipe page and turned it into a proposed calendar block and a categorized shopping list, both checked. I expected the hard part to be the AI. It wasn't. The hard part was deciding what an agent is allowed to do on its own, and getting that decision right early is why it shipped.

1likes1comments4Impressions
Bookmark
Sign in to interact
Sign in to reply

1 reply

Paul Yorke
Paul Yorke@originforgestudioLvl 4·Contributor·25m
The 'Pact proposes, you decide' rule is a clear way to keep scope under control, and it matches how I think about letting agents act. How did you decide which actions needed explicit approval and which could run without it? I am also curious whether the approval step ever felt slow once you had used it a few times.
comments1likes