u/alexid95

I'm Alexander, the solo developer of SimGoodie, an early life sim I'm making in Unity in my free time. I'm aiming for the character depth I loved in The Sims 2 and an open world inspired by The Sims 3.

I use Claude Code alongside other coding agents for implementation and UI work. I organise changes as scoped OpenSpec tasks, have a separate review pass, and use a headless simulation lab to run gameplay scenarios over simulated days. The difficult part is checking whether the building, navigation and character systems still agree after a change.

Game Log #2 shows a concrete example: a floor could look fully covered but still provide no walkable surface. It also leaves in the blocked interactions and second-floor problems. This attached clip is a first look at the current game, and the full walkthrough shows more of the work in progress.

The Game Log and video are free to watch. There is no public playable build yet, and I haven't announced pricing or a release date.

Game Log #2, screenshots and full video: https://simgoodie.com/devlog/the-house-needs-a-floor-before-it-needs-a-reputation

If you're using Claude on a game with several connected systems, how are you testing changes that look correct in isolation but break when the systems interact?

I kept running into a weird split: ChatGPT had the model I wanted to use, while my actual code, terminal, running processes, and unfinished work lived on my Mac. I wanted the normal ChatGPT conversation to behave more like a local Codex/Claude Code session instead of copy/pasting between them.

So I built Mac Developer Bridge and open sourced it today:

https://github.com/alexanderradahl/mac-developer-bridge

It runs locally and exposes arbitrary shell execution, unrestricted filesystem ops, real PTY sessions, detached jobs, and read-only access to persisted Codex threads. The bridge itself makes no model calls; ChatGPT stays the reasoning layer.

The workflow that sold me on it was basically: “find the Codex session I was working on yesterday, recover the context, inspect the live repo, fix CI, push the result.” It can actually do that now from a normal chat.

Important caveat: this is intentionally not sandboxed. It runs with the effective permissions of your macOS user. There is an explicit unlock latch, local audit log, OAuth/Cloudflare or OpenAI Secure MCP Tunnel transports, and a kill switch, but if you want a narrow allowlisted MCP this is the wrong project.

MIT, Node 18+, and the core bridge has zero npm runtime dependencies. I built it for my own workflow, so I’d especially like feedback from people already doing local MCP/agent tooling.