All work
in progress2026 · Systems / DevEx engineer
Multi-Model CLI Router
One coding CLI, routed across frontier models through a unified gateway.
01 / The problem
Coding agents are typically locked to a single provider; comparing frontier models mid-task means switching tools entirely.
02 / The architecture
Diagnosed environment PATH conflicts, corrected model-slug formatting mismatches between providers, and resolved gateway billing/auth errors (402s) blocking requests — treating the CLI environment itself as a system to be debugged with logs and reproducible steps rather than trial and error.
03 / The challenges
The failure modes were silent — a wrong model slug or a billing edge case looks identical to a network error from the CLI's side. Diagnosis meant instrumenting each layer separately.
04 / The results
A single, portable CLI workflow on a cloud VM that can route the same coding task across multiple frontier models on demand.
05 / The lessons
Developer environments are systems too — they deserve the same debugging discipline as production code.
06 / Metrics
2
Providers unified behind one CLI
07 / Tech stack
- Windows VM (Azure)
- OpenRouter
- Claude Code
- Codex CLI
- PowerShell
Contact
Let's Build Something Worth Remembering.
Open to internships, founding-engineer roles, and focused contract work in cloud, data, and AI products.