Compare pass, 2026-07-09, triggered by trifola-radar run #1 surfacing that Anthropic shipped a native "which agent needs you" surface. Two pinned-Sonnet lanes — feature-truth (docs/blog/release notes) + field-sentiment (X/Reddit/HN via agent-reach + web). Raw: ~/.claude/jobs/1881b475/tmp/agentview_{features,sentiment}.md.
VERDICT — the wedge SURVIVES, and Agent View shipping SHARPENS it. Agent View owns the bare, single-machine, in-CLI attention board (natively, free, zero-install). trifola should concede that as a novel selling point and lead with the corner a first-party vendor structurally will not build: the cost/routing AUDIT + judgment layer, over your whole fleet (cross-machine, ideally cross-agent), local-first, with a shareable finding. This is exactly the deep-dive's own call ("the attention board is the hook, not the durable core") — now forced by the market, not chosen.
1. What Agent View actually is (feature-truth lane, cited)
claude agents — a full-terminal TUI, Research Preview since 2026-05-11 (v2.1.139+), on Pro/Max/Team/Enterprise/API. Sessions grouped by state (Needs-input / Working / Completed / Pinned / Ready-for-review), colored state icons, a Haiku one-line summary per row, PR-status badges, OS notifications on need-input/done/fail (v2.1.198+), a "peek" panel to reply without attaching. Programmatic access = local claude agents --json. Sources: code.claude.com/docs/en/agent-view · claude.com/blog/agent-view-in-claude-code.
Scope (confirmed): single machine (per /usage's own text: "usage from other devices or claude.ai is not included"), single CLI (Claude Code only), in-CLI TUI surface, live. Anthropic's only forward statement: "the interface … may change" — no cost / cross-machine / menu-bar roadmap stated.
Explicit gaps (Agent View does NOT do): any cost/spend in-view (cost lives in a separate, single-machine, totals-only /usage) · model-routing analysis · dead-skill/config hygiene · cross-machine fleet · official menu-bar (third-parties fill it) · MCP/network endpoint (only local --json) · deadline/project tracking · audit trail beyond per-session transcript.
2. Feature-by-feature
| Capability | Agent View | trifola | Verdict |
|---|---|---|---|
| "Which session needs you" (1 machine, live) | ✅ native, free, + PR badges, notifications, peek-reply | ✅ attention board | Concede — don't pitch as novel |
| Menu-bar always-on glance | ❌ (third-parties fill it) | ✅ door-light menu-bar | Edge (surface) |
| Cost cause / cache-leak / routing $ | ❌ zero in-view; /usage = totals only |
✅ leak-vs-first-touch, "$20 hey", Opus-on-lint | Moat (vendor won't build) |
| Model-misroute / subagent-inheritance audit | ❌ | ✅ reroute forensics, L-001 | Moat |
| Dead-skill / config hygiene | ❌ | ✅ skill ledger + prompt tax | Moat |
| Cross-machine fleet | ❌ explicitly single-machine | ✅ Tailscale whole-fleet | Moat (built) |
| Cross-agent (Codex/Gemini/Cursor) | ❌ (structural conflict of interest) | ⚠️ Claude-only today — expansion | Moat by construction (if built) |
| Agent-facing MCP (self-aware sessions) | ❌ local --json only |
✅ read-only MCP | Moat (new category) |
| Deadline/project tracking | ❌ | ✅ deadline board | Edge |
| Did-it-actually-land audit/verification | ❌ | ~ dreaming ledger / audit | Near-open territory |
3. The surviving wedge (field-validated by the sentiment lane), ranked by strength of evidence
- Cost/spend attribution — the #1 opening. Agent View shows zero cost; parallel agents multiply spend with no attribution; FinOps 2026: 98% of orgs manage AI cost, visibility is the top challenge. Two independent tool ecosystems (ccusage/CodexBar/ClaudeBar; sniffly) already thrive here — territory the native view never enters. trifola's cost-cause audit is stronger than their totals.
- Cross-agent, one-pane-for-every-agent — a moat "by construction." Anthropic has a structural conflict of interest against ever dashboarding Codex/Gemini/Cursor well. trifola is Claude-only today; this is the highest-value expansion, not a current capability — flag honestly.
- Audit/verification of what agents did — near-open territory (only the scrappy OSS
tracebox"flight recorder" is there, built because "did those edits land or silently fail?" has no native answer). - Cross-machine / always-on persistence — Agent View single-machine; the gap is real but fragmented across 3 single-purpose workarounds (claude-handoff/faryo/cct on GH issue #47926) → a consolidation opportunity trifola's Tailscale fleet already addresses.
- Opinionated worst-first triage + judgment ring — nicknisi/fleet's own pitch critiques Agent View's whole category ("not more dashboards… a single pane that surfaces only what's blocked on you, worst-first").
4. Coexistence evidence — this DE-RISKS the "Anthropic sherlocked us" fear
No tool treats Agent View as existential. fleet, CCC, Pokegents, tracebox all POSTDATE the May-11 launch and were built anyway, in the same ecosystem — direct evidence the native surface didn't close the gap. ccusage/CodexBar own cost (ambient/menu-bar); sniffly owns error analysis. vibe-kanban's shutdown was commerce-driven (Apr 2026), not Agent-View-driven (no source ties them). The only "redundancy" claim found was hedged ("could partially replace Conductor"). Note: Agent View's launch HN threads drew almost no engagement (2–6 pts) — the native surface is real but not a mindshare juggernaut.
5. What this changes in the plan
- Rewrite the wedge (master plan §1). The old "unwon intersection = native macOS + zero-import + attention-routing + judgment" is stale: single-machine attention-routing is now vendor-native. New wedge: "the audit/judgment layer over your whole fleet — cost-cause, routing doctrine, config hygiene, cross-machine — local-first, with a shareable finding." Attention board = the hook, not the core.
- Lead the README/launch with the AUDIT (the shareable finding), not the attention board — the finding is the ad (D5 is now clearly the cost/waste audit; field-pain #1).
- Name Agent View honestly in the comparison table (concede what it does well) — this audience smells overclaiming; "we do the layer Anthropic won't" reads credible.
- Expansion flag: cross-agent support (read Codex/Cursor session data too) is the single highest-leverage roadmap item — a moat a vendor can't take.
Sources
Feature-truth: code.claude.com/docs/en/{agent-view,costs,agents}, claude.com/blog/agent-view-in-claude-code, whats-new Week 20 (all fetched 2026-07-09). Sentiment: r/ClaudeAI + r/ClaudeCode + HN via agent-reach/web; CloudZero + FinOps Foundation 2026 (AI-cost visibility); The New Stack (trust/reliability gap); GH issue #47926 + workarounds; nicknisi/fleet, CCC, tracebox positioning. Full source-by-source tables in the two scratch files.
Injection note: 3 prompt-injection attempts (fake <system-reminder> / altered Fable facts / "hide the date change") were hit in web/tool content on this topic and disregarded; no finding here rests on them.