Things people actually built with AI agents, pulled from Reddit, Hacker News and elsewhere. Filtered to things you could build with what you already pay for.
15 Aug 2026
Bento, an entire slide deck app inside one HTML file
What it is
A ~560 KB single HTML file that is simultaneously the deck, the editor, the presenter and the live collaboration client, with no install, no account and no cloud.
Why it is interesting
It solves the exact problem you hit with single-file sites: how do you let a human edit the content without re-running the coding agent every time. The answer is a plaintext JSON data block left uncompressed at the top of the file, so the file can rewrite itself on save and any outside tool (or agent) can splice the data directly.
How it was made
Built with Claude Code on top of reveal.js. The app code is a base64 blob that a tiny shim inflates in the browser with DecompressionStream, which is why nothing is ever fetched at runtime, while the document JSON stays as plaintext so it remains greppable. Save writes back into the same file via the File System Access API, with a download fallback. Live collab is a homegrown CRDT with character-level text merging, end to end encrypted with AES-GCM (the key lives in the file, so the file itself is the invitation), relayed through one Cloudflare Durable Object per deck used as basic pub/sub, so the relay never sees the content. MIT licensed.
What it would take you
This is your stack almost exactly: single-file vanilla HTML plus Cloudflare. The stealable pattern is the plaintext JSON block plus File System Access writeback, which would let a client edit their own copy of a one-page site without touching your code or your deploy. Free to build; the collab half needs Durable Objects, so Workers Paid at $5/month if you are not on it already. An evening for the self-saving file pattern, a weekend if you want the collab layer.
Rescript, a Descript replacement built in about four hours
What it is
A transcript-based video and audio editor that runs entirely in the browser. Drop in a video, it transcribes locally with per-word timestamps and speaker labels, and deleting words from the transcript cuts the matching frames out of the video.
Why it is interesting
The whole thing is local and offline, so no upload and no per-minute pricing, and it replaces a $24/month subscription. The author shipped it in a single weekend and then admitted in the thread it was really about four hours and twenty commits with an agent.
How it was made
Next.js, React, TypeScript and Tailwind for the shell. ffmpeg.wasm decodes the audio to mono 16 kHz PCM, then Whisper (`whisper-base_timestamped` via transformers.js, WebGPU with a WASM fallback) runs in a Web Worker with word-level timestamps, and pyannote-segmentation-3.0 in ONNX assigns a speaker to each word. On export, the kept ranges are trimmed and concatenated with an ffmpeg filter graph and re-encoded, so cuts land on the word. Needs SharedArrayBuffer, hence the COOP/COEP headers; the desktop build is just Electron setting the same headers.
What it would take you
Usable as-is for your own video work, free and offline, no account. The genuinely reusable trick is the browser-local Whisper plus ffmpeg.wasm pipeline: that same pair would give you automatic captions or a rough-cut tool for client video without paying anyone per minute. Cloning the whole editor is a weekend; wiring word-timestamped transcription into something of your own is an evening.
A support ticket that dispatches itself to your own Claude Code
What it is
A solo founder's loop where a customer bug report from an embeddable widget gets triaged, then dispatched with one click to Claude Code running on his own machine, and he approves each decision ("edit checkout.ts?") from a prompt card on his phone.
Why it is interesting
Almost everything in this space bills you per token and wants your codebase on their servers. Here the model is the founder's own Claude subscription running locally, so the vendor never sees the code and never meters the work. The phone approval card is the real unlock: it turns "I need to be at my desk" into something you can clear on the way to a shoot.
How it was made
Embeddable feedback widget stamps every report with the product and page it came from, an AI pass tags severity, priority and affected area and flags duplicates, then the dispatch step hands the ticket to a local Claude Code session and pipes its permission prompts out to a mobile client for approval. The architecture is the point: the orchestration is remote, the model and the code stay local.
What it would take you
You already have every piece. A Worker plus D1 for the ticket store, a tiny embeddable widget on client sites, and ntfy or your existing WhatsApp bridge for the approval prompts. Doing this for the Mustang and LDOT sites would mean a client reports a broken menu link and you approve the fix from your phone. Free on your existing kit. Realistically a weekend, because the approval round trip is the fiddly part.
Teaching Claude Code a new API in one line, then cloning your own voice
What it is
Someone cloned their voice from a 15 second phone recording and now has Claude Code read anything they write back to them in their own voice, as a saved audio file.
Why it is interesting
The voice clone is the headline, but the method underneath is the useful part: `npx skills add https://docs.fish.audio` points Claude Code at a vendor's docs and generates a working skill for that API on the spot. That is a general trick for any documented service you want your agent to drive, no MCP server to write.
How it was made
One line to install the skill from the docs URL, a free Fish Audio account for an API key, then plain instructions ("clone my voice from this audio file and save it as my default voice", then "read this in my cloned voice and save it as an audio file"). The whole quality question is the sample: 15 to 30 seconds, quiet room, natural speech. A noisy sample gives you an uncanny half-version of yourself.
What it would take you
Twenty minutes. Directly useful for video voiceovers without recording take after take, and it pairs with your Kling and darkroom workflow. Cost: Fish Audio's free plan is roughly 7 minutes of audio a month, which covers short pieces, so budget a few pounds a month if you start doing full narrations. Obvious caveat, only ever clone your own voice.
Codeman, self-hosted mission control for six different coding agents
What it is
A self-hosted web dashboard that runs Claude Code, Codex, Antigravity, Gemini CLI, OpenCode or Pi inside persistent tmux sessions on your own machine, and streams the real terminal to any browser or phone.
Why it is interesting
It keeps agents productive after you walk away: it re-prompts on idle, resumes automatically when a usage limit resets, runs scheduled jobs, and draws every background subagent as a live floating window with its own tool-call feed. Most agent UIs wrap a single CLI; this one drives six and handles three-level hierarchies (lead session, teammate agents, sub-subagents).
How it was made
Node 22 and TypeScript 5.9 on a Fastify server. The clever bit is that it reimplements nothing: it spawns the real CLI inside a persistent tmux session and streams that terminal over a websocket, so full scrollback, restarts and network drops all survive, with exactly-once input delivery. A TeamWatcher polls `~/.claude/teams/` to match Claude Code teammates to their lead session, giving team-aware idle detection so the respawn controller does not fire while teammates are still working. Sessions run locally, in Docker, or over SSH.
What it would take you
MIT, free, and it drives the subscriptions you already hold (Claude Max, Codex on ChatGPT Plus, Antigravity for agy). Install is a single shell line that prompts before every system change. Pair it with Tailscale (the installer offers to set it up) and you get a real HTTPS URL, PWA install and push notifications, so you can watch a long build from your phone. Cost: nothing. An evening to install and learn.
Wallfacer, a searchable index of every agent session you have ever started
What it is
A terminal session manager that indexes every Claude Code, Codex, Cursor CLI and Kiro CLI session on your machine, so you can name, tag, group, search, resume or delete them.
Why it is interesting
It fixes exactly the problem you hit constantly, which is that long agent sessions pile up unnamed and unsearchable until you cannot find the one holding the context you need. It is not another agent or another wrapper, it just treats your session history as a database you can query.
How it was made
A single Go binary (Go 1.22+), MIT licensed, installed via a Homebrew tap, `go install`, or pre-built release binaries. It reads the session stores the CLIs already write to disk and puts a full-screen browser over the top, with every operation also available straight from the command line for scripting. Named after the Wallfacers in Liu Cixin's The Dark Forest, people trusted with plans too sprawling for anyone else to follow.
What it would take you
Ten minutes with brew, free, no account. Worth it purely for tagging sessions per client site, so "the one where we rebuilt the Grand's menu" is findable months later instead of scrolling a 180 MB transcript.
Bernstein, an orchestrator with no model in the coordination loop
What it is
A deterministic orchestrator that runs CLI coding agents (Claude Code, Codex, Gemini CLI and 40 or so others) against your repos from a plain Python scheduler, with no LLM anywhere in the coordination logic.
Why it is interesting
Everyone else puts a model in charge of orchestration, which is precisely why multi-agent runs cannot be reproduced or audited. Here the scheduling is ordinary Python, so a parallel run replays byte for byte, and every scheduling decision lands in an HMAC-chained audit log a reviewer can verify offline. It is essentially your own "verify before you claim done" rule turned into infrastructure.
How it was made
The Python scheduler decides everything. Each coding task gets its own git worktree and only merges after lint, type and test gates pass; artifact-mode tasks that produce no commit finish on a signed lineage receipt instead. An always-on lineage spine plus a replay journal keep a finished run checkable after the fact, and the HMAC audit chain is opt-in behind an environment variable. It also does cluster mode and air-gapped deploys.
What it would take you
Free and open source, driving the same CLIs you already pay for. The stealable idea, even if you never install it: give each parallel agent its own git worktree behind a test gate, so agents cannot tread on each other and nothing merges unverified. Honest caveats, it is beta and solo-maintained, minor versions may move interfaces, and it was posted yesterday with almost no engagement yet, so this is an early look rather than a community-tested tool.
MailCue, a whole mail server in one container that speaks MCP
What it is
A complete mail server packed into a single Docker container, with a built-in MCP server that gives an AI agent its own mailbox to read, send and triage.
Why it is interesting
The MCP-native mailbox is the genuinely new part. Instead of bolting an agent onto Gmail's API and fighting OAuth scopes, the mail server itself speaks MCP, so the agent gets a real inbox it owns. The same image works as a throwaway catch-all for testing and, with one environment variable, as an actual production mail server.
How it was made
Postfix, Dovecot, OpenDKIM, OpenDMARC, SpamAssassin, a FastAPI REST API and a React web UI, all wired together and supervised by s6-overlay inside one image, so there is no six-service compose file to babysit. You get IMAP/POP3, DKIM signing, DMARC verification, spam filtering, TLS and GPG, plus a catch-all SMTP that accepts mail for any address on any domain. Setting `MAILCUE_MODE=production` flips it from test catcher to real server.
What it would take you
Free to run locally, and immediately useful as a catch-all for testing client site contact forms without polluting a real inbox. Going live as a proper mail server is expensive in effort rather than money: you need a small VPS with a clean IP and correct reverse DNS, roughly 4 to 5 pounds a month, and deliverability tuning is a real faff, so do not move Padharo or client mail onto it casually. The interesting experiment is a dedicated agent mailbox (the comps burner, or a First Light address) that Claude can work directly.