I build macOS and iOS apps, and I send small, tested fixes to other people's open source.
My main project is Trailwarden — an audit trail for coding agents on macOS. Claude Code, Codex, Gemini CLI, opencode, Cursor, Copilot and Hermes already log what they do on your Mac. Trailwarden reads those logs, tells you the moment an agent runs something you would have stopped, shows which agent touched which file, and turns a month of agent work into one page you can read or hand on, redacted.
Local-first on purpose. No account, no server, no telemetry. The only two network reads are the update check and the price list — both of a public file, both on your click.
- Swift / SwiftUI app, a CLI, and an MCP server other agents can query
- 27 risk rules —
rm -rf,curl … | sh, keychain reads,DROP TABLE, and more - Apache-2.0 · macOS 14+ ·
brew tap tnalbant/trailwarden
brew install --cask trailwarden # menu bar app
brew install trailwarden-cli # CLI + MCP serverThe same thread runs through my pull requests: security, guardrails, and refusing input that does not parse instead of accepting it quietly. Each one reproduced before it was touched.
| Pull request | What it fixes |
|---|---|
| oxynote#434 | a data source URL that does not parse is rejected instead of silently accepted |
| Ai-edit-studio#159 | WebVTT caption files are read correctly on import |
| openuni#141 | inverted from/to ranges are rejected on the calendar endpoint |
- Reproduce first, then fix. I would rather write the test that shows the bug than argue about the fix.
- Every change ships with a test that fails without it.
- Small diffs and clear messages; no unrelated cleanup.
- Read the repository's own process before writing code.


