Post Show HN first
Stay in the thread for the first hour. Do not ask friends for upvotes or comments.
Open channelLaunch kit
Copy-ready posts for developer communities. The message is narrow: close your laptop while Claude Code, Codex, or a long terminal agent keeps running, then come back to a local receipt.
Post today
Use one channel at a time. The copy is tracked by source, and each post asks for workflow feedback instead of begging for attention.
Stay in the thread for the first hour. Do not ask friends for upvotes or comments.
Open channelIf HN gives useful feedback, make the second post about that behavior instead of repeating this copy.
Open channelUse this as a comment in the thread, not a standalone sales post.
Open channelUse the Product Hunt fields and assets below. Publish only when you can stay around.
Open channelUse in AI builder, indie hacker, or coding-agent groups that explicitly allow demos or feedback requests.
Open channelFast copy
Claude Watcher lets you close your Mac while Claude Code, Codex, or a long terminal agent keeps running, then come back to a local dashboard receipt.
Show HN: Claude Watcher - close your laptop while Claude Code keeps running
I built Claude Watcher for long Claude Code / Codex runs. It lets you close your Mac, keep the run covered, and come back to a local dashboard receipt with changed files, risks, token burn, and rollback notes. Free download, Solo is $9 lifetime: https://www.claudewatcher.com/?utm_source=community&utm_medium=launch-kit&utm_campaign=community-launch
The problem is not just auto accept. Auto accept answers prompts. Claude Watcher answers the practical question: can I leave the desk without killing the session, and when I come back, what changed?
Post now
These links use the tracked community URL. They do not submit anything automatically; they just open the right compose page.
I built Claude Watcher because a new developer habit is becoming normal: starting a Claude Code or Codex run, then carrying an open laptop around because closing it might kill the session. Claude Watcher is a macOS app for that workflow. It keeps long agent runs covered, shows a local dashboard, safely auto-approves low-risk Claude Code prompts, and gives you a receipt when you come back: changed files, token burn, risk labels, result, and rollback notes. The Free version includes the Active/Idle/Done board, Today dashboard, and Trace token view. Solo is $9 lifetime for Safe Carry, receipts, risk classification, rollback notes, and prompt coaching. I would love feedback from people already using AI coding agents for long unattended tasks: what would make this feel trustworthy enough to close the laptop and walk away?
Agent queue
This queue optimizes for Claude Code and AI coding buyers first. It also names the exact approval gate so an agent can prepare work without accidentally publishing, paying, or sending contact email.
node scripts/promotion-drafts.mjs --channel=queue node scripts/promotion-drafts.mjs --channel=queue --json node scripts/promotion-drafts.mjs --channel=next node scripts/promotion-drafts.mjs --channel=next --json
Direct Claude Code and AI coding tools audience.
Developer tools and AI agents directory with no-signup positioning.
CLI and developer utility audience; weaker than Claude-specific directories but still relevant.
Claude ecosystem directory; high potential if standalone commercial developer tools are accepted.
AI agents and automation directory; broader but no-account and review-based.
Agent-native startup/tool audience; API-ready but previously rate-limited.
Developer productivity and AI coding tools audience.
Generic AI directory; lower buying intent but low submission effort.
AI coding category, secondary after Claude-specific directories.
Generic discovery and backlink value; lower audience specificity.
Claude developer audience, but current page emphasizes paid placements.
Real-time threads where the exact open-laptop carry pain appears.
Directories
These are slower than launch-day posts, but they keep showing up after the first day. Copy the prepared fields and submit one by one.
Agent-fillable. Draft was prepared in browser; final Submit requires explicit confirmation because it publishes to a third-party directory.
Open targetAgent-native programmatic submission. Public API is no-account/no-key, but the first attempt was rate-limited by IP; retry later.
Open targetFree listing, no account needed, human-reviewed in 24-48 hours. Needs explicit confirmation before entering contact email and submitting.
Open targetNo-account form with website name, URL, and email. Needs explicit confirmation before entering contact email and submitting.
Open targetFree path exists and review is manual, but it requires logo upload and likely screenshots. Needs explicit approval before uploading assets or submitting.
Open targetHigh-fit developer-tool and AI-agent directory. Public page says free/no-signup, but final Submit still needs explicit confirmation.
Open targetHigh-fit developer-tools directory with AI Coding, CLI, MCP, and Productivity categories. Inspect the live form because it is client-rendered.
Open targetGood fit because Claude Watcher has a free plan. No direct submit form was found in the indexed page, so use contact or owner outreach if available.
Open targetVery high-fit AI coding directory with Claude Code categories, compatibility fields, pricing, and install instructions. Needs explicit confirmation before contact email submission.
Open targetClaude ecosystem directory for developer tools and commercial integrations. Inspect the Submit a Resource flow before entering data.
Open targetSecondary AI coding tools directory. Use after CodeAI and Claude-specific surfaces.
Open targetClaude developer audience. Use only the free basic listing unless paid placement is explicitly approved.
Open targetUseful channels, but not autonomous: human verification, login, or unreachable submit flow.
Open targetTrack these so future agent runs do not waste cycles or submit the wrong kind of asset.
Open targetBest fit for developer-tool discovery. Use the AI coding + macOS utility angle.
Open targetRequires an account. Keep it founder-feedback oriented, not a generic ad.
Open targetSubmit and verify the product, then use the directory posting workflow.
Open targetEmail submission. Include logo and gallery URLs from this launch kit.
Open targetUse only if framed as recently launched and keep the custom-domain download path clear.
Open targetI built Claude Watcher because I kept seeing people carry open laptops around while Claude Code or Codex was still working. It is a small macOS app for AI coding agent runs: - keep long Claude Code, Codex, and terminal agent sessions covered - see active, waiting, blocked, and finished runs in a local dashboard - safely auto-approve Claude Code prompts while holding risky actions - return to receipts with changed files, token burn, risks, and rollback notes - optional prompt coaching for vague Claude Code prompts with local Ollama The free version gives you the Active/Idle/Done board, the Today dashboard, and the Trace token view. Solo is $9 lifetime for the close-lid workflow. I am especially interested in whether this matches how other people are actually using coding agents now.
I built Claude Watcher after noticing a strange but real workflow: developers walking around with an open laptop because an agent session was still running. The app is meant for long Claude Code, Codex, and terminal agent runs. It gives you a local dashboard with active/waiting/done sessions, keeps runs covered while you step away, safely auto-approves low-risk Claude Code prompts, and gives you a receipt when you come back. The receipt includes changed files, token burn, risk labels, result, and rollback notes. There is also optional prompt coaching for vague Claude Code prompts if you run local Ollama. Free gets the Active/Idle/Done board, Today, and Trace. Solo is $9 lifetime for the close-lid workflow. I would love feedback from people using coding agents for longer unattended tasks: is this the right surface, or would you want a different workflow?
X posts
I built Claude Watcher for the weird new developer behavior where people carry an open laptop around because Claude Code or Codex is still running. Close your laptop. Keep your agent running. Come back to a receipt. https://www.claudewatcher.com/?utm_source=community&utm_medium=launch-kit&utm_campaign=community-launch
Claude Watcher is a macOS app for long Claude Code / Codex runs: - close-lid Safe Carry - local session dashboard - safe auto-approve - risk labels - token burn - rollback notes - prompt coaching Solo is $9 lifetime. https://www.claudewatcher.com/?utm_source=community&utm_medium=launch-kit&utm_campaign=community-launch
Promotion loop
The launch is not done when the first links go out. Log feedback, answer the first objections, and reuse real language in follow-ups.
Paste this under every channel. Save exact objections instead of paraphrasing them.
Channel: Post URL: Time posted: Views / clicks: Emails captured: Purchases: Strongest positive signal: Sharpest objection: Repeated question: Feature request: Exact quote worth reusing: Next copy change:
Use when someone asks what is actually different from auto accept.
Thanks for checking it out. The behavior I am trying to solve is pretty specific: long Claude Code / Codex runs where you want to leave the desk without losing track of what happened. The part I am most interested in validating is whether the receipt is enough: changed files, token burn, risk labels, and rollback notes. If you run agents this way, what would you need to trust it?
Use after the first real feedback pattern appears. Do not post before there is a signal.
Follow-up on Claude Watcher: The strongest signal from the launch was not "people want another auto-accept tool." It was that developers want permission to stop babysitting terminal agents. Close the laptop, keep the run covered, come back to a receipt. https://www.claudewatcher.com/?utm_source=x&utm_medium=community&utm_campaign=launch-followup
Send to indie/devtools newsletters that accept maker submissions.
Subject: Tiny macOS tool for developers carrying open laptops during AI agent runs Hi, I built Claude Watcher after noticing a new developer workflow: people walking around with an open laptop because Claude Code, Codex, or a terminal agent is still running. It is a macOS app that keeps long agent runs covered while you step away, safely auto-approves low-risk Claude Code prompts, and gives you a local receipt when you return: changed files, token burn, risk labels, result, and rollback notes. Product page: https://www.claudewatcher.com/?utm_source=newsletter&utm_medium=outreach&utm_campaign=launch Launch kit: https://www.claudewatcher.com/launch I think it fits readers who are already using AI coding agents for long unattended tasks. Happy to send screenshots or a short demo note if useful.
Replies
The free version covers the Active/Idle/Done board, Today dashboard, and Trace token view. The paid version is priced as a small one-time utility because the value is avoiding one killed run, one wasted token burn, or one mystery diff after stepping away.
Claude Watcher is local-first. It does not upload repo contents or terminal history. Safe auto-approve is bounded to low-risk Claude Code prompts, while risky actions are held for review.
That is exactly why the app is explicit about boundaries. It keeps sessions covered while the Mac is awake and managed; it cannot help if the machine powers off, loses battery, overheats, or is blocked by company policy.
Boundaries