loopyard

Persistent containers

Restart the server. Reboot the laptop. Containers stay where you left them.

The same Loopyard session on a phone: Persistent containers

A conversation with history. Close the tab, restart the server, come back tomorrow: the agent, the transcript, and the running services pick up exactly here.

A development environment that disappears when you close the laptop makes you pay for it again every morning: the same commands, the same wait for the database to migrate and the dev server to compile.

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

Caches stay warm, sessions stay logged in, and the agent keeps its working context. You sit down inside the project you left: the branch where you left it, the failing test failing the same way, the chat scrolled to where the conversation stopped.

When you want a clean slate, ask for one.

Run it on your machine

git clone github.com/loopyard/loopyard.git
cd loopyard
mix loopyard.setup

Free and open source on GitHub. Follow @loopyardai.