Raccoon Herder

You already have the agents. Grok, Claude Code, Copilot, Hermes, and the rest. Raccoon Herder is the chat in front of them. Open it on a phone, a tablet, or a laptop, and the work stays on a machine you control. A turn comes back as a conversation: what the agent is doing, the tools it wants to run, and a card that waits until you say yes. Nobody uploaded the repo to a cloud you do not own, and nobody handed you a terminal in a browser tab.

A den is one person and one workspace. When you need more than one, the Herder is the part that runs them. It starts a den, stops it, and leaves the disk where it is, including git work that has not been pushed. A floorplan is the memory of a den: which agent, which repo, how much machine, and what it is allowed to touch. A scratch pad, a client job, and a locked review box are three floorplans. You pick one and a den comes up already shaped.

Each den gets the security the job actually needs. A throwaway can reach the network. A den with real code only reaches an allowlist, and everything else is dropped. Ask for a record and you can see where it talked. Ask for a closer look and you can see inside the traffic, with the contents redacted until you decide you want the raw bytes. If a den starts abusing the control plane, the Herder holds it. The person inside cannot wipe the den before you have looked. A shell stays off until you turn it on for that den. A den cannot reach back and drive the machine that created it.

Keys and login files are sealed in the browser before they are stored. The Herder keeps the envelope and never learns the passphrase. When a session is finished it can be archived, and a reviewer in that organization can open it. Every open is written down. Quotas and floorplans are per organization, so the person running a lab and the person reviewing a client den are not holding the same keys.