coding-agent-config

Machine-level configuration and tooling notes for working effectively with Codex and related terminal-based coding agents on this Mac.

The main setup log is in macbook-agent-setup.md.

For reconstruction on a similar machine, start with recreate-machine.md.

For native macOS app work in SwiftUI/Xcode, see swift-xcode-dev.md.

For Developer ID signing, notarization, and small-scale outside-the-App-Store release flow on macOS, see sign-apple-apps-publish.md.

For macOS TCC permission testing and fast dev-build identity rules, see macos-permission-dev-builds.md.

For Guardian backend work on GCP, including gcloud, ADC, direnv, and ops ergonomics on this machine, see guardian-gcp-backend-dev.md.

For evidence-driven validation patterns and a strict no-cheating testing stance, see closed-loop-validation.md.

For four principles for keeping complexity honest in AI-assisted coding (walking skeleton, YAGNI + Rule of Three, complexity budget, boring tech + subtraction) plus concrete practices and red flags, see complexity-discipline.md.

For terminal UX gotchas that affect Codex output, including Ghostty's tendency to not command-click markdown-style local file links and the preference for vscode://file//... or code -g over open for repo files, see templates/home/AGENTS.md.

For the faster GuardianScreenPipe/macOS tray-app debug loop, including the API-plus-SQLite live watcher pattern, see the tray-app section in closed-loop-validation.md.

For adb-driven Android closed-loop UI control on physical devices such as the Jelly Star, see android-closed-loop-ui.md.

For Android physical-device USB capture bring-up and Jelly Star-specific lessons learned, see android-usb-capture-notes.md.

For Mac plus Jelly Star appliance plus Pixel source-phone testing, see android-two-phone-testing.md.

For repeatable Android lifecycle reliability testing on physical devices, see android-lifecycle-reliability.md.

For post-install and post-replug verification on Android physical devices, see android-post-install-verification.md.

For Expo / React Native closed-loop harness patterns including browser window verification, evidence bundles, PID/build tracking, event-driven waits, and multi-surface testing, see expo-react-native-harness.md.

For Paul's standing permissions around proactive local tooling installs, official-site downloads, and reusable validation setup, see unusual-consents.md.

For iOS reverse-engineering capture work, including CoreBluetooth logs, HCI/ATT pcaps, RVI network negative controls, ExternalAccessory probes, and runtime/static app instrumentation choices, see ios-reverse-engineering.md.

For the generic UI bench core-plus-adapter model used to make remote or local closed-loop UI testing reusable across apps, see ui-bench-core.md.

For the MacBook Air remote mobile bench used by Guardian, including Screen Sharing + Hammerspoon + visible Simulator/Emulator capture + iOS Maestro and Android UIAutomator smoke, see guardian-air-remote-mobile.md.

For Mac-side Jelly Star import tooling, see phonecapture-import.md.

Reusable agent skills live under skills.

Current repo-local skills include:

• gcloud-auth-handshake: pause and ask for the exact gcloud / ADC login command when Google Cloud auth is stale instead of guessing through failures

Reusable closed-loop harness scripts live under templates/home/.local/bin.

Useful Android helpers there include:

• android-ui-snapshot
• android-ui-node
• android-verify-state
• android-two-device-check
• android-source-display-check
• phonecapture-import

phonecapture-import now supports persistent destination configuration and JSON status output, which makes it a good stable backend for a small macOS menubar importer.