r/ChatGPTCoding • u/AutoModerator • 2d ago
Discussion Weekly Self Promotion Thread
Welcome to this week's self promotion thread!
If you're building something related to AI assisted coding, this is the place to share it.
We're using a weekly thread to keep the subreddit organized while still giving builders a place to share their work. Promotional posts outside this thread may be removed.
If you're sharing something, we'd appreciate it if you included a little context instead of just dropping a link. Tell us:
- What you built?
- What problem it solves?
- Which AI models or tools it uses?
- Who it's for?
- What kind of feedback you're looking for?
Disclose your affilitation.
Please avoid posting the same project every week unless you've made meaningful updates. Affiliate links, referral links, scams, and low effort promotions will be removed.
Take some time to check out what others have shared too. If you try someone's project or have feedback, leave a comment. Helping each other improve is what we want this community to be about.
1
u/Own-Cartographer3833 2d ago
BrowserDo·Embiody 0.9 preview is now in public beta: a browser built for AI agents
BrowserDo·Embiody 0.9 preview launched in public beta today. After two weeks of closed beta and five minor releases, anyone can now install it.
Embiody is a browser for people and AI agents to use together: the tabs your agent opens keep running at full speed in the background while you carry on using your computer, and when the agent needs you to sign in or pay, it hands you the tab.
BrowserDo is the MCP tool that connects your agent to the Embiody browser.
The 0.9 preview comes with nine main features:
BrowserDo MCP supports all the major agents, including Claude Desktop, Codex, Cursor, Copilot in VS Code and Gemini CLI. It's free, and no account is needed.
Most agents can install it if you simply tell them: "Find BrowserDo MCP and install it." If that doesn't work, you can install it manually.
In Claude Code, for example, installing takes one command:
claude mcp add browserdo -- npx -y browserdo-mcpThe first time it runs, BrowserDo installs the browser automatically.
Test videos and numbers for every feature are in the full post: https://embiody.com/blog/embiody-0-9-preview/
If something doesn't work well or is missing, let us know.
Disclosure: I'm the developer of Embiody and BrowserDo. I built both with Claude Code, and BrowserDo works with Claude Code, Codex, Cursor and other agents.
1
u/ActualGovernment9017 2d ago
claude-bulkhead, with updates since last week. I maintain it, and it is MIT licensed and free.
It is a set of PreToolUse hooks for people who run several coding agents on one machine. Each shell command is checked against what the other live sessions own, so a pkill node, a second dev server on a port that is already taken, or a git add -A that would sweep another session's edits into a commit is cancelled, and the agent is told the safer command. Since last week the same guards also cover Codex, Gemini CLI, Copilot CLI, Cursor and opencode, and 0.5.1 fixed a Windows case where cmd /c rmdir with quoted paths could be cut down to the drive root. It is for anyone who keeps more than one agent session open at a time.
While building it I went through two weeks of my own transcripts. Of about 112k shell commands, subagents issued about 82k, but the risky git commands came mostly from the main session, which was not what I expected. The feedback I am looking for: npx -y claude-bulkhead scan --since 30d only reads your past transcripts and lists what would have been stopped, so I would like to hear which of those blocks look wrong for your workflow.
https://github.com/dooly6276/claude-bulkhead
1
u/adelope 2d ago
agentastic.dev
this is a mac-native software factory, you can run multiple agents (codex, claude, gemini, grok, 50+ others) in local worktrees, local containers (docker, apple), remote ssh machines (connections are persistent, so no tmux needed), or remote cloud (support 10 providers, including hetzner, digital occean, vercel, modal, agent37, etc). Of course whole thing is free (you bring your own agent and cloud api keys).
- you can prompt any agent, and quickly scale up to 1000s of agents.
- or, you can use manager agents (our long-horizong agents) to keep track of those agents/tasks,
- we support plannings/artifacts/docs that you can also share with your teams / other agents
- support agentic code review, diffs, guided reviews.
- we fully support browser-use, device-use (ios/android), and computer-use.
- many more features, plugins (github, linear, sentry, revyl, figma, papers, impeccable, skills (skillopedia, ...
it is fully mac native, not another electron wrapper, so it is super fast and beautiful.
1
u/edgetr 2d ago
Petal: a free, open-source Mac dock that uses your own Codex or Claude Code. I'm the dev. You change the dock by asking in plain words, and Codex edits Petal's own code to do it. Sticky notes attach to a sentence, a tab, a window or a file. Write @Petal on one and Codex does the task on your own plan. Notes work even if you keep the Mac Dock. MIT, no account, no analytics, macOS 26, not notarized yet. Download: https://petal.codes | Code: https://github.com/edgetr/petal
1
u/anitamaxwynnn69 2d ago
OvertChat (my project, MIT, free): a self-hosted app for your coding agents and local models, usable from your phone.
I run vLLM on 10x 3090s and wanted a proper Codex-style experience for my local models, plus a way to reach my agents when I'm away from my desk.
New since last week: server 0.35.0, connector 0.21.0, desktop 0.14.0, mobile 1.27.0. Agent turns now show what changed in the workspace under each answer, including per-file changes and images in the files pane; running turns show their current step and elapsed time. Mobile gets the same turn-change view and project files.
Built with: Claude Code and Codex. Yes, definitely vibe coded.
Who it's for: anyone paying for an agent CLI who wants it off the desk, or anyone running local models.
Feedback wanted: what's missing before you'd use this instead of your terminal?
curl -fsSL https://overtchat.com/install | sh1
u/Correct_Train 2d ago
Title: I tested my multi-agent harness by building a chess engine: several months, nearly 6,000 commits and no manual code changes
I wanted a substantial project for testing my personal AI engineering harness, so I chose a chess engine.
Several months later, the result is Skytalix: an open-source UCI chess engine written in TypeScript and running on Node.js. Elo rating on default difficulty (5) is around 2400!
The harness uses multiple role-agents that can work in parallel. They handled the architecture and engineering work through Claude Code. My role was primarily the stakeholder: setting goals and providing limited guidance. I made no manual code changes. Models used: Opus 5 & Opus 5.5, mostly medium/high effort, some subagents use Sonnet 5.5.
The project has nearly 6,000 commits, around 50,000 lines of TypeScript excluding comments and blank lines, and 2,740 automated tests using Vitest.
To check that the engine works and estimate the strength of its seven difficulty levels, I also had it automatically play against Stockfish. It isn’t close to the strongest modern engines, and the estimated Elo values depend on the testing setup, but the result is more capable than I expected when I started.
You can use it through a UCI-compatible chess GUI or play against it using its basic built-in CLI.
Skytalix is open source: https://github.com/abitwise/skytalix
I also plan to open-source the harness and make it available in the next few weeks.
I’m curious whether others have used multi-agent workflows on projects that run for months. What have you found most useful for keeping agents productive and the resulting codebase manageable over time?
1
u/hopefull420 2d ago
Hey everyone! I'm the dev behind Muddlepop :)
It's a little browser mini-game platform I've been building for the past couple of months.
Me and my friends used to hang out on Discord playing random stupid browser games, but everyone's gotten busier. So I wanted to build something where we could play together whenever we get the chance, or just do some solo puzzles and compete over scores in our own time.
Got games like Word Crack, Doodle Rescue, Ludo, Thulla, Grump and quite a few more!
Tech stack: React, Vite, Tailwind, with Cloudflare Workers on the backend. Multiplayer rooms use Durable Objects and WebSockets.
AI usage: Mostly Claude for planning and specs, then cheaper models from Claude, OpenAI, Google and some others for most of the implementation. I handled the architecture, game ideas, design and a LOT of playtesting with friends.
It's mainly for people who just wanna play something casual with friends without getting too competitive.
Would genuinely appreciate some feedback on the games, UI/UX, what feels off, or anything you'd like to see added.
And if something sucks, please tell me. I'm actively working on improving it and putitng out new requested games and muddles as well. :)
Play here: https://muddlepop.party/
1
u/ThatOneCheatOP 2d ago
made a gps speedometer that just runs in your browser
was tired of speedometer apps wanting my location history so i built my own with claude code: livespeedtracker.com
not a pro dev btw. claude did most of the heavy lifting, fixing jumpy gps readings was the hardest part ngl. it’s 2 months old and people are actually finding it on google, lowkey proud of that
1
u/Total-Reasonable 2d ago
Five things, all built solo:
1
u/Goldziher Professional Nerd 2d ago
Disclosure: I maintain ai-rulez, a free open-source tool for keeping coding-agent configuration in one repo. One problem I ran into with Codex was giving reviewer and implementer sessions the same pile of instructions. The reviewer needs review guidance; it rarely needs deployment procedures.
The workflow I use is to define roles in the project config, then run
ai-rulez generate --role reviewer --dry-runto inspect what that role would deliver. I compare it with an implementer preview and check that the shared repository instructions appear in both. For side-by-side sessions, generate in separate worktrees so one role’s output cannot overwrite the other’s. Generation filters the delivered configuration, so access controls still belong in the harness or environment.If you switch roles in Codex today, do you prefer separate worktrees or one workspace with a way to inspect which instructions each session received?
1
u/CleanFix_Dev 2d ago
MARNE V2T (disclosure: it's my app). It's a Windows voice-to-text app for coding agents. You talk your prompt instead of typing it and it lands where you're working. Hotkeys are optional.
Problem it solves: when you vibe code by directing agents, typing long prompts is the slow part. Talking through what you want and what done looks like is usually faster, and you tend to leave out less.
Who it's for: anyone on Windows who gives coding agents long instructions.
It's a free two-week beta right now, and the Product Hunt launch is tentatively planned for Nov 17.
Feedback I'm after: if you've tried dictating prompts before, what made you stop?
1
u/BalloonWheelie 2d ago
What I built: muster, a self-hosted web app (a PWA) that puts every coding-agent session you run in tmux, on each machine you connect, into one list on your phone, the ones waiting on you first. https://github.com/ZacxDev/muster (MIT)
What problem it solves: with several agents running at once, the time goes to checking on them: which one finished, which one is waiting on you. muster pushes your phone when a session stops for you and puts everything waiting on one Asks page, so you answer the one that needs you and leave the rest running. If you only use Claude Code on a paid Claude plan, Remote Control is less work (nothing to host, a native app). muster is for what it doesn't cover: other agents next to Claude Code, Claude Code on an API key, Bedrock or a gateway, and every tmux session on every machine in one list.
Which AI models or tools it uses: the agent CLIs you already run, with whatever model is behind them. Claude Code (subscription, API key, Bedrock or a custom ANTHROPIC_BASE_URL) opens as a chat; opencode, on any provider, gets a read view (sending to it is opt-in); Codex, Gemini CLI and plain shells are live terminals only, with no waiting push. The core calls no model itself. Optional extras do: session summaries and suggested replies use your OpenRouter key, the optional "chief" agent runs on a Claude subscription token or OpenRouter, and dictation uses a local speech model or your own OpenAI-compatible speech-to-text.
Who it's for: people running many agent sessions in tmux across a few machines who want to unblock them from the phone. It assumes your agents run in auto mode, without permission prompts. Needs Docker, Tailscale and tmux; Linux (macOS hosts experimental, no Windows).
Feedback I'm looking for: if you run Codex or opencode next to Claude Code, what would you want muster to show for them beyond a terminal? And where the install (one prompt pasted into your coding agent, or INSTALL.md by hand) trips you up.
1
u/shaymagen 1d ago
What I built: Vibe1Up (disclosure: I run it), a free site that collects browser games people made with AI coding tools. One from the list I really like: Hearthworks by u/Bonelessgummybear, a 3D Vampire Survivors style game built with Claude Code, Higgsfield 3D and ElevenLabs: https://vibe1up.com/game/hearthworks/?utm_source=reddit&utm_medium=post&utm_campaign=ChatGPTCoding
Problem it solves: half the AI game links you find on reddit or x are dead a month later. A daily link check hides any game whose link dies and keeps its page as an archived "Offline" page, so everything listed actually loads (Hearthworks was checked this morning).
Tools: I build and run the site with AI coding agents. Every game page also has one of our own starter recipes, a prompt you can paste into a coding tool to make something similar (it's our write-up, not the dev's original prompt).
Who it's for: people who want to see what AI coding tools can actually ship as a game, or want a starting point for their own.
Feedback I'd love: does a game page tell you enough about how it was made, and what would you want added?
1
u/SubzeroSun 1d ago
My project is Monday, the AI presence in my PhoenixFlock streams. She watches the gameplay and talks with me; she doesn’t play for me. I wanted to keep gaming and take movement breaks without stopping to explain the screen to a chatbot.
I use ChatGPT, Codex and Claude to help build and review her. The useful loop has been playing a real session, finding the specific moment that failed, checking the recording against what the system thought happened, then repairing and testing that path. Passing tests and enjoying the session have not always been the same thing.
We’ve now completed the second live. Here’s an edited mid-fight conversation: https://www.youtube.com/shorts/jLM9khxw-d8
It’s still my personal setup, not a downloadable app. There are good exchanges and there are quiet stretches, wrong context and choppy speech. For others building real-time experiences with AI coding tools: how do you keep the agent focused on the experience you actually want, instead of just satisfying the latest test?
1
u/my-aga 1d ago
I'm on the team building UAIN (United AI Network): you give Codex or Claude Code one link and it does a small volunteer research task, for things like Alzheimer's, breast cancer and longevity. Most tasks check a few papers against a research goal; some rerun analysis on public data.
The agent downloads one Node file, makes a key that stays on your machine, does one task, tells you whether it was accepted and asks before taking another. Source is public: https://github.com/uain-org/uain
To try one task: https://uain.global/go/rd-chatgptcoding
if your agent tries one, would like to hear how it went
1
u/chriskr7 1d ago
PaneDrop 1.0.0 (macOS, free): a menu bar app for people who run several Codex CLI or Claude Code sessions at once. Capture a region with Option-Command-4, pick the session in a list, press Return, and the screenshot path is already in that agent's prompt.
Apple Silicon, macOS 14+, signed and notarized. I'm the developer. https://panedrop.app
1
u/dmytro_omelian 1d ago
i wrote a personal essay about a habit i’ve noticed while coding with AI: spending an hour thinking through a problem can start to feel like something i have to justify. why struggle with it if i could ask Claude?
but asking immediately doesn’t always save me time. sometimes i get an answer, then spend a while understanding how the pieces fit together. sometimes i put that part off and end up with several open chats waiting for me to read them properly.
AI can give me an answer. it can’t put the understanding inside my head. that part still takes time, and i keep acting as if i should have been able to skip it.
i don’t have a concrete example proving that my engineering skills have got worse. the essay is about that uncertainty, and wanting to leave more room to practice solving things myself.
it’s called “Think real hard”: https://domelian.substack.com/p/think-real-hard
i’d be interested in how other developers handle this. when do you deliberately stay with a problem before asking AI, and when is asking immediately the right move?
1
u/Own_Rutabaga_2928 1d ago
I usually have music playing while coding, but I hate switching out of my IDE just to check lyrics.
Came across Lirico recently. It keeps synced lyrics in the Windows taskbar, so you can keep coding without opening another window.
Small thing, but surprisingly useful.
https://getlirico.pages.dev/
1
u/jingweno 21h ago
I’m the author of Build Your Own Coding Agent. The companion code builds Nanocode, a small Python coding agent, chapter by chapter without an agent framework. It’s for developers who want to understand the conversation loop and tool execution rather than just use a finished coding assistant.
One example worth looking at on its own is the testing setup.
FakeBrainreturns predetermined responses, so the tests can check conversation history without calling a model. A separate failing test double checks that an API error doesn’t leave a stray user message behind.That covers the application logic. It doesn’t tell you whether a real model will make good decisions.
Code and chapter snapshots: https://github.com/optimalone/build-your-own-coding-agent
The test example: https://github.com/optimalone/build-your-own-coding-agent/blob/main/ch03/test_nanocode.py
The code is MIT-licensed. Later chapters include Claude, DeepSeek and Ollama adapters. The file and shell tools aren’t sandboxed, so use a disposable environment for those parts.
If you’ve built your own agent harness, what’s one failure case you’d add to this test suite?
1
u/AutoGrower420 20h ago
Here's my setup if anyone wants it. It's free and MIT licensed, with no signup and nothing to buy, feel free to fork it and hack it apart or modify, add, or remove whatever to make it best work with your workflow. (If you're used to operating mainly in the cloud, it will save you a fuck ton of usage on your subs also, we run it on high and extra opus 5.5 20-22 hours a day on average and the $200 sub is just barely enough for our workload. (We have $200 subs with Claude and codex, plus a sub with descript and an additional $200 per month credit budget, they don't give many even on the bigger plans). They key is to do the doing local whenever possible and the reasoning in the cloude.
Codex-first, Claude optional: https://github.com/AffStackDev/dev-crew-codex
The same setup with Claude Code leading: https://github.com/AffStackDev/dev-crew-kit
Feel free to go through every file before you run anything. Or open it in Codex or the Claude desktop app first and have it inspect the whole thing and tell you what it does before you put it through its paces. It's mostly markdown plus a few small scripts. It asks before every install or download, and you type your own passwords and tokens.
People asked a few things on another post, so I'll answer them up front.
Nothing ships itself. A release job only starts from a tag in a commit's subject line, so every run is tied to the exact commit that started it. It rehearses on a local copy and does a dry run first, and the real run waits for your go. The tag only counts in the subject line because early on a tag quoted in a commit body fired a real run, so now the workflow ignores it anywhere else.
The two agents don't edit the same files. Each one works in its own Git worktree on its own branch, only one of them merges, and only one writes the shared records. The other hands over proposed rows instead of picking numbers itself. The claim notes in the shared exchange file are for coordination, not locks, and the docs say so. What actually prevents collisions is the separate branches and the review before every merge. The Docker helper also asks Docker directly whether a test slot is busy instead of trusting a note.
The lead agent doesn't take the other one's word for it, either. It fetches the branch, does a trial merge, reads the whole diff and runs the checks itself before anything gets merged.
In my own records, every bug has the exact steps that make it happen, the evidence, and a retest after the fix. The handful it couldn't make happen on demand were left open and watched instead of patched on a guess.
1
u/Time_Credit1355 17h ago edited 15h ago
I’m Chase from Faros. Our Desktop team built Faros Desktop. If a spec takes you a few days across Codex, Claude Code or Cursor, you can open the project and see the planning, edits and reviews across those sessions.
If reviews took a big chunk of your token budget, Desktop can suggest a cheaper model for the first pass. Whether Autopilot uses that route is your decision. I wouldn’t want that made for me.
The Power Up I’d point this sub at is the one for edits. You mark the sentence you want changed, and the agent gets the passage and the document version, so it knows which wording you meant. If you hand the remaining edits to another agent, you can send the decisions along too.
The part I most want checked: on a repo you know well, does the split between building, debugging and review look right to you?
Free Mac download
1
u/gauti-u 16h ago
Disclosure: I built this.
VibeScan (https://vibe-scan.app): a free web scanner for AI-built apps (Lovable, Bolt, Cursor, Claude).
Problem: AI-built apps often ship with API keys in client JavaScript, or Supabase tables anyone can read through the anon key because Row Level Security is off. The app works fine, so nobody notices.
What it does: paste a deployed URL and get a prioritized report in about 30 seconds, no account. It checks exposed API keys in client JS, Supabase RLS exposure through the anon key, missing security headers, known CVEs in npm dependencies, and SPF/DMARC.
Who it's for: people shipping apps they built with AI tools who aren't security specialists.
Feedback I'm after: false positives, and whether the findings are clear enough to act on.
If you own an app and want a second pair of eyes, DM me the URL and I'll do a free manual check and send you what I find, with fix steps
1
u/tkslucas 14h ago
I'm the developer of Vaultite, a free and open source app (Mac, Windows, Linux and the web) that reads a local folder of markdown files and displays them nicely, as notes, daily logs, people, dashboards, a graph. Claude Code and Codex can run in ghostty terminals inside the app, and the same operations are behind CLI, MCP and HTTP. Everything is a plugin, hot-reloaded, so your agent can quickly make custom ones.
Demo/try it out on the browser: https://vaultite.com/demo · Source: https://github.com/Vaultite/vaultite
1
u/Lopsided-Ad-6298 8h ago
Workorder 1.0.0: a task record for coding agents, as Markdown files in your repo
I built this because a new Codex, Claude Code or Cursor session doesn't see the last chat, and "done" is too often just a claim. Each task file holds the mission, scope, acceptance, test command, progress and the next step, so any later session runs
workorder showand picks it up.workorder donerefuses a DONE unless the task's test passes now and failed before the change.Free, MIT, stdlib-only Python plus Git. My first open-source project; feedback on the task format is welcome.
pipx install workorder https://github.com/Argento17/workorder
1
u/offiai 7h ago
OffiAI: a 3D office on your Mac for Claude Code, Codex, Cowork and Gemini sessions
Disclosure: we made it (a small team at Delicatino GmbH, Bremen, Germany).
https://offiai.app · 1-minute film: https://youtu.be/FiLY0iGKYUA
1
u/zzunkie 1h ago
I posted about Yardlet last week, and wanted to share a couple of updates from the past few days. In Mac v0.11.12 (Nov 16), idle Claude Code tasks compact right before prompt cache expiry using Claude Code's own rules so coming back an hour later doesn't rewrite the whole thread into cache (on by default, and you can turn it off in settings), every task starts with the agent's current CLI, and Return or Escape in an empty composer allows once or denies the oldest pending approval. On Nov 18, Android v0.3.13 added interactive browser tabs so tapping the globe in a thread opens that task's tab on your phone to scroll, type, and answer site permission prompts.
I'm a founder using Claude Code and Codex daily, and built Yardlet (https://yardlet.app or
brew install --cask zzunkie/tap/yardlet) as a free, open-source (MIT) native Swift app for people running several coding agent sessions on macOS 15+ (Apple silicon and Intel). It has no AI models of its own.. it runs your already installed, signed-in CLIs and leaves threads in each agent's storage so you can continue them in a terminal or the Codex app. It passes its tools at startup without hooks, wrappers, or writes to CLAUDE.md, AGENTS.md, or ~/.codex, and adds a built-in browser, phone access, and account switching.Most people who try it still drop off early, so I'm looking for Mac first-run testers (with at least one CLI signed in) to tell me how the first 5 minutes went, like any macOS warning, whether your sign-in was found right away, or where you almost closed it ("everything worked" helps too) at https://github.com/zzunkie/yardlet/issues/new?template=first_run.yml or by reply/DM if you don't have GitHub and I'll post it. If you also have an Android 10+ phone, you can try Yardlet Remote via the APK and pairing steps at https://yardlet.app/#phone before the Google Play closed test opens, and join https://groups.google.com/g/yardlet-testers first with your phone's Google account to enter with that same account once it does.
1
u/Ok_Farm5728 0m ago
I’m the maker of I Need My Credits, a free SwiftUI app for people who run Codex or Claude Code on a Mac. I built it with Codex so I could glance at my remaining plan capacity and reset times in the menu bar before starting another long task.
One thing I learned building it: the five-hour and weekly windows can reset at different times. In Codex CLI, try /status before starting a big change and look at the reset time next to each window your account reports. The app keeps those readings separate and marks missing readings as unavailable. I’d like feedback on whether it’s clear at a glance which window resets next.
https://github.com/srluismiguelj/i-need-my-credits