My view is that software engineering is splitting into two paths. One is deep craftsmanship. The other is guided operators who know how to steer tools, systems, and LLMs toward the right result.
I am keen to hear where others agree or disagree, and how you see this playing out in real teams.
Most coding CLIs I've seen lock you into one provider or requires you to bypass by changing BASE_URL and has a lot of conflict. That works fine if you're committed to one vendor for coding cli harness, but it breaks down when you want to run local models, test different providers, or avoid API costs entirely.
So we tried a different approach. Instead of hardcoding a provider, Autohand code lets you swap between OpenRouter, Anthropic, OpenAI, Ollama, llama.cpp, and MLX from the same codebase. Switch models mid-conversation if you want.
High level, the design optimizes for three things:
Machine orchestration: stateless execution, structured outputs, designed for CI/CD and batch runs, not just interactive use
Auto mode: autohand -p "fix the tests" --yes --auto-commit runs the full task without prompts. Three permission levels plus granular command whitelist/blacklist
Skills system: modular instruction packages that activate on demand. Run --auto-skill and it generates skills tailored to your project
One thing that's been surprisingly useful: because it's provider-agnostic, you can prototype with a fast cheap model, then swap to something heavier for the actual run. No code changes, just config.
It's TypeScript + Bun, 40+ tools (file ops, full git, semantic search, multi-file edits), sessions persist and resume.
This made me laugh https://www.forbes.com/sites/annatong/2026/03/05/cursor-goes...
If that's what winning looks like AI Summer is coming!
reply