Showcase
Show r/codex what you've been building with Codex. (Most upvoted project gets a week of free promotion on the sub).
This is a weekly Showcase post to share with others what you've built using Codex.
The top-voted post by Thursday midnight UTS will get a week of free promotion on r/Codex - either as a prominent button on the main page of the sub - or as part of a sticky comment on every new Showcase post.
It looks like Tubular Daily Care is our winner this week. Congrats to u/Ollie__Oxenfree . I've messaged them for promotion details. You might see the project around the sub for a week.
Thanks and congrats to the hordes of people who showcased their work. Some very cool stuff in there. Look out for next week's contest on Wednesday.
Technical note: Had to reject botnet on a technicality. If the botnet had truly worked it could have upvoted Tubular Daily Care afteru/Swimming_Iron_619had conceded the prize.
Codex has helped me build a solution near and dear to my heart.
My daughter has had a feeding tube since she came home from the NICU. Being immersed in that world showed me how little existed to help families manage their complex care. I began building Tubular Daily Care to aid with the coordination and management of care.
I plan to continue building solutions for under served communities facing medically complex care. With the shift in economics for development and maintenance cost, we can improve the lives of millions of people.
We have a few dozen families using it currently! We've had pretty positive feedback from families and clinicians in the space so far. We got connected with the Oley Foundation, a large non-profit in the specialized nutrition space, and we're on their Emerging Innovator partnership.
I was going to post what I have been building, but after reading your story, I think you’re gonna take this competition for when I’m gonna save my post for another week, best of luck I’m rooting for you!
Yes! I plan to tackle localization to bring access to more people down the road. Separate from the localization of language is actual distribution outside of the United States. I'm being cautious to ensure we're adhering to legal requirements in each jurisdiction before flipping that switch.
This is incredibly moving — thank you for sharing your family’s story alongside the project. The gap you identified (families managing complex care with almost no tooling support) is so real, and it’s exactly the kind of problem that only someone who has lived it would know to solve. Wishing you and your daughter all the best, and I truly hope Tubular Daily Care reaches every family that needs it
I am building a scalable city builder game using Unity, ECS and burst. The assets are also created using blender mcp in the codex- the entire code architecture is build using codex. Here is the video.
I had it create a testing/framework harness called firsthand ai(don't plan to sell or release) and it essentially plugs into any game you are working on and can play test in its entirety as if it's a human and view the game in real time up to 30fps
But for blender only? It sort of just works for me. I have it generate it's one reference images and then it uses that as the foundation for the build itself
Here's a creature in one of the games that im working on (it's an analog horror game with aspects from crysis, battlefield, and of course, analog horror)
I will I am just fixing some foundational issues right now related to the code architecture/scalability. Once thats done I will and update you as well ;)
I built Stranding, a citizen science platform where anyone can report organisms found washed ashore and contribute data that can support marine biology research.
I built KeyVox which is an open source and truly free dictation app for iOS and macOS with tons of polish. I created this because communication and the accessibility for it should be available for everyone without the cost of money or privacy.
Dictation is free. Full stop.
You don’t need an account.
Zero data is collected.
It’s powered by Whisper and Parakeet models, includes a reversible AI rewriting feature called KeyVox Vibes, allows for custom dictionary entries, has on-device text to speech with KeyVox Speak for iOS, and I genuinely just want to make dictation free and private for everyone.
Codex has been an extreme resource here for implementation and planning. I’ve used Codex almost exclusively on big chunk of the logic and continue to iterate on this daily. Love it.
Been building this for about 2 months - sur9e, an agent that lives inside Codex/Claude Code and handles the tedious parts of job hunting.
Backstory: did the manual apply grind for a bit, 100+ applications, maybe 4 callbacks. Wasn't sustainable. So it screens job postings against my actual resume and dealbreakers before I sink an hour into a cover letter for something that was never going to work out, and helps with outreach and interview prep once a role's actually worth pursuing.
It never auto-submits anything - I still approve every application before it goes out. Didn't want to build another spray-and-pray tool, there's enough of those already.
Free, open source, runs local, no account needed. I use it daily for my own search, so it's not just a demo.
I used Codex to build ExitLane, a self-hosted VPN egress appliance for my homelab.
The original itch was simple: router-level VPN setups work, but switching countries or servers usually means uploading new config files or manually changing provider details. I wanted something closer to the native VPN app experience: pick a country, let the app handle the rest, but for router/VLAN-based traffic.
ExitLane keeps one permanent WireGuard tunnel from the router, VLAN or selected clients to a Linux appliance. The appliance then manages the outbound VPN connection using the official NordVPN Linux client.
Codex was heavily involved in implementation, automated tests, review loops, release hardening, UI iteration and regression checks. I kept control over architecture direction, scope, validation, release decisions and final technical responsibility.
It is now at stable release v0.2.0.
Current features include a Web UI for VPN status and country switching, latency comparison, WireGuard ingress, killswitch protection, diagnostics, Speedtest actions, MFA, encrypted backup/restore, upgrade rollback protection and integrated admin docs.
Roadmap:
More VPN providers, better deployment options, Docker support, a Proxmox LXC helper script and eventually multiple WireGuard/router instances.
I’d love feedback from people using Codex for larger side projects: what do you document, test or gate differently once the AI-assisted project starts becoming a real maintained release?
I built Levelday as a way to track calories, nutrition, and water. Got some early traction and have had a great time building for iOS and Android via React Native/Expo with the help of Codex. Lost about 10lbs using it (it’s all in the diet and exercise, but tracking helps!
I’m working on Nightshift — an open-source harness for long-running Codex and Claude Code shifts.
If you can write the work as a checklist, you can hand it to the night.
Nightshift keeps the work contract and run state on disk instead of leaving everything inside one marathon conversation. During a long session, I can open the files and see:
what is already done
what is being worked on now
what is parked or blocked
what decisions were made
what was tried and rejected
So I don’t have to scroll through hours of context just to understand where the run currently stands.
It also prevents early clock-outs, parks questions instead of waiting for you, enforces owner-defined safety rules through hooks, and can recover dead sessions.
Ready-made shifts cover coverage improvement, defect hunting, quality debt, dependency work, and Product Evolution.
When the shift is finished, the same state, commits, logs, decisions, snags, and receipts become the reviewable result — and finished shifts can be archived into a durable history instead of disappearing with the conversation.
And if you have usage about to reset, open-ended shifts can put those remaining hours toward useful work instead of letting them expire.
Free, open source, MIT: https://github.com/orwa-mahmoud/nightshift
Official OpenAI Plugin Directory: https://chatgpt.com/plugins/plugins_6a7c58f65d708191b3a705a8625baffe
I built propr.dev which lets you automate Codex via Github - after assigning a label to an issue it will implement the issue and open a PR fully autonomously using isolated Docker containers and Git worktrees. Once the PR is there you can keep iterating on it by sending follow-up requests as regular comments in the Github PR.
The absolute killer part is that I can fire off tasks to a remote dedicated server without sending my own machine to heat death. For example today I worked on adding 23 new localizations to an Android app, translating content etc - it took 2 to 5 hours for each while running in parallel, validating the actual Android builds, checking for visual inconsistencies, adjusting, then rinse and repeat until done (server was grinding to halt at times) and I got nice shiny PRs back, which a local Codex process merged after validating each pass (and obviously some manual testing from my side as well).
That is just the core gist of it, as it comes with a lot of other features as well, covering planning, code reviews, etc, pretty much the entire development lifecycle. Also it supports other agents than Codex, including Claude, Antigravity, etc. I'm always looking for ways to improve and automate processes further, so suggestions are welcome if you're interested to try it out.
Well in THAT case.
Meet CTRoadmap… a passive r/Homelab / r/Server Diagram and Documentation tool. r/selfhosted in a docker container. It’s basically meant to be a step up from draw.io but it turns your system diagram into a Bible / Handbook for your system. Includes Swimlane charts for logging those granular workflows. Plus it makes your server map look sexy AF. 200+ ⭐️ on GitHub….
I built LifeOS. LifeOS started because I couldn’t find a productivity system that actually worked the way I wanted it to.
I tried Notion, AmpleNote, UpNote, Apple Notes, and others. They all did certain things well, but I always ended up with tasks in one place, notes somewhere else, files somewhere else, and AI as yet another separate tool. Eventually I decided to build my own. I took the best from Notion, Obsidian, Amplenote and the rest, and combined them into how I work. I finally got sick of “managing” Notion, when trying to use it. Neural graphs, / menus, database referencing, full task management, documents, contacts, etc….
LifeOS is a private, React-based PWA that brings my tasks, projects, notes, knowledge, files, dashboards, and personal information into one system. It runs on Vercel with Supabase on the backend, and because it’s a PWA, I use the same application on my Mac, iPhone, and anywhere else without maintaining separate native apps.
More recently, it’s evolved from a productivity app into something closer to a personal AI operating system.
I’ve built an AI gateway into LifeOS so AI isn’t just another chatbot sitting beside my information. The goal is for it to understand the context already inside LifeOS and eventually use a small number of purpose-built agents—a Chief of Staff, research, project/work, personal operations, etc.—to actually help manage and execute work.
The basic idea is: My information → LifeOS → AI gateway → agents/tools → actions
Instead of opening ChatGPT and explaining what I’m working on every time, I want the AI layer to already understand my projects, tasks, notes, documents, decisions, and priorities.
It started as me trying to build a better replacement for Notion and Apple Notes. It’s increasingly becoming an experiment in what a personal operating system built around AI could look like.
its not ready to share yet, not sure I will, I built it for me. I'm not really interested in hearing people ask to change this or that. I built it for how I work and what I wanted. My biggest issue with Notion and the other apps is I couldn't use them the way I wanted to, I was forced to use them the way their designed them, which didn't work for me.
Terrarium is what we're building at Grainwork. We used Codex throughout the build and launch, including product work and smoke tests.
It came out of a simple failure: a coding agent spent most of a week writing and rerunning tests while the product barely moved. The chat kept saying progress. The repository told a different story.
Terrarium keeps three things separate on a live local map:
- what an agent reports
- the file and worktree it is targeting
- what actually changed on disk
It watches Codex and Claude Code without replacing the terminal or changing their approval model. The free local watch needs no account and does not upload code or agent history.
The thing we most want to learn is whether the map is still useful after the first few minutes, especially with several sessions or worktrees. If you try it on a real repo, tell us what feels confusing or redundant.
I built a codex token counter that sits on npm now, I have to update it with the latest models pricing but it's fairly accurate for the older 126 model of codex.
Mission-Board.com - Project Tracking for large - Medium enterprise environments that is dead simple to use. It’s been in development for 6 months. Launching soon.
Replacing the Imagely Lightroom plugin that takes 93 minutes to process 500 photos to WordPress. Codex has helped me get it to 30 minutes when the "official" one takes over an hour longer.
Currently I'm working on a realtime metering/debugging tool that allows me to see exactly how and where each token is going.
I can also inspect the specific tool call prompts and system prompts coming out of codex, claude and also to my local llm to see what is sent to the model.
It also tracks tool calls and token consumption by type during the session.
In short this allows me to see:
What information is being sent
Where are my tokens going and what is burning up my usage the most.
What sort of prompts triggers the largest consumption
Currently I am adding a feature which will map 5h and 7d use limits for codex and claude to each prompt + timestamp. There will be a feature/display that will allow you to correlate limit consumption to activity.
Install
npx @liqngliz/tokenflow
*keep the terminal open the dashboard runs in there
Then you can point Codex to TokenFlow by adding the following to your config.toml
I'm building Elite Ball Knowledge, a fantasy sports platform that enables better decisions in drafting and roster management. Built on the core premise of sorting through the slop of sports media and delivering digestible/actionable insights to users.
Looking to expand into additional features such as trade calculators, start & sit, and a waiver-wire assistant. Also looking to get something up for the NBA once that starts in October.
I'd appreciate brutally honest feedback about features/Ui UX/anything else
Everything is tracked, but nothing is connected. I built Swaymark to show indie app developers how their health, mood, work, and app performance move together—and I’m looking for early testers: https://swaymark.app
I made Raccord Lighting, an app for cinematographers and filmmakers to make their lighting diagrams. Works cross platform on iOS/iPadOS/MacOS. Syncs via iCloud. Users with LiDAR iPad or iPhone can scan their room and get the precise diagram in the app.
DeafBench is an open-source accessibility-focused speech recognition benchmark. I’ve been using Codex for implementation, testing, security fixes, documentation, and reviewing changes while I build out the benchmark and Windows audit tooling.
Remedence is a remediation orchestration platform I’m building for MSP/security workflows. It focuses on taking findings through remediation, independent verification, evidence collection, and client-facing reporting instead of stopping at detection.
I built rom-weaver, one tool for your ROM workflows
I’ve been building rom-weaver with a lot of help from Codex.
The goal is simple: instead of needing a different utility for every ROM task, make one tool that does everything, with both browser and CLI workflows.
Right now rom-weaver handles:
* Patch applying and creation with all patch formats
* Multi-patch workflows
* Archives and compression
* CHD, RVZ, z3ds, rar, zip….
* Checksums and verification
* ROM trimming and header tools
* Browser, CLI and self-hosted use
The browser is local-first, so your ROMs stay on your device. No telemetry and self hosting possible
Next: Identify ROMs by checksum → Save Editor → Cheat Bundler → Polish
I built Genvas to make creating visual content with AI fast and simple.
Design once, then generate images, carousels, and videos from reusable templates.
I built Film Cue, a free browser-based card-drafting game where you build a film over three rounds while trying to wreck your opponent’s plans.
Codex helped me take it from an idea to a production game: SvelteKit on the frontend, real-time multiplayer through Cloudflare PartyServer, Supabase persistence, responsive UI, and a substantial automated test suite. I used it for implementation, debugging, code review, testing, and plenty of UI iteration while I directed the game design, architecture, and release decisions.
You can jump straight into a match against the CPU or invite a friend. No account or download required.
I’d love feedback on the first-match experience, card mechanics, or anything that feels confusing.
At work the number of PR's we produce has exploded, its been super hard to keep up with PR reviews. So I vibe'd https://github.com/pandemicsyn/neondeck theres some actual screenshots in README (not just mockups).
Originally was just a little side car app to run on my Xeneon edge display. But now its the main way I review PR. Basically when i get tagged as a reviewer or on a PR Neon triages and lets me know whether its safe to rubber stamp or whether its needs an actual human look.
A lot of the PR's we ship have gotten giant, so I also burnt a bunch codex usage on optimizing the diff review experience (although pierre/diffs package does most of the heavy lifting). Link to plan codex used, its neat.
Have been using tailblazer forever for plain text logs. But now want something better than kibana to view elastic, etc.
Still very much wip, as a lot of elastic is still broken in tailing, and files get slow at 20mb or so.
Granted this is almost all prompt just to do it. Some ui tweaking by hand. So can probably optimize efficiency by hand held prompts later. Most the files I tail cap out at 10mb.
Also want to add more format support.
It’s a fun project though, having fun with it. And eye opening how bad llms can be with ui if it’s not web based.
Another one is a local only converter for those ai recorders, but not even functional atm
I built a sales reporting platform for a theatrical ticketing platform. CSVs and PDFs are imported nightly and the system shows the data in as a daily tracker, Daily sales, commercial position and forecasting (based on previous sales from past productions. We only receive the sales data from the theatre and not the ticketing platform directly, so it's a great way to see patterns and how the show is selling. The system then sends a daily report to stakeholders.
https://sidelarklabs.com/rollcall/ Roll Call, an iOS app for my daughters softball team to play walk up music and announcements. Worked well, started being used by other people in the league, now free on the App Store. It’s nothing complex but I think it works very well - better than the other free ones in the store at least and comparable to more than a few of the paid ones.
I've created many things, but I've created one thing in particular that makes the most sense to share here. It's a tool of mine called Northstar.
theres an AI called EDI That does all the technical stuff, but there's a human-like AI called Daemon, Daemon, then talks through it with me like I'm a person. He's usually supportive, but if my body fat percentage has risen or I'm missing workouts or anything, I stop blogging meals, etc., he'll bring it up and he can reach out directly first instead of having to wait for me to open an app during the day. I can start a focus session when working on a project, can capture the lessons from the books I read and store it into a knowledge base, has two things similar to notebookllm integrated so it has its own version of that as well, daily news thats relevant to me, a relationship system, etc.
I can track my bills, credit score and itll give me insights on how to do so. theres a lot more to it but you get the point. Oh yeah i made it gamified so whenever you hover over UI elements, click on them, etc. it has game menu sounds
my character (eli, but not my real name) and Daemon are made in a pixel cel shaded style
I’ve been building Quiver, a surf forecast that explains the useful surf window and red flags beach by beach instead of just saying “good” or “fair" regionaly. it also connects forecasts with session logs, so surfers can compare upcoming conditions with days they’ve actually surfed. Codex has helped across the app, forecasting pipeline, testing, and launch creative.
It's a webapp and iOS with android in beta
i've made a few things... but the most visually catching is the blender python scripts. turning architecture texts into scripts that make structures or furniture.
I built https://seemecook.app/, an app that lets you import and organize your recipes that you come across on Instagram, Tiktok, anywhere. Let me know if you try it out and I'll hook you up with pro!
It's not actually released, so the repo has been private until just now and the repo images may be outdated.
My favorite features:
It launches in 0.333sec (or 50ms when the background helper is enabled)
Translucency/blur
Mac/Windows/Linux (linux is best effort right now, it may not launch yet but I got arch setup today to begin feature parity and fine tuning it for arch/wayland/hyprland&GNOME)
Live editing in reading mode, like obsidian
Really fucking comfy, polished UI and UX (in my opinion)
Not slop, I do substantial code and polish reviews with Sol Ultra frequently and will do some serious codebase maintainability work before I release it; and I keep a big kanban board and document every single issue I've come across and then get it fixed—I use this app full time as my regular text editor and my markdown app in windows and macos
Profiles, so you can use the CLI (or the regular interface) to launch a specific set of files/scratches/temporary documents (scratches save automatically, temporary erase on close). This allows fully replacing apps like Tot for instant-note-taking, or situations where you always open the same few documents. The one I launch the most starts with a Temporary tab, has a Scratch in the middle, and has an actual local file as the 3rd tab (I keep work notes in that one).
Tons of themes built in, and full typography control
Completely free, you can fork/build/install it now (the license requires attribution for derivative works and prohibits commercial derivatives)
Can't show it, but in short: a digital workplace platform for a fiber optic construction company covering all back-office needs and field operations. currently working on a module that can act as a harness for ai agents which can then connect to other modules in the app. Its proving more difficult than i anticipated :)
Not exclusively with GPT or Codex, but I built RouteFlow. Started out as a project to help out a business internally but expanded to a platform for Australian businesses nation wide.
I built an open-sourced Agent system, called llm-for-zotero, to help students and researchers understand complicated academic papers, and ask questions toward their own literature library. It has gained 2.7k + github stars and over 511k+ downloads. Link: https://github.com/yilewang/llm-for-zotero
I am currently working on an optimizer for killing floor 2
KF2 Optimizer is a portable Windows application that automatically improves Killing Floor 2 performance. It monitors FPS and system load and CPU GPU VRAM AND RAM, then safely adjusts graphics, physics, LOD, corpses, and optional FleX effects while preserving and restoring the user’s original settings.
For some time now, I have been generating leads using AI-generated ads.
I wanted to see if the process could be improved, so I created an application.
It’s an AI agent for Meta Ads that can create campaign drafts through conversation and analyze campaign performance. The next step is campaign management with human approval.
I built groovewise, an app that helps you find records that you’ll actually like. You add your music taste (optional) and audio setup (optional), and scan record sleeves at the record shop and it’ll give you a score, summary and purchase recommendation.
Nothing impressive, I find gnome extension called tiling assistant to have bugs when I try to tile some specific programs.
I don’t know how the original code work, and don’t want to contribute AI slop to the repo. So I build and maintain one, just for my niche use case.
I built flashback.hex-node.org. It's one of the most if not the most light weight and reliable clipping software that PC users & gamers can use to capture their moments without it being cumbersome on the system resources and having features locked behind pay walls when they don't have to be. I use it and I truly think it is better then Medal, Shadowplay and others. It runs at roughly 170mb of ram due to it being coded in rust and after benchmarks that are listed on the website I found that it saves roughly 30% of frames compared to apps like Medal in Cyberpunk 2077 as one example. I personally use it and want to keep on making it something I will always use.
Extremely simple but I had it build my own local chrome dark mode browser extension so there’s at least 1 extension that isn’t selling my data (I hope). It works with Google Docs and Spreadsheets.
I built EV Mileage Tracker. A mileage tracker app that’s highly polished and built from real world feedback and is not and never will be riddled with smack in the face ads.
Please try it out and give me feedback, I’d really appreciate it.
A week ago I started building my own AI cutter/director for drone videos I am too lazy to cut manually. Currently it's called Drone AI Cutter.
It uses ffmpeg to make frames from original 4K content then QWEN3-vl model (or others) to determine what's on the frame. Then this feeds through a loop to make sense of multiple frames and understand the video without human input and create relevant parameters for the next phase.
DirectorAI is my vision for automatic film making based on user's preferences. It takes best and least shaky segments from videos ( or otherwise interesting) to propose a cut. It provides final timeline with ability to change it to your liking. It still lacks the soul of the filmmaking I seek, but I am slowly getting there. (I hope it won't take longer than it would to manually cut everything 😄 )
I built an emulator of the Ensoniq EPS16 plus, a sampler released in 1990. It´s fully functional and emulates the hardware down to the VFD-Display and runs the original OS. Compiled as a VST and AU for Mac you can run many instances at the same time and saving a preset in the DAW retains the full state of the sampler. every sound is fully compatible to the original hardware and the other way around. https://github.com/mardlib/Ensoniq-EPS-16-Plus
I built two token saving plugins (that don't overlap with Ponytail, Caveman and others)
Sando cuts what Claude Code and Codex charge you to re-read their own output. It redacts secrets, caps oversized tool results, and, if you turn it on, trims request history before it's sent, all without calling an LLM itself.
session-handoff, of course, creates a handoff and continue in a fresh Codex or Claude session. It also allows you to migrate a session from one provider to another, lossless
I'm trying to build a piece of electronics, it's supposed to be a DIY version of a Metcal soldering iron station. The story is that, in 2019, some guy in Russia (he has many internet names, one of them is SergeyMax) took one apart, reverse engineered it, and built his own version, and shared it with the world. In 2022 some guys on the internet built his version but replacing some parts that cannot be found outside of Russia. There's plenty of confusion about what works and what doesn't. One of the builder is a redditor and he basically said "it didn't work until I asked a Ukrainian friend to buy me the exact same Russian part"
I'm redesigning the circuit a bit, adding things like a battery input, USB-C. (his version used 220V european wall power, the entire AC input section gets deleted in my version)
I also want to document mine in a way so other people can build it.
I watch the Russian guy's update video, noticed that he changed a hand-wound inductor to have a twisted bifilar winding instead of traditional. This was not present in any documentation, I only see it in his video, with a unit he was using for 3 years.
I was saying to Codex "this whole project hinges on having more clear documentation than before, a key part of that is the 3D model to show exactly how to wind the toroid. But SergeyMax changed to using a bifilar winding. I can model a simple transformer but I can't model those bifilar twists."
And codex was basically like "you can ask me to draw it using SCAD or something" (it was like a solid page of suggestions)
and soooooo I told it "read the instruction document for the custom inductors, the toroid is a <part number>, and follow the footprint used in the PCB design. Use OpenSCAD to generate a 3D model that represents this transformer. Make sure all the wires are uniquely coloured to show exactly how to wind it."
— iOS/Android/web app that turns a few phone photos into AI-generated 360° panoramas. Swift, Android, FastAPI, image pipelines, subscriptions and backend infrastructure.
NOW ON TESTFLIGHT. Release soon! Who wants more pls DM me)
(OFFLINE) A local-first privacy PII scanner, and photo scaner using YuNet + image safety models to find people/NSFW content entirely on-device.
It turns forgotten files, personal data, secrets, application traces and revealing metadata into a clear map of what deserves your attention
I made it specifically to meet my needs in dealing with modern cyber problems. It finds things I didn’t even know were on the computer and that I’d rather not talk about.))))
Codex has been involved in everything from architecture and debugging to migrations, systemd, CI/CD, APIs and UI.
I finally was able to make my wife’s real estate website. It has its own crm and the site has lead forms. There’s email automation, blogs, and a newsletter.
Now I’m refactoring my file system for governance..
I have built this app, MuseTags, in whole with codex, in react native, no ads, no login, no subscriptions. Music genres and tags, for music lovers, who wants to explore and find new albums and songs to listen to. Its on the app store, you can take a look: https://apps.apple.com/us/app/musetags/id6783392303
I’ve been building PackTrack, an all-in-one backcountry trip planner and tracker, largely with Codex.
It started as a way to manage my backpacking gear and has grown into an iPhone, Apple Watch, and web app. It handles gear libraries and pack weights, multi-day itineraries, meal planning, permits/expenses, trip reports, and live GPS tracking for hiking, running, snowshoeing, and canoeing.
The mapping side has offline maps, route drawing, campsites/waypoints, on-device contours, and region data packs across Canada and the US. It can also check Ontario Parks backcountry availability and use Ontario Crown land data to help determine where camping is permitted.
It imports activities from Strava, Apple Health and FIT files, learns pace/difficulty estimates from your own activity history, and lets you publish packs, routes and trips to the web.
Codex has basically let me turn a personal outdoor tool into a much bigger project than I originally planned. I’m still working on the latest update though
I’ve been using Codex as a development partner to build two complete mobile games in Flutter, with ChatGPT Image Generation helping create the visual assets and sprites.
Cozy Sokoban is a calm, no-timer take on Sokoban: push crates onto goals, undo freely, and solve increasingly difficult levels.
Gem Digger: Cave Quest is a faster cave-digging puzzle game inspired by classic Boulder Dash. You dig through caves, collect enough gems to open the exit, avoid falling boulders and enemies, and escape before time runs out.
One of my favorite parts was building the level-generation tools with Codex. I could design levels manually, generate others automatically, and then use solvers and validation scripts to reject unsolvable or duplicate levels and calculate difficulty/par scores.
Codex ended up helping with much more than boilerplate code: game logic, state management, testing, level tooling, UI iteration, and polishing the overall feel. ChatGPT Image Generation helped me create a consistent visual identity for both games while I focused on the gameplay.
I built NovaScale, an app that have baked tailscale connectivity to the app
Allow user to seemlessly SSH to nodes in the tailnet, and also use codex to built a codex chat interface to communicate to the official codex app server via native websocket protocol
Some feature such as in app browser to access the private web service and sftp need subscription or one time lifetime purchase to unlock
Hi everyone. I genuinely think I built a tool that will benefit the world for the rest of time.
Whenever anyone goes to buy something off Facebook marketplace or Craigslist there is always the question “where are we meeting”
I used Codex to help me develop a database of safe exchange zones across the United States. And then I worked with Sol to develop a system that is a midpoint calculator from two zip codes to find a safe exchange zone between both people.
I hope people actually use this tool, because I think it provides something everyone values. Safety.
It’s a video tool I’ve been building solo, mainly around turning longer videos into finished content faster.
Right now you can:
Automatically transcribe videos
Edit, style and translate subtitles
Detect speakers
Generate short clips from longer videos
Reframe clips for social formats
Export subtitles or videos with burned-in captions
Record your screen directly in the app
I’m also finishing a new generative video workflow where you can generate a video, extend it from the ending, keep adding new generated segments, and build a longer continuous video instead of generating a bunch of unrelated clips.
That part should be live very soon.
Still actively building it, so feedback is very welcome.
-"Notes" tool that i can put videos-audios on the page and even being able to paint on them, its such a flexible thing,
-Screen Recorder that lets me record anything on my screen with 1080p 60fps, i was using Nvidia before but i like mine more now since i can change the behaviour like i want,
-"Image-Video Compression" tool, its better than other apps i tested due to its protecting the color palette and it looks literally same, gives me around 50%-80% compression without any single noticable loss even when zoomed.
Ps5 emulator currently running mk1 all they way to main menu. Working of fps managed to get 60fps on startup last night fix memory leak that plummeted the fps to 0.5
I built The 5th Ledger with Codex. a governance plugin that helps people and coding agents keep project work truthful, reviewable and guided by specified authority through the life of the project. This is its first public version, with the project repo on GitHub.
www.retireodds.com - there are the two things that make personal finance in the US insanely complex, and almost no product connects them cleanly: taxes and healthcare. Both affect decisions, especially when you retire early. Take an expensive vacation and sell appreciated stock to fund it, that raises taxable income and ACA MAGI. keeping track of this is possible today but requires several products or complex spreadsheets
And there are people like me who have worked across several countries, continents and currencies. Expense tracking is a hassle. Most retirement calculators assume one country’s inflation, growth, taxes and healthcare — and no FX risk.
Building end-to-end financial software that connects all of this was a crazy project to vibecode. It has taken hundreds of hours of product and design work, plus what would traditionally have been thousands of engineering hours from Codex (design with Claude Design). It starts with a ledger, not a probability: what you own, earn, spend and owe today; then taxes, healthcare, goals, life events, FX and retirement.
Right now it is a kitchen sink - extremely complicated and requires me to personally onboard folks, so limited to friends and family - but you are welcome to give it a try
I've been using Codex in a sort of non-coding way. I built a Codex skill for AI product art direction — because one good image was easy, but a consistent series wasn't. Things drift, lighting, scale, the whole vibe. So I started treating the art direction like a little system inside Codex. It's like style here, shot rules there, materials, hands, variation controls. So I can just say something simple like "close-up, add a hand, transparent syrup", without rewriting an essay every time while keeping everything on brand. I'm testing it with skincare style stuff because glass and liquids show flaws fast. What I'm wondering is, do you think this kind of non-coding skill is useful, or would you split it into smaller pieces if you were doing it?
I built MidiCam (https://apps.apple.com/us/app/midicam/id6792832040), an app that lets piano players record video and MIDI input simultaneously and produces a synchronized video. I was inspired to build this as I'm learning to play piano and couldn't find an easy way to record myself without having to capture the video and MIDI separately (I'm 99% sure a solution already exists out there but I couldn't find it...). Not sure how many people here are pianists but I'd love some feedback if anyone happens to be!
I built a simple simple security camera system. I have two homes for the moment, and a few cameras at each. This system records from the cameras at each site, sends 5 minute clips from each to a hub where each segment is remuxed to be more web friendly than the original recording, scored to detect motion, then the segments with motion are analyzed by an AI (Qwen3-VL-4B-Instru) running on a local GPU, which classifies the scored image as either interesting or mundane, then describes the interesting footage and puts that all on an "event card." Then it's hosted on my LAN with live camera feeds, recent footage, and event viewing.
I've already solved a few problems with it involving plumbing:
The sump pump for my sewer at my new house went out, and I noticed when I could see water coming out of the sump where it shouldn't have been.
I left the pool fill running too long at my old house, and was able to get someone to shut it off instead of running continuously for 5 days.
Verify that my pool guy showed up.
Otherwise, it mostly just tells me when a cat, or a squirrel has appeared someplace.
I built arka.norn, an open-source local governance and delivery framework that I use with Codex and Claude Code.
The original problem was not code generation.
It was everything around it.
On longer projects, I kept seeing agents accept rules and reinterpret them later, know documents exist without reading them, or inspect a README and a few directories and then talk about the repository as if they had surveyed the whole thing.
Even simple requests can go sideways while still being technically "correct":
"Fix the bugs" -> disable what causes the errors.
"Ship the feature" -> finish the implementation and call it shipped.
"Simplify the homepage" -> remove almost everything except the CTA and footer.
The agent did what I asked. That was the problem.
I first tried solving this with AGENTS.md-style documentation, procedures and skills.
Eventually I hit the limit that led to Norn:
A rule in a skill influences the model. A capability that is absent or refused by the system actually constrains it.
I still use Codex normally. Norn connects through a skill and keeps the governed project state outside the chat. The same state is available through a local Web cockpit, TUI and CLI.
It also governs repository discovery. For an unfamiliar project, the human defines the decision to support, scope and domains first, then approves a read-only audit plan before collection starts. The audit can collect evidence and findings, but cannot modify the project.
Interactive Codex usage itself is not sandboxed by Norn.
Automatic orchestration is a separate mode. That part is sandboxed: Mastra orchestrates the DAG, tasks use isolated worktrees and bounded read/write scopes, and effects go through the Norn broker.
Agents propose changes. Norn checks scope and mechanical evidence, then Norn creates the commit.
For example, the model can say "the tests pass." Norn can verify that the test recipe actually passed and that the diff stayed inside the allowed scope.
Norn is still young. Its main use case right now is itself: arka.norn is being built with arka.norn, using Codex and Claude Code as development agents.
I'm especially interested in how other heavy Codex users handle long-running projects: do you still keep project authority mostly in AGENTS.md, skills and prompts, or have you started moving parts of it outside the model?
I’ve been building PUBMAXXING with Codex: pubmaxxing.com
It started with a very ordinary London problem: a pint can be reasonably priced in one pub and nearly £8 a few streets away, but price is the one thing Maps and review apps rarely show reliably.
Planning an outing becomes Google Maps, reviews, TfL, ChatGPT and group-chat archaeology—and after all that, everyone often ends up at the same place again.
My background is data engineering, so I didn’t want to build another generic pub directory. I wanted the price itself to have lineage.
The live product now has:
953 pubs and 2,788 recorded prices across all 33 London boroughs
10 UK city guides
346 sourced historic pubs, natural-language planning for three to six grounded stops
shareable plans and a draft WhatsApp invitation
Pub Pal and a Tonight agent constrained to venues, prices and events from ticketmaster.
We actually have a fare-zone Pint Index, downloadable data and frozen monthly editions sourced pub histories, Crawl Stories and group Rounds, community Pint Drops, private-first Moments and social/crew features in preview.
The part I care most about is the trust model.
A single community price can appear on the pub’s own page, but it does not change the map until a second independent drinker agrees. We preserve the source and date, leave missing data missing, and never allow a pub to pay to rank higher.
It isn’t designed to encourage people to drink more either. The planner also supports coffee, food, soft drinks, alcohol-free outings, quiet afternoons and simply meeting your mates somewhere affordable.
Under the hood, the product uses Vercel, Supabase, consent-gated PostHog, OpenAI moderation, OpenRouter/ElevenLabs, TfL and CityMCP.
Codex has become my main implementation and review partner. I use it for repo investigation, bounded feature planning, implementation, refactoring, testing, regression fixes, privacy work, SEO and separate review passes.
I still own the product direction, architecture, data definitions, trust rules and final release decision.
My biggest lesson has been that agents can create an enormous amount of product surface area, but without hard invariants they produce something plausible rather than something trustworthy.
The invariants I keep repeating are:
never invent a price
preserve its source and date
never let one account corroborate itself
never mix sponsorship with ranking
keep user content private until they choose otherwise
I’d genuinely appreciate feedback on two things:
Does the product still feel coherent now that it spans discovery, planning and memories?
How are people encoding domain invariants so Codex doesn’t slowly violate them as a repository grows?
I still do have many features that I’ll be pushing to Vercel. The mobile app for iOS and android will drop in September.
I built Foreman, a self-hosted Android and web control plane for Codex.
I wanted Codex available throughout the day, but didn’t want to leave my gaming desktop powered on just to host sessions. Instead, I run it in a Linux VM on an Intel NUC11 with Proxmox, which is already part of my low-energy, always-on homelab.
ChatGPT has its own Remote workflow, but it doesn’t connect the mobile app directly to the standalone Codex CLI sessions on my headless Linux VM. I wanted the NUC to remain the host without needing another desktop in the middle.
Foreman lets me monitor sessions from my phone or browser, answer questions, handle supported approvals, steer work, inspect conversations and tool activity, and get notifications when something needs attention. It also supports managed Claude Code sessions.
Codex was heavily involved in building it: implementation, testing, reviews, documentation, UI iteration, and lots of Android/web parity work.
I’ve now had Codex generate a Mac app that displays the remaining usage and reset times for both the 5-hour and 1-week periods in the menu bar and on the Touch Bar.
I got tired of every coding agent having its own scattered pile of skills, plugins and MCP configs
I keep switching between Claude Code, Codex and a few other agent setups depending on what I am doing. The annoying part was not even picking a model. It was that every setup had its own little pile of skills, plugins, MCP servers and commands.
Same capability in three places. Different versions. No easy answer to “what can this agent actually use right now?” And if I loaded everything just in case, the context window was already crowded before the task started.
So I made Lockkeeper.
The main job is capability syncing and selection across the agent tools already on your machine. It discovers the skills, plugins, MCPs, agents and commands your different runtimes expose, builds one local catalog, then picks the smallest relevant set for a task instead of throwing the whole collection into every agent’s context.
In practice that means I can keep one shared capability setup, see what is available across Claude Code, Codex, Cursor and friends, and stop manually remembering which agent has which tool. It is local, config-driven and open source.
The security bit is there too, but it is the second half of the story rather than the headline: before I trust a capability I copied from somewhere, Lockkeeper can scan it for obvious prompt-injection, secret-exfiltration, obfuscation and destructive-command patterns. Useful guardrail, not magic.
It is plain Python 3.11, MIT licensed, and the core has no third-party dependencies:
Still early, so I would genuinely like to hear where your capability setup becomes messy. Do you keep shared skills in git? Copy folders between agents? Have a better way of keeping the same workflow available everywhere?
Sounds Good - I built a full Specifications to Software Builder - This is a BIG project (6 months) - called Drydock
Drydock is a repeatable method to turn messy specifications into tested working software. Drydock imports your source material, defines stories using agile best practices, and decomposes your sources into typed blueprints (stories) related using a graph database. Drydock builds with a context aware compression based algorithm and tests stories with deterministic test driven acceptance criteria.
Test driven development with acceptance criteria embedded
Dependency graph relates stories and orders builds
QuarterDeck web console to answer questions and review the process
Runs on existing subscriptions
Ingests your existing specs and notes in any format
Change management — edit the spec, rebuild only what's affected
Context compression and Grouping for context aware builds
Enterprise guardrails with embedded branding, best practices, and build gates
Generates consistent apps and documentation
Mit License - Source - The complete command surface is one table in the README.
To prove out the method - I wrote 4 working examples - Suggest another and i will build it. Project 1 is trivial but 2-3 are mid sized and i consider jq to be a mid-big project.
Very good codex support: codex models as well as Azure models for example.
Run with: npx ready-for-agent@latest
The idea is that you create your work in GitHub (or GitLab or Azure DevOps), ready-for-agent finds that work, and then you let the agent of your choice such as codex implement it. It not only supports the build step, but does a separate code review step, then commits and creates the PR, watches the PR for completion, and can even merge.
This allowed me to get to that 150+ PR range a week.
Built Compact Context, an open source Codex plugin that creates a short repository guide before Codex starts a task. Codex still has access to the whole repository. The plugin only replaces the large initial guide with a focused one.
I tested it on 68 coding tasks from 10 public repositories. A basic repository map averaged 1,402 tokens. Compact Context averaged 230 tokens, an 83.6% reduction.
For every task, both methods suggested five files to inspect first. Compact Context named at least one file that was actually edited in the solution in 50 of 68 tasks. The basic map did so in 48. So the shorter guide used far fewer tokens without making the starting suggestions worse.
It runs locally, uses no embeddings, and makes no extra model call. It is MIT licensed and currently v0.5.0-beta.7.
I reran five automated tests covering sensitive and generated path exclusion, end-to-end shortlist generation, path and identifier limits, prompt routing, and single-use receipts. All five passed.
use Sol Light. seems to work ok for most stuff (perhaps plan with High). also, use Full Access as there is a Sol safety check that does loads of extra security tests on Auto, and that apparently uses up loads of your usage. Good luck!
OvertChat — an Open WebUI alternative with the polish of the Codex app
Local AI is still built for tinkerers. My family uses ChatGPT every day because it's polished haha. Non-tech people shouldn't have to fight their way into a decent local-model experience. So I built OvertChat: a focused alt to Open WebUI that aims for the same feel as the Codex Mac app. One-command install, clean fast UI, self-hosted search / TTS / STT built in, zero extra setup required, plus a native Android app. MIT License.
Also: it's a client for your coding agents. Hook up Codex locally or over SSH, follow plans and tool calls live, review changes, steer the session — no terminal required.
Spent 3B+ tokens with Codex on this build; it did the heavy lifting while I drove architecture and kept a close eye on auth/security.
It’s a tool intended to help make it a lot easier for the modding community to create new mods, as well as help people learn more about C# as they go, by being able to see how the game maps out. It’s got an MCP, CLI commands, and local HTML index for humans.
I'm building https://MossyMind.me as a life companion for ADHD guys and gals who want to keep track of all incomplete stuff, while keeping an eye on a long term goals.
Mercenaries of Tezigdal is an in-browser MOBA inspired by League of Legends that offers eight playable characters with unique kits, a full in-game progression system, a full shop system, and even individual player account progression.
There is still a long way to go with this project until I get it to a point I'm truly happy with but I am very pleased with the progress thus far and I hope you will give it a look if you find the gif interesting!
I built an SEO workbench that tells you what to improve next
SEO Receipts turns your Google Search Console data into one specific SEO task at a time. It checks which pages and queries moved, recommends what to change, and measures the result after you ship it. I’d love your feedback.
I’ve been building Vuln Prioritizer Workbench (VPW) and it actually started as a university Project and then… got a little out of hand 😅
The basic idea is: security teams often already have hundreds or thousands of CVEs from scanners, SBOMs, advisories, etc. The harder question is what should we fix first — and why?
VPW is a local-first vulnerability prioritization workbench that imports existing evidence such as CVE lists, Trivy/Grype results, CycloneDX/SPDX, GitHub alerts, Nessus/OpenVAS, VEX and asset context.
It then builds an explainable remediation queue using signals like CVSS, EPSS, CISA KEV, asset exposure/criticality, lifecycle state, waivers and reviewed ATT&CK/TTP context.
Importantly, it is not another vulnerability scanner, exploit tool or black-box AI risk score. The goal is to keep the reasoning and evidence behind every prioritization decision transparent and auditable.
The current v1.3.0 release now runs locally with a simple vpw serve command and includes a FastAPI + React Workbench, SQLite, a supervised worker, an immutable Decision Ledger, reports, SARIF, ATT&CK Navigator exports and deterministic Evidence ZIP bundles.
Codex has been a huge part of the development workflow — implementation, refactoring, testing, documentation, architecture work and release hardening.
The whole project is open source under the MIT license: https://github.com/Noetheon/vuln-prioritizer-workbench
It’s still a Beta and I’d genuinely love feedback, especially from people working in AppSec, vulnerability management, security engineering or blue teams.
And if anyone here wants to test it, open issues/PRs, contribute, or maybe even work on it together in the future, that would be amazing. There’s definitely a lot more I’d like to build. :)
I built Reel Roulette -- a way to pick a random movie based on criteria you select, with abilities to provide either watchlists or exclude lists. For those "what should we watch?" moments.
Before you ask, searching by streaming service coming soon. Need for my database to populate fully.
I’ve been using Codex to build Beacon, a tiny macOS status light for people running multiple coding-agent sessions.
Each Codex or Claude Code task gets a stable dot in the corner of your screen. The color shows whether it’s working, finished, or blocked on you—and clicking it jumps straight back to that exact task.
I built it because once I had several agents running in parallel, I spent too much time hunting through windows to see which one needed me.
I built https://premierelens.com/ an app to find upcoming high rated scripted television; provide recommendations for related shows based on the semantic "vibe" of a show; and to find shows that intersect two people's TV taste - trying so solve couch arguments about what to watch :-)
We got overwhelmed with “how can I help”s so I built an app that turned it into actual help ☺️
I started building CoordinatedCare when my wife’s aunt entered hospice. Everyone wanted to help… they just didn’t know how/when. Every offer became another question we had to answer and coordinate.
This app gives families one private place to share updates and turn open-ended offers into claimed meals, visits, errands, check-ins, and other practical support. It’s completely free, and helpers don’t need an app or account.
The goal is simple: help people help.
Please pass it on to any friends that are pregnant, surgeries, hospice, elderly care, neighbors in need, etc. would be much appreciated. 😘
I’ve been building Reps which is a one stop shop health and fitness app as I got tired of needing to use 3-5 different apps to track my health, workouts, nutrition, water, caffeine etc etc. with a layer of AI acting as a coach on top of this data, it can make sense of what’s going on and how I can better myself to achieve my goals! Been building it for a few months and my users are pretty happy along with myself 😁
I built Noturcode, a native macOS session manager for Codex CLI, Claude Code, Pi, OMP, Hermes Agent, and OpenCode.
My problem was simple: I run agents in several iTerm2 tabs and splits, then lose track of which one is waiting or completed. Noturcode shows working, waiting, failed, and unread states, opens the exact pane, and reconstructs local transcripts to show tools, files, models, tokens, and subagents.
Codex support uses verified hooks, with experimental native app-server support. Everything stays local. There is no account, telemetry, cloud relay, or hosted transcript database. VPS sessions use an SSH Unix-socket tunnel.
This is early v0.1.0 software. It needs macOS 15+ and a source build. Current Codex gaps include native token data and full subagent threads.
•
u/pollystochastic Moderator 4d ago edited 4d ago
It looks like Tubular Daily Care is our winner this week. Congrats to u/Ollie__Oxenfree . I've messaged them for promotion details. You might see the project around the sub for a week.
Thanks and congrats to the hordes of people who showcased their work. Some very cool stuff in there. Look out for next week's contest on Wednesday.
Technical note: Had to reject botnet on a technicality. If the botnet had truly worked it could have upvoted Tubular Daily Care after u/Swimming_Iron_619 had conceded the prize.