# Woodshed > Open source cloud dev environments for Claude Code and Codex, on machines you host. Every task gets its own > environment: its own branch, databases and running copy of your app, so many tasks run side by side and each is > tested on its own. Inside, the agent changes the code, checks the change in a real browser, and opens a pull > request with a `## Proof` section. One console manages every environment, with a live terminal, a shell, a review > of its changes and its app, on a laptop or a phone. Source: https://github.com/ChifferCo/woodshed. Licensed AGPL-3.0-only, with `shared/` under MIT. ## Starting an environment (the console calls it a session) - GitHub: the `woodshed` label on an issue, or a `/woodshed ` comment on an issue or pull request. A shared session, which everyone signed in can see. - The console: **New session**. A private session on your own Claude Code or Codex sign-in; the console posts nothing on GitHub. - Slack: mention the bot with a question about the code. A short read-only session answers in the thread. ## What an environment can reach - Its own container, branch, Postgres and Mongo copies, and its app at `https://.`. - Hour-long GitHub tokens for one repo, from the console. - Never AWS credentials, production data or production integration tokens. ## Setting it up (for an agent doing it) 1. Try it: `git clone https://github.com/ChifferCo/woodshed`, then `node woodshed/console/bin/devConsole.mjs`, and open http://localhost:7690/s/aaaa1111. Made-up sessions; needs Node 22 and nothing else. 2. Pick where it runs. `WOODSHED_PROVIDER=local` runs sessions as Docker containers on any machine: a VM or bare-metal server on Hetzner, OVH or any other provider, or your own hardware. `WOODSHED_PROVIDER=aws` uses an AWS account of its own: EC2 for the console, Fargate for sessions, Secrets Manager, S3, RDS, and a Lambda URL into SQS, built with Terraform. 3. Follow that provider's README step by step. Read `terraform plan` before every apply. Never print a secret's value. 4. Describe the repo in `.woodshed/project.yaml` at its root. Only `version: 1` is required; the reference lists every field with an example. ## Read these - [README](https://github.com/ChifferCo/woodshed/blob/master/woodshed/README.md): what Woodshed is, how it works, the providers, the project file - [console/README.md](https://github.com/ChifferCo/woodshed/blob/master/woodshed/console/README.md): sessions, states, My Woodshed, Review, apps, Slack, phones - [providers/README.md](https://github.com/ChifferCo/woodshed/blob/master/woodshed/providers/README.md): what a provider gives the console - [providers/local/README.md](https://github.com/ChifferCo/woodshed/blob/master/woodshed/providers/local/README.md): Docker on any machine - [providers/aws/README.md](https://github.com/ChifferCo/woodshed/blob/master/woodshed/providers/aws/README.md): AWS, its costs and how to remove it - [project.reference.yaml](https://github.com/ChifferCo/woodshed/blob/master/woodshed/project.reference.yaml): every field of `.woodshed/project.yaml` ## Costs and plans - Self-hosted: free and open source. On AWS about $55 a month idle and about $0.13 an hour per session, plus Anthropic usage. With Docker, whatever machine you run it on. - Cloud for individuals: free. Cloud for teams: coming soon. Self-hosted in your VPC for enterprise: coming soon.