A Show HN is the one $0 event that behaves like a paid traffic spike for people who run coding agents. It is also a one-shot consumable. This kit exists so the shot is taken with real data — not survivorship stories — and only once the traffic has somewhere good to land.
Mined from the true Show HN population over the last 3 years via the HN Algolia API (empty-query population pull, no relevance bias). N = 79,893 Show HN; agent-tooling comparable cohort N = 9,483. Re-mine before any launch date — node scripts/shn-miner.mjs.
| Cohort | N | Median | P75 | P90 | P95 | <10 pts | 100+ pts |
|---|---|---|---|---|---|---|---|
| All Show HN | 79,893 | 2 | 4 | 12 | 47 | 88% | 3% |
| Developer tooling | 14,930 | 2 | 3 | 10 | 31 | 90% | 2% |
| Agent tooling (our set) | 9,483 | 2 | 4 | 9 | 23 | 90% | 2% |
| Comparable launch | Points | Comments | Date |
|---|---|---|---|
| Omnara — Run Claude Code from anywhere category ceiling | 310 | 168 | 2025-08 |
| Vibe Kanban — manage your AI coding agents | 195 | 132 | 2025-07 |
| OneCLI — Vault for AI Agents | 161 | 52 | 2026-03 |
| Agent Vault — credential proxy for agents | 156 | 55 | 2026-04 |
| Boxes.dev — ditch localhost; run CC in the cloud | 105 | 79 | 2026-06 |
| Pulse — approve tool calls from your phone cautionary | 39 | 13 | 2026-06 |
The cautionary one matters most. Pulse — "Dashboard for Claude Code, approve tool calls from your phone" — got 39 points, and its top comments were "Claude Code already does this natively." Lesson baked into the titles below: do not lead on phone-approval, and lead on what no comparable does — the agent building you a decision, not a log dump. Separately, "Continue? Y/N — a 60-second game about AI agent permission fatigue" scored 386 points: permission fatigue is a proven HN nerve, and it's exactly Meltbox's wedge.
Not the content — the timing. This is decided in the brief; here's the reasoning.
A Show HN is one-shot. Today the traffic would land on either an app login wall (meltbox.ai root is the app, not a landing page) or a noindex preview. Even a median Show HN with a real landing page beats a front-page hit that bounces. Two cheap prerequisites unlock the shot: (1) the docs robots.txt AI-crawler block is lifted (the AEO fix), and (2) the hello-demo page is live on a real URL. Both are other GTM items already in flight.
also on the table this week (fire now, accept the login-wall bounce) · after realtime ships (wait for a bigger story, risk the momentum cooling). The brief lets Will pick.
Winner shapes from the mined top set: Name – concrete what-it-does (em-dash) dominates; concrete numbers over-index; first-person "I built/used…" recurs; 0% of top titles use marketing adjectives. All five obey that.
Data: em-dash winner shape (Omnara/Semble/Mastra). "Decision inbox" is concrete and names the one mechanic no comparable has; "you already run" targets the exact ICP. Sidesteps the phone-approval trap that capped Pulse at 39.
risk "inbox" could read as email-adjacent — the first comment must clarify fast.
Data: the product's own line; precise ICP targeting. Clean, no adjectives.
risk "control plane" scans slightly enterprise/abstract next to the concrete winners.
Data: rides the permission-fatigue nerve that scored 386 points, and echoes a real operator on the Pulse thread: "phone only pings when something's irreversible… per-call approval you stop reading by day two." Positions against Pulse/native remote-control instead of competing with it.
risk "babysitting" is mildly loaded; two clauses.
Data: first-person origin framing recurs among winners ("I built a sub-500ms voice agent", "I put an AI agent on a $7 VPS"). Humanizes; leads with the shared pain.
risk longest of the five; some HN readers want the tool named first.
Data: the secret-proxy framing pulled 156–161 points for Agent Vault and OneCLI — proven live demand for exactly this sentence. Concrete and specific.
risk foregrounds one pillar and hides the brief story; invites the "prompt-injected agent still exfiltrates through the proxy" objection (answered in the crib sheet).
Drafts. The post body is the submission text; the first comment goes up within two minutes of posting. Both honest, concrete, ending in a real question — HN rewards a genuine ask.
POST BODY Meltbox is a control plane for the coding agents you already run. The bottleneck stopped being "can the agent do it" and became "the agent produces decisions faster than I can review them, scattered across terminal tabs, localhost pages, and Slack DMs to myself." So the agent hands me a *brief* instead: a small clickable HTML page with the actual choice laid out. I triage them in an inbox with keyboard shortcuts (j/k to move, e to archive), and my pick + note flow straight back to the agent as its next step. When something actually needs me, my phone gets a push — Mac and iPhone, even with the app closed. It also proxies your API keys: an agent gets a scoped key that resolves to the real token server-side, so it can *use* a connector without ever *seeing* the token. And it gives agents one authed place to build and update internal dashboards against shared data. Onboarding: sign up (email, Google, or anonymous guest -> workspace instantly), then hand a one-time invite link to Claude Code / Codex / any LLM. It redeems a scoped, revocable token and says hello with a brief. It's built by its own briefs — the PWA push, the MCP hub, keyboard triage, and the ChatGPT app were all shipped by an agent proposing a decision brief and me picking. Build log (8 real rounds): [build-log link] Free plan, works today at meltbox.ai. The thing I most want feedback on: is a clickable *page* the right unit for an agent to hand you a decision — or do you just want a better notification with a link back to the terminal?
FOUNDER FIRST COMMENT (post within 2 min) Founder here. Origin: I run a lot of agents, and "three tabs of Claude Code, two localhost pages, and a Slack DM to myself" became the actual job. I built the thing I wanted — agents come to me with a decision I can act on in two keystrokes, and my phone pings only when it's my turn. The part I'm least sure about and most want to argue about: I made the atomic unit a *brief* — a functional HTML page the agent builds — instead of a notification + a link back to a terminal. The bet is "here are 3 options, pick one, leave a note" beats "come look at my logs." The whole product is built this way: [build-log link] is 8 real rounds (PWA push, MCP hub, ChatGPT app, realtime) where an agent proposed a brief and I clicked. Stack: single Cloudflare Worker, D1, Durable Objects for realtime presence, Web Push (VAPID) for the phone. Secrets are a proxy, so the token never enters the agent's context. Happy to answer anything — especially "why not Slack / ntfy / the built-in CC remote control." Short answers below; poke holes.
Every objection below is a verbatim comment from a comparable launch thread (Pulse, Omnara, Vibe Kanban, Agent Vault, OneCLI, ntfy). Answer in your own words on the day — never paste.
Launch Tue–Thu, 12:01am PT. Assets: logo 240×240 PNG, 3–5 gallery images, demo GIF. Tagline <60 chars, no jargon, no adjectives.
“Your coding agents hand you decisions, not log dumps” 52 chars
“A decision inbox for the coding agents you run” 46 chars
DESCRIPTION (≈220 words) Meltbox is a control plane for the coding agents you already run — Claude Code, Codex, Cursor, cron jobs, anything. Instead of scattering their output across terminal tabs, localhost pages, and Slack DMs, your agents hand you *briefs*: small clickable pages that lay out a decision — "here are 3 options, pick one, leave a note." You triage them in a keyboard-fast inbox, and your choice flows straight back to the agent as its next step. When something actually needs you, your phone pings — Mac and iPhone, even with the app closed. Three more pieces come in the same authed home: a Secret Proxy so agents can *use* your API keys without ever *seeing* the tokens (scoped and revocable per agent); self-building Apps so agents can spin up and update internal dashboards against shared data; and a remote MCP server that works in ChatGPT. Onboarding takes a minute: sign up (email, Google, or anonymous guest), then hand a one-time invite link to your agent. It redeems a scoped token and says hello with a brief. Free plan. Meltbox is built by its own briefs — its PWA push, MCP hub, and ChatGPT app all shipped by an agent proposing a decision and a human clicking approve.
1 · Brief Inbox with the keyboard-triage overlay (j/k/e) · 2 · a real brief — 3 options + per-item note box · 3 · iPhone lock screen: "New brief in Meltbox" · 4 · terminal redeeming an invite → "says hello with a brief" · 5 · Secret Proxy diagram (agent → scoped key → real token, server-side) · 6 · the build-log: "shipped through its own briefs"
X / THREAD (5 posts) 1/ I run a lot of coding agents. The bottleneck isn't the agents anymore — it's that they produce decisions faster than I can review them, scattered across terminal tabs, localhost pages, and Slack DMs to myself. So I built Meltbox. 2/ The idea: your agent hands you a *brief* — a small clickable page with the actual choice — instead of "come look at my logs." You triage an inbox with j/k keys. Your pick flows back to the agent as its next step. 3/ When something actually needs you, your phone pings — Mac + iPhone, even with the app closed. Not per-call approval (you stop reading those by day two). Only the decisions that are yours. 4/ Keys: agents get a scoped proxy key that resolves to the real token server-side. The agent can *use* a connector without ever *seeing* the token. Revoke per agent. 5/ It's built by its own briefs — PWA push, the MCP hub, the ChatGPT app all shipped by an agent proposing a decision and me clicking. Free plan, works today: meltbox.ai
LINKEDIN (single post) The hard part of running coding agents in 2026 isn't getting them to do the work — it's that they produce decisions faster than one human can review, and the output scatters across terminals, localhost pages, and DMs. Meltbox is the control plane for that. Your agents hand you decisions as small clickable pages — pick an option, leave a note, and it flows back to the agent as its next step. Your phone pings only when a decision is actually yours. Keys are proxied so agents can use connectors without ever seeing the tokens. It's built by its own briefs. Free plan at meltbox.ai — feedback welcome.
The first comment's credibility rests on this: 8 real shipped rounds, each proposed as a decision brief and chosen by a human.
Open the build log →