Persistent containers

A development environment that vanishes the moment you close the laptop isn’t an environment, it’s a script. You spend the first ten minutes of every morning rerunning the same commands, waiting for the same database to migrate, waiting for the same dev server to compile.

Loopyard’s containers are persistent by default. The workspace, the dev server, the database, the queue: they keep running between sessions. Restart the Loopyard server itself and they’re still there when it comes back up. Restart your machine and they come back with it.

That means caches stay warm, sessions stay logged in, the agent’s working context isn’t reset. When you sit back down, you sit back down inside the same project you left. The branch is where you left it; the failing test is still failing the same way; the agent’s chat scrolls to where the conversation paused.

When you actually want a clean slate, you ask for one. The default is to remember.