## Problem Fresh Ubuntu 26.04 workspaces emitted Playwright unsupported-OS warnings even after upgrading the package. The repository pinned Playwright 1.55.1, and the dogfood image baked in `PLAYWRIGHT_HOST_PLATFORM_OVERRIDE=ubuntu24.04-x64`, which prevented native OS detection. ## Fix Update `@playwright/test` and its lockfile resolutions to 1.63.0, which supports Ubuntu 26.04, and remove the obsolete platform override from `dogfood/coder/ubuntu-26.04/Dockerfile.base`. Companion https://github.com/coder/dogfood/pull/638 upgrades the separate Playwright MCP installer and clears the inherited override at runtime for already-published images. ## Validation - Fresh TEST workspace `startup-warnings-clean` reached ready and healthy. Its 15 captured startup log files (774 lines) contained zero `node-gyp: not found`, optional crypto-binding failure, `EBADENGINE`, Playwright missing-dependency (`without first`), or unsupported-OS (`BEWARE`) warnings. The logs recorded one native-binding success and one dashboard start. The preceding fresh-startup test reproduced five Playwright `BEWARE` warnings. - Site Chromium `153.0.8010.12` launch/navigation passed. The actual generated `~/.claude.json` MCP configuration passed launch, initialization, navigation, and close; the Codex TOML command matched. Agent-browser smoke testing also passed. - This used repository commit `d137476055` and the published Ubuntu 26.04 image with the template clearing its inherited platform override. The image-source removal was not present in the tested image; no rebuilt-image startup test was performed. - Earlier frozen-lockfile installation, frontend formatting, checks, and lint passed. Fresh Chromium downloads, headless-shell and full-Chromium launch/click/assertion smoke tests, and all 15 Button Storybook tests passed locally. - Current CI passed the Ubuntu 26.04 image build, lint, formatting, generation, JavaScript tests, application E2E tests, Flake Check, and the required-check aggregator. The newly built image has not been startup-tested. [Storybook/Pixel](https://github.com/coder/coder/actions/runs/36856302955/job/110349479622) again failed with HTTP 500 (`could not record snapshot`), aborting after 11 failed snapshot reports. <details> <summary>Implementation decisions and verification limits</summary> Runtime verification used inactive template version `startup-warnings-native-os` (`7a0ea80e-60ef-4fb0-abc9-fbb8ec32d9a3`). The active shared version `cf3c11f` remained unchanged. Use native Ubuntu 26.04 support rather than filtering warnings or forcing fallback builds. Remove the override at its image source and clear it in the companion template so existing images benefit without waiting for a rebuild. Keep dependency changes limited to Playwright and its lockfile resolutions. Firefox, WebKit, and local Nix compatibility remain unverified. An earlier dependency-install dry run reported missing system packages despite successful Chromium smoke tests. Local Storybook retained its existing Vitest package-version mismatch warning and teardown timeout. The Mux AI SDK/Ollama peer-dependency warning ([upstream issue](https://github.com/coder/xum/issues/5372)) and generic agent-browser Linux advisory remain. Provisioning also reports unrelated `coder_agent.dir` deprecation and Desktop file-sync warnings. This does not claim a warning-free workspace. </details> > 🤖 This PR was created with the help of Coder Agents, and needs a human review. 🧑💻
Coder is a self-hosted platform for cloud development environments and AI coding agents. Workspaces are defined with Terraform, connected through a secure Wireguard® tunnel, and automatically shut down when not used. Coder Agents runs a native AI coding agent whose loop executes in the control plane on your infrastructure, with no API keys in workspaces.
- Define cloud development environments in Terraform
- EC2 VMs, Kubernetes Pods, Docker Containers, etc.
- Automatically shutdown idle resources to save on costs
- Onboard developers in seconds instead of days
- Delegate coding work to AI agents on your infrastructure
- Bring any model (Anthropic, OpenAI, Google, Bedrock, self-hosted)
- No LLM credentials in workspaces, user identity on every action
- Centralized model governance, cost tracking, and audit logging
Quickstart
Check out our install guides for other methods and a complete tutorial.
Try Coder with the install script on Linux and macOS, or grab the latest binary or installer from GitHub Releases on Windows:
curl -fsSL https://coder.com/install.sh | sh
Start the server and open http://localhost:3000 to create your initial user, create a Docker template, and provision your first workspace:
coder server
For a production deployment, add a PostgreSQL database (version 13 or later) and an external access URL, and see our validated architectures for sizing and infrastructure guidance:
coder server --postgres-url <url> --access-url <url>
Without these flags, Coder uses a built-in database and sets up a *.try.coder.app access URL for evaluation. Use coder --help for the full list of flags and environment variables.
Documentation
Browse the documentation or visit a specific section below:
- Workspaces: Workspaces contain the IDEs, dependencies, and configuration information needed for software development
- Templates: Templates are written in Terraform and describe the infrastructure for workspaces
- Coder Agents: Delegate coding work to AI agents running on your self-hosted infrastructure
- AI Gateway: Centralize authentication, auditing, and cost controls for AI tooling
- Administration: Learn how to operate Coder
- Premium: Learn about paid features built for large teams
- IDEs: Connect your existing editor to a workspace
Support
Open an issue for bugs and feature requests.
For community support, showcasing what you built, and feedback on in-progress features, join our Discord or GitHub Discussions.
Dedicated support is included in Coder Premium. For more information, visit coder.com/pricing.
Integrations
New integrations are always in progress. Open an issue to request one. Contributions are welcome in any official or community repository.
Official
- Coder Registry: Templates, modules, and integrations for common development environments
- Coding Agents: Run agents like Claude Code, Codex, and OpenCode isolated in Coder workspaces
- coderd Terraform Provider: Declaratively manage your Coder deployment configuration as code
- VS Code Extension: Open any Coder workspace in VS Code with a single click
- JetBrains Toolbox Plugin: Open any Coder workspace from JetBrains Toolbox with a single click
- Dev Containers: Build development environments using
devcontainer.jsonon Docker, Kubernetes, and OpenShift - Kubernetes Log Stream: Stream Kubernetes Pod events to the Coder startup logs
- Self-Hosted VS Code Extension Marketplace: A private extension marketplace that works in restricted or airgapped networks integrating with code-server.
- GitHub Actions: An action to set up the Coder CLI in GitHub workflows
Community
- Coder Discord: Chat with the community, get support, and hear about new product updates first
- Community Templates: Community-contributed workspace templates in the Coder Registry
- Community Modules: Community-contributed modules to extend Coder templates
- Coder Template GitHub Action: A GitHub Action that updates Coder templates
- Coder Agents Chat Action: A GitHub Action that starts a Coder Agents chat against a GitHub issue or pull request
Contributing
New contributors are always welcome. If you are new to the Coder codebase, see the contribution guide to get started.
Hiring
Apply on the careers page if you are interested in joining the team.
