# Brief 11a — Startup ideas grounded in pains created by AI agents (Jul–Sep 2026) Prepared 2026-09-07 for Gocha (solo founder, Tbilisi, usectl) + Claude (agent). Excludes painboard, threadbus, runbyagent. Method note: HN threads were pulled through the Algolia HN API (dated to the second); GitHub issues through the GitHub search API and issue pages. reddit.com is blocked from this environment, so no Reddit post could be verified and none is cited; X posts could not be fetched (robots.txt) except where a search snippet carried the text. Every URL below was opened and checked unless marked "not found". Ranking = first-dollar speed × evidence strength. | # | Idea | Type | First dollar | Evidence | |---|------|------|--------------|----------| | 1 | Token Autopsy — "where did my $X go, and here is the patch" | Agent does the work (outcome) | Same week, ship in 1 day | Strong: $6k/week issue, weekly-limit threads, OpenClaw zero-usage loops | | 2 | Vetted — verdict-and-watch service for skills and MCP servers you are about to install | Agent does the work (outcome) | 1–2 weeks | Strong: scanner false positives, skill that passed every scanner reached 26k users | | 3 | Claim — "who is editing this file" registry for parallel agent sessions on one repo | Software (hook + tiny service) | 2–3 weeks | Strong, very fresh: detailed Aug 22 issue with measured incidents, 3 HN threads in 2 weeks | | 4 | One Policy — one `agent-policy.yaml` compiled into Claude Code / Cursor / Codex / OpenClaw enforcement | Software | 3–4 weeks | Medium-strong: explicit "I need a separate one per model" complaint | | 5 | Blackbox — pre-compaction action ledger so an agent never denies what it did | Software | 4+ weeks, crowded | Strong pain, crowded market | --- ## 1. Token Autopsy (rank 1) **Pain in one sentence:** People on Max plans and API keys are losing hundreds to thousands of dollars a week to agent loops, subagent fan-out and context reloads, and the dashboards they have tell them *that* it happened, not *why* or *what to change*. **Evidence (three, dated):** 1. anthropics/claude-code #81359, opened 2026-07-26: a Max user documents 59 sessions in 7 days, ~6.9B tokens, estimated ~$6,069 (~$867/day, peak $2,179), caused by session-restart storms and 30–74-hour tool loops; asks for a credit and an investigation; closed "not planned / stale". https://github.com/anthropics/claude-code/issues/81359 2. Ask HN "Claude Code randomly burning through 10% of the weekly limit?", 2026-08-24: on "the biggest plan", "9% usage within 10 minutes" after a weekly reset, asking if others see the same. https://news.ycombinator.com/item?id=49415754 3. openclaw/openclaw #108056, opened 2026-07-15: one request ("check if OpenClaw needs updating") produced 45 automatic turns and 1,498 tool calls (the same 30 commands repeated 44 times), estimated 500K+ tokens, while all `usage` fields read zero, "making it impossible for users to detect runaway costs before billing". https://github.com/openclaw/openclaw/issues/108056 Supporting: #74803 (2026-07-06, consumption bar 13%→90% "while doing nothing different"), https://github.com/anthropics/claude-code/issues/74803; #56068 (2026-05-04, 4 forked subagents each inheriting ~120K parent context, 425K tokens/$10 in one session, no warning), https://github.com/anthropics/claude-code/issues/56068; #68619 (June 2026, subagent recursion 50+ levels, 1.2M–4M tokens burned with zero output, "50% of weekly budget"), https://github.com/anthropics/claude-code/issues/68619; openclaw #110336 (2026-07-18, 236-turn loop, "15+ million input tokens merely repeating prior conversation"), https://github.com/openclaw/openclaw/issues/110336; a Japanese author counted 60,000 of their own log lines on 2026-08-31 to find what actually consumes the weekly limit (cache rebuilds past ~300 turns), https://note.com/ai_hack_dx/n/n9b9307aa13a8?hl=en. **Who has it:** Solo developers and 2–5 person teams on Claude Max / Codex Pro / OpenClaw with their own Anthropic or OpenAI key, running 3+ sessions or cron agents, who got the bill or the "limit reached" banner and cannot explain it. **Smallest product that removes it:** A paid *autopsy*, not a dashboard. Customer runs one command that tars `~/.claude/projects/**/*.jsonl` (or OpenClaw `sessions/`), strips file contents, and uploads it. Within 24 hours they get: (a) a one-page "where the money went" with the top 5 sessions/subagents/MCP servers/loops by cost; (b) a concrete patch — `settings.json` changes (disable unused MCP servers, `CLAUDE_CODE_FORK_SUBAGENT`, compaction thresholds, PreToolUse loop-breaker hook, model tiering for cron), plus an OpenClaw heartbeat/cron rewrite where relevant; (c) an estimated monthly saving. Optional monthly re-run. **What exists and why it does not solve it:** - ccusage (https://github.com/ccusage/ccusage) and a dozen local dashboards (https://github.com/chengzuopeng/ccgauge, https://github.com/ocodista/claude-usage, https://github.com/cero-t/ccc-usage-dashboard): totals per day/project; no cause, no fix. - claude-token-analyzer (https://github.com/li195111/claude-token-analyzer, 11 stars, last release 2026-04-14): six anomaly types, "generates diagnostic reports and analysis only — it does not produce automated fixes". - token-trace-viewer (HN 2026-07-29, https://news.ycombinator.com/item?id=49093353): per-subagent cost from OpenInference spans; requires instrumented LangGraph-style agents, not Claude Code/OpenClaw logs; author says LangSmith/Langfuse/Helicone "none provide per-run granularity or detect repeated context reuse". - AgentObs hook (HN 2026-08-30, https://news.ycombinator.com/item?id=49497992): blocks before the limit; commenter Kamlesh502: "With several parallel sessions the hard part is picking which one to block". - AgentWatch / AgentBudget proxies (https://news.ycombinator.com/item?id=48706317, https://news.ycombinator.com/item?id=47418574): budget caps for API apps, not for Claude Code/OpenClaw subscription users, and they stop spend rather than explain it. - Anthropic's own `/cost` and usage bar: no attribution to session/subagent/MCP, and #66180 shows the bar and the actual limit disagree (https://github.com/anthropics/claude-code/issues/66180). **Price and who pays:** $49 one-off autopsy (first 10 at $29), $19/month for a monthly re-run with a delta ("you saved $X vs last month"). Paid by the individual whose card or weekly limit got hit; teams $149/month for up to 5 seats. **How an agent runs it day to day:** Agent's job: watch inbox/form for uploads, run the parser (a script over jsonl: tokens per session, per subagent, per tool, per MCP server, cache-hit ratio, restart gaps, repeated tool sequences), draft the report and the patch, run a safety check that the patch only touches settings/hooks, send it, log the episode to the public show. Founder's job: 10-minute review of each report before it goes out for the first 20 customers, handle refunds, ship the parser fixes the agent files as issues. **Build estimate:** 1 founder-day (parser over Claude Code jsonl + report template + Stripe payment link + upload form on usectl). OpenClaw log support +1 day. Codex logs +1 day. **First ten customers and where:** (1) am1devs, author of #81359; (2) terabytest, author of HN 49415754; (3) Kaoz-K, author of #74803; (4) diegoacanales, author of #56068; (5) the openclaw #108056 reporter; (6) klars-ai (AgentObs) — offer a partnership, their users are the buyers; (7–10) reply to every "burned my limit" post in the next two weeks on the Claude Code issue tracker `area:cost` label (https://github.com/anthropics/claude-code/issues?q=label%3Aarea%3Acost) and in HN Ask threads, and post the first anonymized autopsy as an episode on X. **Kill signal:** 30 personalized offers (free first autopsy) to authors of cost issues/threads produce fewer than 5 uploads in 14 days, or fewer than 2 of the first 10 free autopsies convert to the $19 re-run. **Biggest risk:** Anthropic ships attribution in `/cost` or the usage UI (they already label issues `area:cost` and closed #81359 as not planned, which suggests it is not imminent). Second risk: people will not upload session logs — mitigate with a local-only mode that runs the parser on their machine and uploads only the aggregate. --- ## 2. Vetted — skill and MCP server verdict-and-watch service (rank 2) **Pain in one sentence:** Anyone installing an OpenClaw skill or an MCP server cannot tell whether it is safe, the free scanners disagree with each other and block legitimate skills, and nobody re-checks after the skill updates. **Evidence (three, dated):** 1. openclaw/openclaw #105942, opened 2026-07-13: a legitimate ASIC-mining business had its own `miner-testing` skill quarantined by the Skill Workshop `crypto-mining` rule; "Quarantine is effectively a workflow dead end", "Operators are pushed toward manual edits or local monkey patches, which are less auditable". Open, P2. https://github.com/openclaw/openclaw/issues/105942 2. "Fake AI Agent Skill Slipped Past Every Scanner", HN 2026-07-04, linking CSO Online: a malicious skill passed security checks and reached ~26,000 users. https://news.ycombinator.com/item?id=48785425 (article: https://www.csoonline.com/article/4188840/how-a-malicious-ai-agent-skill-passed-security-checks-and-reached-26000-users.html) 3. Ask HN "Who is using MCP in production?", 2026-09-03, 191 points / 196 comments: "How is security handled in a situation like this?"; "poorly implemented MCP servers" hand service credentials to the model; "my team is producing MCP servers for other teams, and I find it a bit maddening". https://news.ycombinator.com/item?id=49548600 Supporting: "Security scanners for AI agent skills agree no better than chance", HN 2026-06-10, https://news.ycombinator.com/item?id=48477095; Snyk's agent-scan executed MCP server commands from untrusted `mcp.json` during a scan (2026-04-20), https://dev.to/pachilo/execute-first-ask-never-a-vulnerability-in-snyk-agent-scan-4plc; the February ClawHub incident (341 malicious skills, https://thehackernews.com/2026/02/researchers-find-341-malicious-clawhub.html; Unit42 analysis https://unit42.paloaltonetworks.com/openclaw-ai-supply-chain-risk/); OpenClaw's VirusTotal gate produces "common" false positives and the documented fix is to raise the threshold or disable scanning, https://dev.to/zacvibecodez/openclaw-skills-blocked-why-skills-wont-install-and-4dan; feature requests #11014 (2026-02-07) and #47080 (2026-03-15) for a built-in scanning pipeline, both closed, https://github.com/openclaw/openclaw/issues/11014, https://github.com/openclaw/openclaw/issues/47080. **Who has it:** Two specific people: (a) the IT/security owner at a 10–200 person company where employees run OpenClaw or Claude Code with MCP servers and someone has to say "yes/no" before install; (b) an OpenClaw operator running agents for clients (agencies, "remote OpenClaw" hosts) who gets blamed if a skill steals keys. **Smallest product that removes it:** A form: paste a ClawHub skill slug, a GitHub URL, or upload your `mcp.json`/skills list. Within 24 hours you get a plain-language verdict per item (Safe / Safe-with-config / Do not install), the reasons (network egress, credential reads, obfuscation, prompt-injection strings, maintainer history, diff vs previous version), and a recommended allowlist entry. Paid watch: the agent re-scans every new version and emails a diff-based alert. The agent runs Cisco skill-scanner, openclaw-skillscan and static checks, then actually reads the code, which is what the scanners cannot agree on. **What exists and why it does not solve it:** - cisco-ai-defense/skill-scanner (https://github.com/cisco-ai-defense/skill-scanner, 2.2k stars, last release 2026-04-30): local CLI, skills only (no MCP servers), "no hosted verdict service or continuous monitoring"; "a scan that returns no findings does not guarantee that a skill is free of all threats". - snyk/agent-scan (https://github.com/snyk/agent-scan): scans MCP servers by running them; had the execute-first vulnerability above; enterprise-oriented. - openclaw-skillscan, security-skill-scanner, ClawGuard (https://github.com/Jibberdaffle12/openclaw-skillscan, https://github.com/anikrahman0/security-skill-scanner): pattern matchers; scanners "agree no better than chance". - OpenClaw built-in Skill Workshop scanner + VirusTotal: blocks legit skills, no allowlist workflow (#105942). None gives a decision a non-security person can act on, and none watches for the update that turns a safe skill malicious. **Price and who pays:** $29 per verdict (bundle of 10 for $199); $49/month watchlist for up to 30 skills/servers with update alerts; $299/month for a company allowlist maintained by the agent. Paid by the IT/security owner or the OpenClaw hosting operator, not the hobbyist. **How an agent runs it day to day:** Agent's job: poll submissions, clone, run the three scanners, read every file, fetch maintainer/publish history, write the verdict against a fixed rubric, publish a public verdict page per skill (SEO and the show), run the watch cron (diff new versions, alert). Founder's job: sign off on every "Do not install" verdict for the first 50 (false accusations are the liability), write the rubric, handle disputes from skill authors. **Build estimate:** 2 founder-days for v1 (submission form, scanner runners in a usectl job, rubric prompt, public verdict page, Stripe). Watch cron +1 day. **First ten customers and where:** (1) the #105942 reporter (the mining company) — they need an allowlist workflow now; (2) Remote OpenClaw / hosting operators who wrote the "skills blocked" guides (https://www.remoteopenclaw.com/blog/openclaw-skills-blocked-fix); (3–5) teams in the "Who is using MCP in production?" thread who said they produce MCP servers for other teams; (6) the Big Hat Group "OpenClaw Weekly" audience (https://www.bighatgroup.com/blog/openclaw-weekly-2026-08-31/) — offer a weekly "verdicts" column; (7–8) authors of #11014 and #47080 who built scanners (ClawGuard) — partner or convert; (9–10) companies listed in joylarkin/openclaw-security-news advisories (https://github.com/joylarkin/openclaw-security-news). **Kill signal:** 25 free verdicts offered publicly (one per day as episodes) generate fewer than 3 paid verdicts or 1 watchlist in 30 days; or OpenClaw ships an allowlist/verdict marketplace natively. **Biggest risk:** Liability and reputation — a "Safe" verdict on a skill that later steals keys. Mitigate with explicit scope ("at version X, on date Y"), no guarantees, and watch alerts as the core paid value. --- ## 3. Claim — "who is editing this file" for parallel agent sessions (rank 3) **Pain in one sentence:** Developers now run 3–15 Claude Code / Codex sessions on one machine, and sessions commit each other's uncommitted edits, spiral on stale files, and hang when told to coordinate, because nothing tells a session that another session owns a file. **Evidence (three, dated):** 1. anthropics/claude-code #88862, opened 2026-08-22: three measured incidents (2026-05-12, 08-08, 08-11) where one session's `git commit` swept another session's staged edits; on the hottest file 55% of commits bundled foreign work; author built an advisory `session-claims.js` and an inbox-merge pattern (compliance 88%) and asks Anthropic for "Session B has uncommitted edits to 2 files in your index" warnings and session awareness. https://github.com/anthropics/claude-code/issues/88862 2. Ask HN "What are your biggest problems and fixes with multisession engineering?", 2026-08-30: author cannot pause agents at checkpoints; ebcode "I don't let them write or read anything w/out my approval". https://news.ycombinator.com/item?id=49503285 3. Ask HN "How many of you juggle multiple agent sessions at the same time?", 2026-08-27: kasey_junk "8 is about my limit but I never have less than 4"; atsaloli runs 15–30 tmux windows. https://news.ycombinator.com/item?id=49469723 Supporting: #86012 (2026-08-12) — Claude Code Desktop's own cross-session `send_message` leaves the recipient wedged 16–20 minutes, "forcing users to fall back to manually opening windows and pasting task text", https://github.com/anthropics/claude-code/issues/86012; "I Ran Seven Claude Code Sessions on One Repo. Three Spiraled" (2026-06-06) — worktrees "isolate less than you think", needed PreToolUse write guards and a serialized merge gate, https://readysolutions.ai/blog/2026-06-06-parallel-claude-code-sessions-one-repo/; Ask HN "How do you use multiple sessions for software engineering?" 2026-08-28, https://news.ycombinator.com/item?id=49479775. **Who has it:** The senior engineer or solo founder running 4+ agent sessions against one repository on one workstation (not the worktree-per-task person — the person who deliberately shares a tree because the sessions edit the same planning/config files). **Smallest product that removes it:** `claim` — a 200-line local daemon plus a PreToolUse/PostToolUse hook for Claude Code (and Codex/Cursor hooks). On Edit/Write the hook registers `session → path`; on `git add/commit` the hook blocks or warns if the index contains paths claimed by another live session; `claim who ` and `claim list` show contention; claims expire with the session. Optional shared mode over threadbus for sessions on different machines. Ship the hook first, the UI never. **What exists and why it does not solve it:** - Git worktrees (https://code.claude.com/docs/en/worktrees): isolation, not coordination; fails for shared files, and the June 6 article shows spirals persist. - gastown (https://github.com/steveyegge/gastown): a full multi-agent workspace manager; heavy, opinionated, not a drop-in hook for an existing workflow. - claude-squad / crew / polydev (https://github.com/pikehouse/crew, https://github.com/shikihane/polydev): session launchers and tmux managers; no file ownership. - Claude Code's cross-session messaging (#86012): unreliable and Desktop-only. - The #88862 author's own scripts: proven to work, unpublished as a product, advisory only because the harness ignores it — the hook layer is exactly what is missing. **Price and who pays:** Free single-user OSS hook (distribution); $9/month per developer for shared claims across machines + a "contested files" feed; $79/month per team. Paid by the developer's company card. **How an agent runs it day to day:** Agent's job: build and maintain the hook for each harness's changing hook API, triage issues, write the weekly "contention report" for paid users, answer support in the repo. Founder's job: install it on his own multi-session workflow first and make the show about it; approve releases. **Build estimate:** 2 founder-days for the Claude Code hook + daemon; Codex/Cursor hooks +1 day each; shared mode over threadbus +2 days. **First ten customers and where:** (1) the author of #88862 (they already wrote the prototype and asked for exactly this); (2) the four commenters in the 2026-08-27 and 08-30 HN threads (kasey_junk, atsaloli, ebcode, top_rooster); (3) WarmBed, reporter of #86012; (4) the readysolutions.ai author; (5–10) people replying to the `area:agents` and "multiple sessions" issues on the Claude Code tracker and posting worktree guides (claudefa.st, codewithmukesh) — offer the hook as the "other half of the fix". **Kill signal:** Fewer than 100 installs in 30 days after the OSS hook is posted to the #88862 thread and HN, or Anthropic ships session awareness in Claude Code (watch #88862 for a maintainer response). **Biggest risk:** Anthropic solves it in-harness (they own the hook points). Also: overlaps with threadbus — position Claim as a threadbus consumer, not a competitor. --- ## 4. One Policy — a single agent policy compiled into every harness (rank 4) **Pain in one sentence:** Enforcing rules like "never handwrite migrations", "no `rm -rf`", "no network from shell" requires a different, hand-written config per tool — Claude Code hooks, Cursor rules, Codex config, OpenClaw exec policy — and rule text in AGENTS.md decays as sessions get long. **Evidence (three, dated):** 1. Ask HN "How do you guys stop coding agents from acting out of line?", 2026-08-27: vivekyyy — "it seems kinda provider dependent, so I'm gonna need to do this differently for Claude, Cursor, and Codex. It will also require a custom pre-tool use plugin ... which is pretty annoying when I need a separate one per model". https://news.ycombinator.com/item?id=49466458 2. Ask HN "How do you gate an autonomous coding agent's shell access?", 2026-09-03: containers are not enough because agents "can still exfiltrate secrets or perform irreversible actions undetected"; commenter Verdverm is building a "tool calling policy" guardrail. https://news.ycombinator.com/item?id=49556858 3. Ask HN "Why still no unified standard file to describe all skills/mcps for repo?", 2026-08-29: opwizardx — "have an agents.yaml in your repo and know it will be sourced by a harness you use", like docker-compose. https://news.ycombinator.com/item?id=49489006 Supporting: Ask HN "How are teams sharing AI/agent setups internally?" 2026-08-17 — shared skills/MCPs/context in GitHub, non-technical teammates cannot keep it in sync, https://news.ycombinator.com/item?id=49330900; #88862's finding that "a tool can only refuse calls it receives... the harness is the only layer that sees writes"; OneCLI (HN 2026-07-23, 110 points) shows appetite for policy at the proxy layer, https://news.ycombinator.com/item?id=49023427. **Who has it:** The tech lead at a 5–50 engineer company who has already picked two or three harnesses (Claude Code + Cursor + Codex is common) and is being asked "how do we make sure the agent never does X" by someone with a title. **Smallest product that removes it:** `agent-policy.yaml` (deny/allow commands, path write rules, network rules, required-tool rules like "migrations via CLI only") + a compiler that emits `.claude/settings.json` permissions and PreToolUse hook scripts, Cursor hooks, Codex config, and an OpenClaw exec-approval policy, with a `policy test` command that replays sample tool calls against every target and prints pass/fail. Runs in CI so drift is caught. **What exists and why it does not solve it:** - rulesync / ai-rules-sync / agent_sync / agent-rules-sync (https://github.com/jpcaparas/rulesync, https://github.com/PanisHandsome/ai-rules-sync, https://github.com/yelmuratoff/agent_sync, https://github.com/dhruv-anand-aintech/agent-rules-sync): they sync *instruction text* (CLAUDE.md, .cursorrules) and settings files; agent-rules-sync explicitly "does not handle command deny rules or enforcement policies". Instructions decay; enforcement does not. - OneCLI / credential proxies: enforce *secrets*, not behavior. - Each harness's native hooks (https://docs.anthropic.com/en/docs/claude-code/hooks): the thing that has to be written N times. **Price and who pays:** Free CLI for one harness; $12/month per developer for multi-harness compile + CI check; $99/month per team with a hosted policy registry. Paid by engineering managers. **How an agent runs it day to day:** Agent's job: track each harness's hook/config schema changes (they change monthly) and update the compiler, maintain a library of policy recipes ("no handwritten migrations", "prod DB read-only"), run the CI check service, answer issues. Founder's job: design the YAML schema (the one thing that must not churn), review compiler changes for each harness, handle enterprise questions. **Build estimate:** 4–6 founder-days: schema + Claude Code target (2), Cursor and Codex targets (2), test-replay command and CI action (1–2). **First ten customers and where:** (1) vivekyyy (HN 49466458), (2) alanfuNZ and Verdverm (HN 49556858), (3) opwizardx (HN 49489006), (4) TBraunz (HN 49330900), (5–10) teams that starred agent-rules-sync/rulesync and opened issues asking for hooks/permissions sync; the "Chain-aware (A2A) authorization using OPA" poster (HN 49488952, 2026-08-29) as a design partner. **Kill signal:** If an `agents.yaml`-style standard with enforcement semantics is adopted by two of the three harness vendors within 60 days, or fewer than 10 teams run the free single-harness CLI in 30 days. **Biggest risk:** Vendor standardization (the Aug 29 thread asks for exactly the standard that would make this a feature). Second risk: the founder is dragged into per-harness maintenance forever — the agent must own that. --- ## 5. Blackbox — pre-compaction action ledger (rank 5) **Pain in one sentence:** After compaction or a restart the agent forgets what it itself did minutes ago, denies it, and re-does or contradicts the work, across Claude Code, OpenClaw and Cursor. **Evidence (three, dated):** 1. anthropics/claude-code #75759, opened 2026-07-08: after mid-session compaction the agent "denies performing actions it actually completed", could not locate backup files it had just created, user had to paste conversation history as proof. https://github.com/anthropics/claude-code/issues/75759 2. anthropics/claude-code #79217, opened 2026-07-19: auto-memory MEMORY.md index size limit truncates what the agent can remember; asks to make it configurable (11 comments). https://github.com/anthropics/claude-code/issues/79217 3. Ask HN "How do you keep AI coding agents in sync with a changing Figma file?", 2026-09-07: "the design changes and the agent has no memory of what changed or why". https://news.ycombinator.com/item?id=49595961 Supporting: Ask HN "How do you keep track of all your codex/Claude sessions?" 2026-08-17, https://news.ycombinator.com/item?id=49325946; openclaw #5429 (2026-01-31, "Lost 2 days of agent context to silent compaction — no warning, no save, no recovery", closed not planned), https://github.com/openclaw/openclaw/issues/5429; openclaw #50096 (2026-03-19, long-term memory, closed not planned), https://github.com/openclaw/openclaw/issues/50096; #43733 PreCompact hook request, https://github.com/anthropics/claude-code/issues/43733; #66144 (2026-06-08, auto-compact fails and Claude Code stops itself), https://github.com/anthropics/claude-code/issues/66144. **Who has it:** Anyone running multi-hour sessions, especially OpenClaw operators with always-on agents and Claude Code users on Bedrock/enterprise where sessions run for days. **Smallest product that removes it:** Not "memory". A PreCompact/PostToolUse hook that appends an append-only ledger per project (`what I changed, where, why, at what time, which command`), and a post-compact hook that re-injects the last N entries plus a one-line summary so the agent can answer "where did you save the files" from the ledger, not from context. A `blackbox find "backup"` command across all sessions and harnesses. **What exists and why it does not solve it:** - Anthropic auto-memory (https://www.anthropic.com/news/memory) and MEMORY.md: memory of preferences/facts, size-capped (#79217), not an action log. - claude-historian and dozens of memory MCPs (https://glama.ai/mcp/servers/@Vvkmnn/claude-historian/blob/5523c7a4febebd9cb3e54990eb6bc693ee206aa5/COMPARISON.md): search past transcripts; none is written at compaction time, none is cross-harness. - re_gent "Git for AI Agents" (HN, 129 points, https://news.ycombinator.com/item?id=48063548): tracks agent activity for "why did the agent do that", Claude Code only, positions as version control rather than context re-injection. - OpenClaw memory flush requests (#8185, #41216, #45608): closed or open, unshipped. **Price and who pays:** $8/month per developer; free for one project. Paid by individuals; weak willingness to pay because "memory" is perceived as the vendor's job. **How an agent runs it day to day:** Agent's job: maintain hooks for each harness, ship the ledger format, run the hosted search for paid users, and — the show angle — write its own ledger publicly. Founder's job: keep the ledger format stable and small (this must never bloat context, or it recreates pain #1). **Build estimate:** 3 founder-days (Claude Code hooks + ledger + re-inject; OpenClaw plugin +2). **First ten customers and where:** authors of #75759, #79217, #43733, #5429, #50096; the Figma-sync HN poster; the sessions-tracking HN poster (lasky); the "Cool little hack using Claude Code watching files with tail -f" poster (HN 49499700, 2026-08-30) who is already hand-rolling coordination via files. **Kill signal:** Anthropic ships PreCompact hooks with state re-injection (watch #43733), or <50 installs in 30 days. **Biggest risk:** Crowded and vendor-owned; every harness vendor is shipping memory features, and users conflate "memory" with this even though it is a different thing. --- ## Notes on what was looked for and not found - Reddit (r/ClaudeAI, r/cursor) posts: reddit.com is blocked from this environment; no Reddit post could be verified, so none is cited. - X posts: the one X post surfaced by search (Chrys Bader on OpenClaw cron jobs burning tokens, https://x.com/chrysb/status/2032562442937815510) could not be fetched (robots.txt); its date is unverified, so it is not used as evidence. - "Is there an MCP server for X" posts from Jul–Sep 2026: searches returned only directories and listicles; no dated request post was found. The closest is "One MCP directory for all docs.domain.tld" (HN 2026-08-26, https://news.ycombinator.com/item?id=49447616) and "A model router should also provide a MCP gateway" (HN 2026-08-07, https://news.ycombinator.com/item?id=49212357), which are people building rather than asking. An "MCP servers people ask for and can't find" idea was therefore not included. - Discord recaps: none found for July–September that were fetchable. ## Counts - Searches run: 36 WebSearch queries + 9 structured API queries (HN Algolia, GitHub search) = 45. - Unique URLs cited in this report: 71 (all opened and checked except the X post and the CSO Online article, which are cited via the HN item that links them).