The Giles Engine. From What If? to Fuck Yeah.

Your KiCad AI bridge, without the terminal

  1. Keep the entire GilesEngine folder together in a writable location.
  2. Double-click Giles Engine.exe. It automatically checks your existing bridge.
  3. Open KiCad PCB Editor with your intended board. Enable the IPC API in Preferences → Scripting if needed. Keep one editor instance open.
  4. Click Check connection. If your bridge lives elsewhere, use Choose engine folder.
  5. In Codex, ask: Test the KiCad connection without modifying or saving anything. A successful response confirms Codex tool access.

What the status means

Engine found: the working server and its dependencies exist. KiCad API connected: KiCad answered a read-only version request. MCP connected: the existing server passed a protocol handshake and its original connection test. Codex configured: Codex settings point to the selected engine. Sign-in, permissions, account limits, and tool access are confirmed inside Codex.

The launcher briefly starts the original server for its connection test, then closes that test session. Codex starts and owns its own server connection. Leaving a separate launcher server running would not connect it to Codex.

If a check needs attention

Follow the plain-language message. An access-denied result means the connection is unverified. Run this app under the same Windows account as KiCad, outside a restricted agent session. You should not need administrator access. If there are multiple KiCad editors, the launcher tests the exact connection configured in the existing engine.

Use Save diagnostic report when asking for help. It contains local engine paths, versions, statuses, and a server fingerprint. It contains no design contents or credentials. Review it before sharing.

Undo and portability

Close the app and delete this folder to remove Phase 1. It has no installer, registry changes, background startup service, automatic updates, or changes to Codex settings. The only saved preference is engine.txt beside the app; delete it to reset folder selection. Your original bridge, runtime, backups, and designs remain in place.

If you used GilesEngine-Setup-0.1.1.exe, remove the installed copy through Windows Settings → Apps → Installed apps → The Giles Engine — Phase 1. Uninstall removes the app and shortcuts while preserving saved folder selection and user-added files. The installer includes playful profanity workshop messages; click the message on its finish page to discover more.

This Phase 1 executable runs on Windows with .NET Framework 4.5 or later (4.8 recommended). It uses your existing engine runtime. The launcher installer is available, but it does not bundle the external engine or dependencies for another computer. See the portable project-brain documents and packaging plan.

3D printing is part of the plan

Blender, FreeCAD, model/export checks and slicer/print preparation are core future tracks in 3D_PRINTING_ROADMAP.md. This Phase 1 build connects KiCad only.