Coming from a traditional XP and Agile background, the current AI developer landscape can feel incredibly hollow because tools like Copilot or Cursor treat the model as a glorified editor plugin or autocomplete box. If you value open source, local-first computing, and deterministic control, modern tooling shouldn't be about finding a better IDE extension but treating the AI as an independent operator that sits completely outside the text editor.
I built an entire local-first sovereign agentic stack on Linux that completely replaces the IDE-centric model with a terminal control plane called Hyperia. Hyperia is a terminal emulator with a decoupled agent sidecar that hooks directly into standard protocols like the Model Context Protocol.
https://deepbluedynamics.com
Instead of just reading passive text buffers, it monitors discrete command lifecycle events across your shell sessions and web panes, catching stack traces as your test suite runs like a true pair-programming partner. To make this safe and reproducible, you cannot let an LLM run arbitrary, side-effect-heavy tool calls directly on your host machine.
This is handled by Nemesis, a container orchestration runtime that acts as a secure, session-persistent sandbox for the agentic workspace. When an agent writes code or touches system files, it executes inside an isolated Docker container, keeping the host operating system completely pristine.
For data-heavy tasks like parsing local markdown files or indexing an entire photo archive, you should avoid proprietary cloud vector databases. This stack uses Shivvr, a local semantic search engine that handles chunking and inverted vector embeddings entirely on your own hardware so your data never leaves your laptop.
Finally, the extraction, ingestion, and scraping of local docs or web sources is handled by Grub, an automated, high-speed crawler that feeds structured data back into the system. Modern tooling shouldn't mean chaining yourself to a proprietary cloud SaaS platform.
By exposing standard Unix primitives like files, shells, and local compilers to an API, sandboxing the environment in a container, and letting a local agent orchestrate the workspace, the cloud-vendor magic fades away and actual sovereign software engineering takes over.
All of this is a WIP but I use it every day to work on it.
https://deepbluedynamics.com/blog/sovereign-architecture