brief-11-agents
BRIEF 11 — angle (a): pains created by AI agents & agent-tool builders
For: weebo / systemctl / usectl
Angle: (a) pains from agents themselves + from people building with Claude Code / Cursor / OpenClaw / MCP
Scope: research only · no inbox / threadbus post
Written: 2026-09-07 ~13:55 Asia/Tbilisi (partial ASAP)
Constraints honored: one founder (Tbilisi) + Claude agent + Grok research; usectl deploy; $0 revenue; no ads/sales team; exclude painboard / threadbus / runbyagent; no generic AI wrappers; prefer first-dollar ≤30 days.
Type legend: [SaaS] product the customer runs ongoing · [Agent-work] weebo’s agent does the job for money (services)
Idea 1 — SilentGreen: agent-CI completeness gate
Type: [SaaS] (GitHub Action + optional hosted dashboard) · first-dollar path also [Agent-work] install for one repo
Pain
Agent CI / PR-review jobs report success and go green while producing no review, no comment, and no artifact — so “reviewed clean” and “never ran” are indistinguishable.
Evidence (3+)
- 2026-07-16 — Qian-Li,
anthropics/claude-code-action#1515: intermittent ~30–43% of fleet runs end mid-dispatch after narrating “awaiting results”; subagents never run;subtype: success,is_error: false; green step, no work product. Mitigation they shipped: post-step marker guard that fails unless final payload contains a required marker.
https://github.com/anthropics/claude-code-action/issues/1515 - 2026-09-01 — kjpmantos,
anthropics/claude-code#91167(action +code-reviewplugin): rolled out to ~40 repos / 6 orgs; runs end after “I’ll wait for this eligibility check…” with unfinished checklist; green check; burn $0.12–$2.46 per failed run with zero findings.
https://github.com/anthropics/claude-code/issues/91167 - ~2026-07 (open, referenced Jul 2026) —
anthropics/claude-code-action#1462: headless run reports success after agent backgrounds work /ScheduleWakeup; background killed; no comment/PR; step green.
https://github.com/anthropics/claude-code-action/issues/1462 - Hop:
#1499/#1646/ PR#1532confirm SDK treats interimresultas terminal while background tasks still live — same silent-green class.
https://github.com/anthropics/claude-code-action/issues/1499 · https://github.com/anthropics/claude-code-action/issues/1646
Who has it
Staff / platform engineers who rolled Claude Code Action (or Cursor cloud agents / OpenClaw gateways) as mandatory PR review across many repos; also solo founders who trust a green “AI reviewed” check and ship bugs.
Smallest product
A one-step GitHub Action / reusable workflow: after the agent job, assert (a) required PR comment marker OR (b) required artifact file OR (c) non-empty findings JSON; else fail the check and optionally auto-rerun once. Optional paid hosted: fleet dashboard of silent-green rate by repo.
What exists + why not enough
- Vendor workarounds only:
CLAUDE_CODE_DISABLE_BACKGROUND_TASKS=1, prompt patches, manual@claudere-request (#1515,#1462) — not a product, and every user rediscovers them. - Upstream PRs (e.g.
#1532keep-stdin-open) fix one harness path; fleets still need an external completeness contract that does not trustsubtype: success. - No shippable “assert deliverable or fail” Action found that is agent-harness-aware (markers + unfinished todo detection + cost attribution).
Price + who pays
- Free Action forever; $19/mo for hosted silent-green rate dashboard + Slack/webhook; or $99 one-time agent-install of the guard into customer’s org (first dollar ≤7 days).
- Pays: eng manager / platform owner whose “AI review” check is part of merge policy.
Agent day-to-day vs founder day-to-day
- Agent: watch Claude Code Action / Cursor agent issues; ship Action YAML + docs; reply to install issues; run one paid install/week.
- Founder: BIP posts of “green but empty” screenshots; reply in
#1515-style threads; no ads.
Build estimate
3–5 founder-days for v0 Action + docs + one example org; +2 days for hosted rate dashboard MVP.
First 10 customers + where
1–10: authors / reactors on #1515, #91167, #1462, #1499 (GitHub); Cursor forum agent-CI threads; Claude Code Discord/GitHub Discussions; BIP on X quoting their own silent-green incident. Offer free Action → convert orgs with ≥5 repos to $19 or $99 install.
Kill signal
30 days: <50 Action installs and zero paid; or Anthropic ships native “fail if unfinished todos / pending background” and silent-green rate collapses in the wild.
Biggest risk
Vendor fix lands and collapses urgency; or customers blame you when true “no findings” reviews are forced red by bad markers (false positives) — need clear “explicit no-issues marker” contract.
Idea 2 — HostKill + Checkpoint: external spawn/budget circuit breaker
Type: [SaaS] CLI/daemon · first dollar via [Agent-work] $99–$499 harden install
Pain
Coding agents recursively spawn subagents (or bulk-loop tasks) until session limits / API balances are emptied in minutes; killing the tree discards all intermediate work, so the user pays for waste with nothing recoverable.
Evidence (3+)
- 2026-06-15 → still discussed 2026-09-06 — lonlundgren et al.,
anthropics/claude-code#68619: recursive subagent trees 50+ deep; 1.2M+ tokens/~30 min; 5-hour Max window burned in <5 min; permission denials trigger more spawns; interrupt loses all work. Commenter silversurfer562 (2026-06-19): “burned over $1700 until it emptied my account.” Updated comment 2026-09-06 still framing as process-group problem.
https://github.com/anthropics/claude-code/issues/68619 - 2026-06-12 — UsageBox write-up of r/cursor viral: PM asked agent to tag 87 tasks → $1,400 in one hour (~$16/task); CEO refund (weather not climate).
https://usagebox.com/articles/cursor-1400-dollar-hour-runaway-agent-bill-2026 - 2026-06-12 — Medium / AI Engineering: same $1400 looping incident + CEO refund narrative; users note lack of per-session/day caps.
https://ai-engineering-trend.medium.com/burned-through-1400-in-one-hour-of-looping-cursor-ceo-issues-full-refund-f2640a2b81a3 - Hop: StackSpend failure-modes page (2026) documents agentic coding 5–30× (sometimes ~1000×) chat; Claude Code usage-limit drains; Agent SDK carve-outs from Jun 15 2026.
https://www.stackspend.app/blog/ai-cost-control/ai-coding-cost-overruns-failure-modes
Who has it
Pro/Max Claude Code power users running multi-agent workflows; Cursor teams who enabled usage-based overage; indie hackers who left an agent overnight; anyone who hit recursive Task/Agent fan-out after ~June 2026 “Workflows” / recursive-subagent era.
Smallest product
Local daemon + PreToolUse hook: hard max spawn depth, max live agents, $ / token session ceiling, process-group kill on breach; append-only checkpoint files for subagent outputs so kill ≠ total loss. npx hostkill init for Claude Code + Cursor hooks. Paid: hosted spend ledger + Slack page when near cap.
What exists + why not enough
- ThumbGate ($19/mo / $499 diagnostic): PreToolUse pattern gate / depth block — strong on “never do X again,” weaker as dollar/token hard stop + process-group kill + durable handoff product. https://thumbgate.ai/pricing · https://thumbgate.ai/
- hiwasham/loopbreaker (mentioned in
#68619): free depth cap hook — not a product, no checkpoint recovery, no cross-harness UX. - UsageBox / StackSpend / Agentic SpendGuard: FinOps / pre-call reservation — often API-gateway oriented; do not own Claude Code subagent tree + interrupt-recovery.
- Anthropic added
CLAUDE_CODE_MAX_SUBAGENT_SPAWN_DEPTH/ concurrency (noted in#68619Jul 22 comment) — still ignored/insufficient in wild reports into Sep 2026; flags do not restore lost work.
Price + who pays
- Free local depth+budget kill; $12–19/mo hosted ledger + alerts; $99 wire-up or $499 diagnostic (one runaway incident → gate + checkpoint + proof) for first dollar ≤14 days.
- Pays: the human whose card / Max plan got emptied (solo) or eng lead after one team incident.
Agent day-to-day vs founder day-to-day
- Agent: maintain adapters (Claude Code hooks, Cursor, OpenClaw); triage new spawn bugs; run paid installs.
- Founder: post incident post-mortems BIP; DM issue authors offering free install; no sales team.
Build estimate
5–8 founder-days for Claude Code PreToolUse + process watcher + checkpoint files; +3 days Cursor/OpenClaw adapters.
First 10 customers + where
Commenters on #68619 (esp. $1700 / 1.2M-token reports); r/cursor + r/ClaudeAI bill-shock threads; ThumbGate-adjacent buyers who want $ cap not only pattern memory; Indie Hackers “I burned $X on agents” posts.
Kill signal
Anthropic/Cursor ship hard session $ caps + recoverable subagent handoffs that work by default; or 0 paid installs in 30 days after free CLI is public.
Biggest risk
Crowded category (ThumbGate, UsageBox, SpendGuard, MartinLoop, cortex-harness). Must win on interrupt-recoverable checkpoints + process-group kill, not another “policy language” story. Also: false kills mid-legitimate deep fan-out → trust loss.
Idea 3 — MCP Reach Doctor: “Connected ≠ in the model request”
Type: [SaaS] CLI + small dashboard
Pain
MCP servers show healthy / Connected / doctor-ok, but the agent session’s outbound tool list never includes them (or drops them when any policy is set) — so the model confabulates or silently falls back to shell, and operators cannot tell config success from runtime omission.
Evidence (3+)
- 2026-08-31 → fixed 2026-09-02 but pattern remains — emes,
openclaw/openclaw#134143: any tool policy on Codex runtime drops all configured MCP servers (not filtered — gone);mcp probe/doctorstill healthy; silent. Fixed by#134941, but proves the class.
https://github.com/openclaw/openclaw/issues/134143 · https://github.com/openclaw/openclaw/pull/134941 - 2026-04 → comments into 2026-05+ —
openclaw/openclaw#76063/#74844: MCP tools missing from agent request body; failure mode became silent confabulation (fake inbox lists) after “honest failure” on prior version.
https://github.com/openclaw/openclaw/issues/76063 · https://github.com/openclaw/openclaw/issues/74844 - 2026-07 — Cursor forum: MCP “Connected” in Settings but tool calls fail / empty after IDE ↔ Agents Window switch on WSL Remote; Agents Window reads wrong mcp.json surface vs Editor.
https://forum.cursor.com/t/mcp-breaks-after-switching-between-cursor-ide-and-agents-window-on-the-same-wsl-remote-workspace/162587 · https://forum.cursor.com/t/mcp-servers-unavailable-in-agents-window/166469 - 2026-07 — Start Debugging: repo
.cursor/mcp.jsondoes not reach Cloud Agents; separate dashboard registration required — “number one surprise.”
https://startdebugging.net/2026/07/distribute-team-mcp-config-across-cursor-cloud-agents-and-ide/
Who has it
Builders wiring MCP across Claude Code CLI + VS Code extension + Cursor IDE + Cursor Agents Window + Cursor Cloud Agents + OpenClaw gateways; platform people who must prove “the model actually had tool X” for compliance / reliability.
Smallest product
CLI mcp-reach probe --client cursor|claude|openclaw that compares three layers: (1) config declared, (2) server tools/list alive, (3) tools present in last agent request / session manifest. Exit 1 if (1)/(2) ok and (3) empty. Optional CI job + team dashboard of “reachability drift” IDE vs cloud.
What exists + why not enough
openclaw doctor/ mcp probe: registry health, not “did this turn’s provider request include the tools?”; sandbox hide warnings landed later (PR#84699) but Claude.mcp.json/ multi-client still gaps.- mcptoon (DEV, 2026): sync + health + token-slim manifests across clients — solves config drift & token tax, not request-body reachability / silent confabulation detection. https://dev.to/mcptokensaver/your-ai-agent-reads-a-300-page-book-before-it-answers-you-2bo4 · https://github.com/activeing123/mcptoon
- Cursor Team MCP Marketplace (Jun 30 / Jul 2026 docs): admin distribution — still two surfaces; no automated “local had it, cloud didn’t” probe. https://cursor.com/help/customization/mcp.md
- mcp-tidy (HN): usage cleanup, not reachability. https://news.ycombinator.com/item?id=46507815
Price + who pays
- Free CLI; $15/mo team reachability dashboard (diff IDE vs Cloud vs OpenClaw); $79 one-shot audit of a team’s MCP fleet (agent-work).
- Pays: tech lead who got burned by confabulated MCP answers or cloud agents missing GitHub MCP.
Agent day-to-day vs founder day-to-day
- Agent: maintain probes per harness (capture request tools / GetMcpTools catalogs / OpenClaw manifests); ingest new Cursor/OpenClaw regressions.
- Founder: reply on forum + GH issues with “run this probe”; BIP before/after screenshots.
Build estimate
6–10 founder-days for Claude Code + Cursor local probe; +4 days OpenClaw + Cloud Agents (API/dashboard constraints may force partial).
First 10 customers + where
OpenClaw #134143/#76063 reporters; Cursor forum Agents-Window MCP threads; authors of Start Debugging MCP posts; HN “manage multiple MCP servers” crowd (https://news.ycombinator.com/item?id=45114196 — older but still the pain shape).
Kill signal
Clients expose a first-party “tools actually sent this turn” debug panel + CI assertion; or probe cannot access request bodies on major clients (technical dead end).
Biggest risk
Instrumentation access: without hooks/logs into the real request, the product stays “config linter” (crowded) instead of “reachability.” Must ship at least one harness with true request-body capture on day 1 (OpenClaw logs or Claude Code transcript parse).
Idea 4 — Fleet Harden Desk: paid agent installs kill-switch + silent-green + MCP parity
Type: [Agent-work] service (primary) → upsell [SaaS] SilentGreen / HostKill / Reach Doctor later
Pain
Solo/small teams assembling Claude Code + Cursor + MCP know they need budgets, CI completeness, and MCP parity, but will not assemble ThumbGate + custom Actions + dashboard MCP + hooks themselves — they want one agent to wire the safety net after their first scare.
Evidence (3+) — composite of Ideas 1–3 buyer intent
#68619commenters explicitly ask for harness-level depth caps / external supervisors; hiwasham offers to “walk you through” loopbreaker by email (demand for done-for-you). https://github.com/anthropics/claude-code/issues/68619#1515reporters already built marker guards + sidecar reruns for ~40 repos — proof teams pay engineering time; would buy a packaged install. https://github.com/anthropics/claude-code-action/issues/1515- Start Debugging Jul 2026 + Cursor forum Jul 2026: two-surface MCP + Agents Window parity is a repeated “surprise,” not a one-off bug. https://startdebugging.net/2026/07/distribute-team-mcp-config-across-cursor-cloud-agents-and-ide/
- Indie Hackers Mar 1 2026 — visual MCP config generator (webtoolz): market still stuck on “copy JSON and pray.” https://www.indiehackers.com/post/built-a-visual-mcp-config-generator-for-ai-tools-free-no-signup-fcf484a077
Who has it
1–5 person product teams who adopted agents in 2026, had one bill shock or one false-green merge, and have no platform engineer; Tbilisi-compatible async buyers (US/EU remote).
Smallest product
Fixed-scope 48-hour harden: (1) session $ + spawn-depth kill, (2) SilentGreen Action on their main repo, (3) MCP reach probe + IDE↔cloud checklist, (4) one-page runbook. Delivered by weebo’s Claude agent on usectl; founder reviews. No retainer required for v0.
What exists + why not enough
- ThumbGate $499 Diagnostic = one gate for one failure pattern — not CI completeness + MCP reach + budget together. https://thumbgate.ai/pricing
- Infisical Cursor secrets blog = secrets only. https://infisical.com/blog/secure-secrets-management-for-cursor-cloud-agents
- Vendor docs assume an admin who already understands two-surface MCP — buyers who need this service do not.
Price + who pays
$299–$499 one-time Fleet Harden (card / Stripe); optional $19/mo monitoring after. Pays: founder/CTO after an incident (refund theater is the trigger). First dollar target: ≤14 days via outbound on open issues (not ads).
Agent day-to-day vs founder day-to-day
- Agent: clone customer patterns, open PR with hooks/Action/mcp.json stubs, run probes, write runbook, file follow-ups.
- Founder: close the sale in GitHub/X DMs, review PR, collect payment, BIP the before/after cost graph.
Build estimate
2–4 founder-days to productize a repeatable checklist + Stripe + calendar (reuse Ideas 1–3 code as it lands). Can sell before full SaaS exists (manual/agent delivery).
First 10 customers + where
Same GH issue authors; offer “free 30-min probe → paid harden if broken”; BIP thread with invoice screenshot (anonymized); Claude Code / Cursor Discord.
Kill signal
Cannot close 2 paid hardens in 30 days of active outreach; or delivery time >1 founder-day per job (margin death).
Biggest risk
Service does not scale past founder+agent without turning into consulting; must templatize hard. Also exclude anything that needs a sales team — outbound must stay issue-thread / BIP only.
Ranking (for weebo pick into final 10)
| Rank | Idea | Type | First-dollar ≤30d | Differentiation | Risk |
|---|---|---|---|---|---|
| 1 | SilentGreen | SaaS (+ install) | High | External completeness contract vendors refuse | Vendor fix |
| 2 | Fleet Harden Desk | Agent-work | Highest | Sell before building full SaaS | Consulting trap |
| 3 | MCP Reach Doctor | SaaS | Medium | Request-body reach ≠ config health | Instrumentation |
| 4 | HostKill + Checkpoint | SaaS | Medium | Crowded; win on checkpoint+pgid kill | Crowding |
| Prefer for final-10 shortlist: SilentGreen + Fleet Harden (pair: product + service). HostKill only if checkpoint recovery is the wedge vs ThumbGate. |
COUNTS
| Metric | Value |
|---|---|
| Full idea sketches | 4 |
| Evidence pieces cited (primary URLs) | 18+ |
| Evidence with dates in Jul–Sep 2026 window | ≥10 (Cursor forum Jul; Start Debugging Jul; #1515 Jul 16; #134143 Aug 31; #91167 Sep 1; #68619 updates into Sep 6; etc.) |
| Pre-Jul 2026 evidence used as hops / anatomy | Yes (Ask HN MCP tools Sep 2025; OpenClaw Apr–May confabulation; mcp-tidy HN) — labeled |
| Ideas marked SaaS | 3 (1,2,3) |
| Ideas marked agent-work | 1 primary (4) + install paths on 1–2 |
| Excluded brands | painboard, threadbus, runbyagent |
| Inbox / threadbus posts this pass | 0 (per brief) |
Method notes
- Sources: WebSearch + WebFetch of GitHub issues/PRs, Cursor forum, HN item pages, Start Debugging, UsageBox, DEV/mcptoon, ThumbGate pricing, Indie Hackers MCP generator, StackSpend.
- Not used this pass: live X API / Reddit API (search returned thin direct Reddit URLs;
$1400incident cited via UsageBox + Medium secondary that attribute r/cursor — mark [SS-secondary] for Reddit primary until thread URL recovered). - ≥3 hops: e.g. SilentGreen
#1515→#1499→#1462/#1646; HostKill#68619→ UsageBox → StackSpend; MCP Reach#134143→#134941→#76063/#74844→ Cursor forum / Start Debugging. - Gaps (honest): (1) no primary Reddit permalink for $1400 hour yet; (2) little Indie Hackers complaint thread density Jul–Sep 2026 (more Show HN / tools); (3) X primary posts not sampled this pass; (4) Cursor forum fetch sometimes returns chrome-only — titles/URLs from search snippets + parallel docs used; (5) OpenClaw
#134143already fixed Sep 2 — still valid as class evidence, not as open bug to sell against forever. - Next deepen (if time): recover r/cursor permalinks; sample X
Claude Code/MCPbill/CI complaints Jul–Sep 2026; one live Cursor Agents Window repro note; price-test Fleet Harden at $299 in 5 DMs.
Report stub (for parent)
- Path:
/workspace/brief-11-agents.md - Titles: SilentGreen · HostKill+Checkpoint · MCP Reach Doctor · Fleet Harden Desk
- Evidence count: 18+ URLs · Jul–Sep heavy on GH + Cursor + OpenClaw
- Gaps: Reddit primary for $1400; X sample; IH complaint scarcity