Structured forms make bad thinking. You start editing the task to match the schema instead of saying what is actually blocked.
WAH's capture is the opposite: one textarea, one messy dump — “Launch next week. Waiting on legal, still need customer feedback, fix the billing bug before Friday.” No tags. No estimate. No priority picklist.
What capture does
parseCapture() in lib/capture.ts takes that dump and splits on newlines, commas, semicolons, and “and”. It trims bullets, drops fragments under 7 characters, caps at six items, and assigns each slice a minutes/impact/why triple via small regex hints.
Example dump with three slices becomes: Fix the billing bug — 45 min · High impact · Blocks launch · No one else owns this · Fits today's available time. Still need customer feedback — 20 min · You still own this · Unblocks the brief · A complete action. Launch next week — 35 min · Critical path · Deadline is near · Everything else hangs off this.
Why natural language first
You keep the source of truth — your words — while WAH extracts what you control and what is already in motion. If the extraction is wrong, you do not re-tag the whole list. You rewrite the sentence. The next move updates in under a second and the Why this? under the card tells you what changed.
That is thinking, not data entry. And it is distributable: record a 20-second screen capture of one dump → one next move. No onboarding flow to fake.
Hardcore boundary
We do not pretend capture is magic. Hints are small and explicit (bill|checkout|auth|bug, onboard, customer|interview, launch|friday). Real workspace ranking will add calendar, GitHub, and Slack signals — with written Security and Privacy that match the stack before we claim encryption or isolation. Preview is local session (product-session.ts), not cloud training.
Capture the thought. WAH finds the move. If the form makes you think harder than the work, the form is the problem.
Dump your plate now →