What problem does it solve? When developing Birdhouse plugins, AAPI routes, or read modes, testing against your own live Birdhouse environment pollutes your agent tree and risks corrupting real work. This Skill lets you spin up and drive a completely separate Birdhouse server over HTTP so experiments stay isolated. ## Core Features & Use Cases - Isolated Server Management: Start a dedicated Birdhouse server on custom ports with its own data database and workspace directory. - HTTP-Driven Agent Control: Create workspaces, seed provider keys, create agents, send follow-up messages, and read agent state entirely through curl endpoints. - Snapshot Lifecycle: Archive, restore, and trash complete test environments (workspace directory, data DB, SQLite sidecars, app-support folder) using the included shell scripts. - Use Case: You changed OpenCode plugin behavior and need to verify read modes. Start an external server on port 50150, create a workspace, run a real agent through multiple exchanges, inspect messages with last, full, and all modes, then compare against raw OpenCode session output. ## Quick Start Start an external Birdhouse server on port 50150 with a dedicated data database, create a test workspace via curl, and drive a fresh agent through HTTP to validate my plugin changes.