// Tools & Experiments
Local-first tools for serious work.
Small systems from my own workflow: remote Codex control, session recall, runnable worktrees, mailbox context, voice-note transcription, tool feedback, and desktop utilities.
// Featured Tools
Tools built from recurring agent-work problems.
The page is not a complete project list. These are the tools that best show how I make local workflows more reliable.
codex-telegram-bridge
A local bridge for supervising Codex work from Telegram: receive updates, reply into the right thread, inspect active runs, and approve actions away from the laptop.
It turns Codex Desktop from a single-machine workflow into an agent setup I can safely supervise while away.
View repocodex-recall
A local SQLite FTS index over Codex session archives, so agents can search prior work and reuse context with receipts.
View repodevtree
A Rust CLI that turns Git worktrees into runnable local environments with copied env files, setup commands, managed dev servers, stable local URLs, logs, and safe cleanup.
View repomailbridge
A conservative JSON CLI over Gmail and Fastmail for search, read, thread lookup, attachment pulls, and draft-only composition.
View repotranscribe-audio
A Rust CLI for local audio transcription with batch runs, discoverable audio files, JSON manifests, prompt files, and combined Markdown transcripts for agent workflows.
View repotool-feedback
A local runtime for capturing tool-friction cases from real work, deduping them, and routing triage or patch jobs.
View repoapartment-finder
A TanStack Start app and Bun CLI for searching Buenos Aires rentals, extracting listing evidence, and classifying whether washer access is likely in-unit or shared-building.
View repoSimple Image Viewer
A dependency-free SwiftUI macOS viewer for opening an image or folder, stepping through nearby images by keyboard, and scanning a thumbnail rail with GIF and natural filename support.
View repocli-tools
A TypeScript monorepo of local CLIs for macOS apps, Granola notes, browser tabs, and social workflows.
View repo// Operating Rules
The same judgment shows up in client systems.
Keep useful state on the machine when possible.
Expose the smallest surface that still gets the job done.
Prefer source files, command output, and explicit state.