What changed
By 2026 much of a billable dev's day is prompting, reviewing, and waiting on AI agents — time that legacy trackers (which assume typing/active-window work) don't capture, so hourly invoices look padded or undercount real effort (FACT: stated in the Ask HN pain thread).
Why now
HYPOTHESIS: AI-agent work is now the bulk of dev output. FACT (capability signal): the purely-local browser-extension-over-LLM-UI pattern just shipped (Claude Organizer), proving a solo dev can observe a Claude/chat session client-side with zero backend — the technical enabler for auto-attributing prompt/review/wait time.
Converging signals
A concrete PAIN complaint (Ask HN: no honest way to track AI-era dev time) meets a just-proven CAPABILITY (local extension observing an LLM chat UI). Two signals, weak convergence — this is a discretionary quick-win, not a forced-buyer mandate.
Customer pain
FACT (one thread): a freelancer says half their work is prompting/reviewing/waiting on agents and asks whether anyone tracks it honestly or is 'just eyeballing it.' Real but thin — a single Ask HN post, not a volume of complaints or evidence of people already paying to solve it.
Who pays
Independent devs/consultants and small dev agencies who bill hourly and need timesheets a client won't dispute. Discretionary prosumer buyer, pays by card.
Solved today
Toggl, Harvest, Clockify, RescueTime, Timely (AI auto-tracking), Memtime — plus most freelancers just eyeball round-number hours (FACT: the pain thread implies exactly this fallback).
Why current solutions are bad
HYPOTHESIS: existing trackers key off active-window/keystroke activity and score 'waiting on an agent' or 'reading a diff' as idle, so they under-count the exact AI-era work the founder wants to capture. Unproven that they can't be configured to approximate it.
Proposed product
Local-first extension that watches AI-agent/chat sessions + editor activity, classifies time into prompt/review/wait buckets, attributes it to a client tag, and exports a clean hours report + CSV invoice line-items. No backend, privacy as the pitch.
MVP version
Chrome/desktop extension: detect active client (manual tag or repo/domain heuristic), timestamp chat-session and editor focus events locally, roll up into a daily hours table with prompt/review/wait split, one-click CSV export. Buildable in 1-3 weeks solo on free tooling.
30-day build
Ship MVP against Claude.ai + VS Code/Cursor; dogfood on own consulting hours; post as a Show HN / to the same Ask HN thread and r/freelance, r/cscareerquestions, indie hacker channels; instrument how buckets map to what users actually invoice.
60-day build
Add Cursor/Windsurf/ChatGPT session capture, editable time entries, and 'client-defensible' PDF/CSV export; add a paid tier gate; collect willingness-to-pay signal and 3-5 paying testimonials.
90-day revenue plan
Convert free users to $12/mo (or a one-time $29-39 lifetime for the local-only privacy crowd who distrust subscriptions); target a few hundred seats via developer-community distribution, not ads.
Distribution path
Chrome Web Store + direct download, launch in the exact HN/Reddit/IndieHackers threads where the pain lives, content on 'billing honestly for AI-agent work,' word of mouth in freelance dev circles. Demonstrated-value channel, which fits the founder.
Pricing hypothesis
$12/mo per seat as proposed; test a $29-39 one-time local-only license for privacy-minded solos who resent SaaS subscriptions.
Technical difficulty
Low-moderate. The local-observation pattern is proven; the hard part is accurate client attribution and turning raw activity into hours a client accepts — a heuristics/UX problem, not infra.
Legal / regulatory risk
Low. No PII leaves the machine if it stays local. Watch: capturing prompt CONTENT could expose client-confidential material — keep it metadata/timing only and say so loudly.
Platform dependency
Moderate. Depends on Chrome Web Store review and on scraping/observing third-party LLM UI DOMs that can change without notice, breaking capture. No government platform, so no deplatform-by-owner of the workflow itself.
Founder fit
Moderate. It's a browser extension / micro-SaaS he likes and can prototype fast, but it carries NONE of his strongest edge — no government portal, no forced filer, no public-money flow. It's a discretionary tool in a saturated category.
Breakout potential
Limited-to-moderate. Could expand into full AI-work analytics or agency-wide 'proof of AI effort' reporting, but time tracking is a crowded, low-loyalty category with strong incumbents who can bolt on an 'AI time' feature.
Final recommendation
WEAK PASS / build only as a cheap 1-2 week experiment. The technical wedge is real and cheap, but this is a discretionary painkiller in a saturated category with one thread of demand evidence and no founder edge. If built, validate willingness-to-pay in the launch thread BEFORE polishing — and prioritize the founder's public-money/forced-filer pipeline over this.
Next action
Reply in the Ask HN thread (id 48890963) and post a 1-question landing page ('would you pay $12/mo for honest AI-agent time tracking?') to measure real intent before writing capture code; kill if the thread's own participants say they'll keep eyeballing hours.