nemesis8

lueDynamics/nemesis8 https://skiff.deepbluedynamics.com (demo)

e to the host metal, for testing agent builds inside their containers. Hyperia has a lot of extra features as well that I have found personally useful: - Sticky notes (search too) - addressable panes in addressable tabs, tabs in windows, multiple windows - full ACLs across panes, notes, tabs, windows - Poke-a-pane to keep an agent going (any agent, not just CC which has a timer function) - webpanes with markdown extraction, JavaScript injection - directory pickers for people who find cd'ing to things confusing or those weary of typing nearly the same directory path over and over again in new terminals (not perfect, but I'm iterating on it) - a built in agent loop (in the Rust sidecar) that allows using local models for tool calls (needs a trained drafter to make it viable) or using a local model for token maxxing (compresses reads of panes by frontier models) - pane splits down/up/left/right and quick layouts. As for whether it was "vibe coded" or not, or Herdr for that matter, I don't think that term is useful, other than for quick judgment. No, this is not a one-prompt project. I've spent 100s of hours on it, started out with Hyper, and did a crazy amount of planning on how to architect it. I have done systems architecture for a living before, and have a strong search background. People who hate on AI, and therfore projects done with AI, are threatened. Nothing more. That's why they shortcut with "AI slop" or "Vibecoded. Nope". That's just ignorance speaking from a standpoint of fear. Slop, whether AI or human, is an effort problem: https://deepbluedynamics.com/blog/ai-slop-effort-problem. Looking at Herdr, it looks solid. Judge the product by it's outcomes, it's use, not whether or not AI wrote it or not. That's the moment we're in though, for now, so downvote or not. I don't care.

and windows. I've tried to keep it minimalistic, which helps with flowing back and forth between different projects (I typically work on 3-4 at a time). I added a Rust sidecar, making all objects addressable over MCP, so Claude Code, Codex, or a small local model on Ollama can split panes, run commands, and read screens, with one hard rule enforced in the harness rather than the prompt: an agent can never move my focus, other than asking for permissions to access a new object. ACLs too. Hyperia also carries an agent loop that wires into it's own MCP server, so a local model in a Javascript "shell" can control resizing the terminal (handy for videos), or opening a project and setting up the agent panes. I stay typing in a pane while the agents work in theirs, in my peripheral vision, and web panes sit right next to terminals so docs, webapps/sites and the agent chat live in the same window. Reviewing becomes glancing instead of context switching, which is the closest thing to ideal flow with prompts I've gotten out of this auto-AI stuff. Tab and pane clicks copy the address into the buffer, then I paste and issue commands referencing what I want dealt with. I have an SDR radio on my box that allows me to talk to a given pane (WIP not in the build yet). Working on getting the local agent stuff done and wired to the radio. The upshot of this approach is enabling agents running in one tab, all mounting the same directory, with one in charge of the others. Claude Code is great at this, and it saves on the tokens it would normally use for doing it itself. I talk to Claude, or whatever I pick, and it talks to the rest of the agents and coordinates the work. I like Antigravity a lot because it moves crazy fast for coding. With Claude in control and GLM-5.2 doing auditing and explaining to me how development is going. As an example. No unseeable agent army here. No need for it, actually. About the only thing that trips me up at the moment is having to work on Hyperia itself, which I don't do inside of it because of restarts. When I work on Hyperia, I start an agent in Windows terminal and wire it into the MCP for testing. I build installers constantly as well, and then run through the Q&A process by using it to work on other projects I'm doing. I use Zed for code editing and viewing, but rarely. I also just open things in special sticky notes (or have the agent do it) so I understand how we're doing things. GLM-5.2 took to the planning stickys like a fish in water. https://github.com/deepbluedynamics/hyperia https://github.com/deepbluedynamics/nemesis8 (n8) Both are open source, obviously. It's worth mentioning they will remain that way and will never require a service plan or any other cost. I built them because I needed it for another project I will be selling, not aimed at developers at all. n8 implements the agent runs in containers. This is a separation of concerns - in runs in any terminal and controls the session starts and search for previous sessions (as well as monitoring the usage of tokens, CPU, network and file access). Working on the dashboard for that now, so I can easily see which files are changing, how much they changed, and what changed in them. I co-founded Loggly, so that crap is in my wheelhouse. This isn't the tab completion model. It works great for the way my brain works, but I also think having an agentic terminal is a good move for anyone writing code and we'd all be better off if we ran agents in containers over our bare metal. It makes it way easier to see what the agent is doing (and resuming later), and allows it to do most of its work in the container, as opposed to running loose on my box..