Design on Defender TD5

The Bridge's Missing Tools: Where AppleBridge's MCP Surface Is Thin

Mon, 29 Jun 2026 10:36:38 +0200

The toolchain note argued that AppleBridge’s integration points are its two automation surfaces, not its compiler — and that the boldest move is to stop compiling on the Mac and let the bridge deploy-and-run. This follow-up asks the practical question that raises: do the MCP tools actually support that, and what is missing? Read against the code, the answer is sharp — the toolset is mature where it drives a compiler and thin where it moves bytes and interacts with what runs. Captured as a design note on branch AppleBridge_mcp; not implemented.

Development Toolchains Beyond MPW: What Fits AppleBridge's Automation Surface

Mon, 29 Jun 2026 10:08:05 +0200

AppleBridge drives MPW and ToolServer to build 68K software inside the emulated Mac. The natural question is whether something better than MPW exists — but, thinking out of the box, that is the wrong question. AppleBridge does not need a better compiler; it needs a better automation surface. Re-asked that way, the field of alternatives sorts itself cleanly, and one genuinely unconventional option appears: stop compiling on the Mac at all. Captured as a design note on branch AppleBridge_mcp; not implemented.

One Transport, Then Many: The Impact of Widening AppleBridge from Open Transport to MacTCP and Beyond

Mon, 29 Jun 2026 09:14:14 +0200

The installer note recorded Open Transport as a hard launch dependency, and the transport-alternatives note named an OT → MacTCP → serial → native fallback ladder. This piece asks the operational question those two raise: what does it actually cost to widen the daemon’s transport from OT-only to MacTCP, and maybe beyond? The answer is encouraging in the place one expects pain and sobering in places one does not. Captured as a design note on branch AppleBridge_mcp; not implemented.