The agents write the code.

The IDE for the agentic era.

You observe, judge and decide. Whaatcher puts the evidence in front of you, so you keep the quality while your agents keep the pace.

An agent's work runs without you. It stops in four places, and each one is a call only you can make.

  1. 1 · beforeSet the directionThe plan touches a function that keeps getting more tangled.
  2. 2 · duringStep inThe agent keeps returning to the same few lines.
  3. 3 · afterReview the workRead the hot spots first, with your team's comments on them.
  4. 4 · next timeFix the environmentAgents copy instead of reusing. Change the rule, not the line.
Moment 1 · before the work

Set the direction.

Whaatcher · feature/hindsight-exportRead Hindsight/HindsightAnalysis.swiftPlan ready. Add a session export: extend HindsightAnalysis.export with a new section. Proceed?›
What Whaatcher shows you · Function history
ƒ HindsightAnalysis.export144 lines · 11 versionscomplexity116▲ 35 in 30 days100SepOctnowcomplexityversions per month
The plan adds a section to the one function that has grown fastest this month. In the same file, 18 functions are already over 30.
What you decide
  • Split export into one function per section first
  • Proceed as planned
  • Put the export in its own type
Moment 2 · while it works

Step in, or let it run.

Whaatcher · feature/open-pr-redesign · ctx 79%Edit Views/Pulls/OpenPullsView.swift +12 −9Bash swift build error: cannot find 'PullRow' in scopeEdit Views/Pulls/OpenPullsView.swift +4 −11✻ Flummoxing… 4m 0s · still thinking›
What Whaatcher shows you · Where in each file the agent keeps editing
OpenPullsView.swift10 of next 31 commits
PullReviewPanel.swift6 of next 18
ClosedPullsView.swift6 of next 9
MergedPullsView.swift5 of next 17
Each bar runs from the top of the file to the end.edited onceedited again and againOne band of OpenPullsView keeps heating up while the context fills. The agent is circling, not progressing.
What you decide
  • Stop, and give that view its own task
  • Point it at the missing type
  • Let it run
Every agent has its own window. Double-click its tab on the terminal board and you are in its terminal.
Moment 3 · when the work comes back

Review where it mattered.

Whaatcher · feature/presentation-principles · PR #31Bash gh pr view 31 --commentsAddressed the F3 review in f435e3a. Ready for a second look.›
What Whaatcher shows you · Edit heat with your team's line comments on top
HindsightContextView.swiftthread 1
HindsightMomentView.swiftthread 1
110 } else {111 Text("Moment").font(.headline)112 }113 }114 Spacer()115 HelpMark(text: String(localized: "Anything marked with a dashed line…116 Button { if let moment { onCopy(moment.window) } } label: …117 .buttonStyle(.borderedProminent)118 .disabled(moment == nil)
ibare-dev1 · 21:14[F3] This screen no longer has a "fact" chip. Rewrite the help around the marks that are actually on it.ibare · 21:28Fixed in f435e3a. Dashed marks are what Whaatcher worked out. Only the process tree, lifetimes and samples are stated as observed.ibare-dev1 · 22:15[F3] Second review: resolved.
HindsightView.swiftthread 1
The hottest bands are where the agent struggled. When a teammate's comment lands on one, read it there first.
What you decide
  • Read the hot bands with comments, then approve
  • Ask for changes on line 115
  • Hold the merge for another review
After a merge, the PR keeps a diary for seven days: rework, reverts, reopened issues.
Moment 4 · before the next session

Fix the rule, not the line.

methii · apps/server · langchain.service.tsWrite LangChainService.suggestImages +38Added suggestImages, following the same pattern as the other generators.›
What Whaatcher shows you · Similar functions (structural similarity)
complexity 641 lines5 versions
async generateCode(params) { try { const response = await http.post( `${this.LANGCHAIN_SERVICE_URL}/…/code/generate`, { concept, programmingLanguage, language, … }, { headers: { 'x-user-id': params.userId }, timeout: 60000 } ); if (response.data.usage) saveLlmUsage(…); return response.data; } catch (error) { console.error(…); throw error; } }
generateMylang99
polishContent98
generateAnalogy98
suggestToc97
refineMaterial95
generateSummary95
generateMaterial…95
suggestImages92
Nine request functions in one file, 92 to 99 alike, and none of them ever changed together. Each new one was copied from the last. Tests and lint pass all of them.
What you decide
  • Extract one request helper, and write the rule down
  • Leave the copies, but stop the next one
  • Accept it as is
This is the decision that makes every future session better. No agent will make it for you.

Let the agents write. Keep the calls.

Download the betaNative macOS app · Free trial