Coder’s blog shows wiring Microsoft’s VS Code Server into a Coder template so developers get browser VS Code with legal access to the Microsoft Extension Marketplace—including Copilot and Pylance—on cloud workspaces.
Official Coder docs compare four ways to run Docker builds and tests inside container workspaces: Sysbox runtime, Envbox, rootless Podman, or a privileged docker:dind sidecar.
Coder admin docs let template owners set default autostop, activity bumps, and optional dormancy so idle workspaces stop (and eventually delete) instead of burning compute.
Official Coder docs show four ways to reach apps running in a workspace—Coder Desktop auto-forward, coder port-forward CLI, dashboard Open Ports, or SSH -L—so you can hit web servers, Jupyter, and APIs on localhost.
Coder’s tutorial walks you through a Docker+Ubuntu workspace template in Terraform: coder_agent, code-server via coder_app, persistent home volume, then push with the CLI or dashboard.
Short official blog on workspace anatomy: reproducible templates with deps/IDEs/config, plus connection options—web IDEs, SSH + VS Code Remote, or local file sync.
Workshop write-up: define persona templates (cloud-native, serverless, agentic, GenAI) as Terraform, GitOps them, and run parallel agents each in isolated AWS workspaces instead of conflicting on one laptop.
Docs overview of Coder Agents, Agent Relay, IDE agents, and agents-in-templates—plus Terraform snippet to install Claude Code/Codex modules into a workspace template.
Coder blog explains why local Claude Code is risky for enterprises, then shows AWS/EKS reference setup, golden templates with Claude Code registry module, managed settings, and audited sessions.
Official quickstart: install a container runtime, start coder server, create a Docker template in the template builder, launch a workspace, and connect VS Code Desktop or browser VS Code.