Docs · Concepts

The moving parts.

Five ideas explain everything poddle does.

Identity: A coding-agent login, created and stored on your machine - never only in poddle. You authenticate once with poddle identity add; poddle re-authenticates it if it goes stale before wiring it into a pod, so a dead credential never reaches the sandbox.
Provider: The auth vendor behind an identity (e.g. Anthropic). A provider knows how to authenticate a login and materialize it into a pod's mounts and environment.
Harness: The coding-agent runtime that runs inside the pod, chosen with --harness (default claude-code).
Pod: An isolated, disposable Podman-backed environment created by poddle up (or per poddle task) and removed by poddle down. Sized weak (2 vCPU / 4 GB) or strong (8 vCPU / 16 GB); resize it live with poddle resize, or re-home a session onto a fresh shell with poddle move.
Broker: The secret-safe egress path - the poddled daemon. The pod carries a revocable handle, and the broker injects the real credential on the wire while scrubbing stray secrets from outbound bodies - so the raw secret never lands in the pod. poddle connect brokers services (git, CI, …) the same way.

The broker is the whole trick

Everything else is plumbing around one guarantee: the pod holds a revocable handle, and the broker swaps in the real credential on the wire. Revoke the handle and the pod is instantly locked out - no key rotation, no scrubbing a container image.

Security & threat model →Examples →Command reference →