This is not an ai-agent virtual vibe coding ecosystem. It's an organizational pattern that helps me mentally keep track of my projects and their infrastructure. Servers are barns, deployed repositories are livestock, system services are critters, herds are environments. The running process itself acts as an MCP server for Claude Code sessions providing this information to sessions based on the context.

I have been working on this tool for a few weeks now, both developing on it and from within it. It's a central place for me to keep track of my projects, servers I run code on, and what is running on what server. It also helps me run multiple instances of Claude Code in an organized way.

I'm a fan of working in my terminal, and I love using Claude Code. This tool mentally helps me keep track of various issues and tasks I'm working on. It's built on top of Tmux so it can be detached and remain running in the background. I have some fun ideas in the future to bring in more automation in a structured way to help extend dev processes even further.

The code is open source. If you find it useful or interesting I'm curious to know your thoughts or suggestions. There are more features as well that are sort of half-built, like syncing environments based on IaC tools, issue tracking with github/linear, a project wiki feature, visualizer, and more.

Let me know what you think!