#31521 made computer use send `computer_toolset_20260801` to Claude 4.8 and later, but swapped it back to `computer_20251124` on Claude Platform on AWS and Bedrock, since Anthropic's docs say neither offers the toolset. That's wrong for Claude Platform on AWS, so computer use on dogfood's Opus 5.5 fails with `'claude-opus-5-5' does not support tool types: computer_20251124`. I probed the AI gateway, and Claude Platform on AWS accepts exactly the versions the Claude API does, e.g. the toolset for Opus 4.8 and 5.5, and `computer_20251124` for Opus 4.6. The harnesses that get this right (Anthropic's computer-use demo and SDK toolset helpers, the Vercel AI SDK, LiteLLM) pick the version from the model ID alone and leave the wire format to the platform client, so we'll do the same and drop the override. fantasy's doc comment repeated the docs, which coder/fantasy#83 fixed, so this bumps fantasy too. Bedrock follows the same model table. AWS's Opus 4.8 model card only lists `computer_20251124`, but it's just behind: Anthropic's Bedrock docs list Opus 4.8 as taking the toolset with no beta header, and `anthropic.claude-opus-4-8` on Bedrock (via Mantle in us-east-1) returned a `screenshot` tool call for the toolset with no beta. Dogfood's InvokeModel route, which runs Opus 5.5, does the same. Bedrock was also broken on `main`, since aibridge's Bedrock beta allowlist drops `computer-use-2025-11-24`, so `computer_20251124` never got through validation. I've added it. On InvokeModel, Opus 4.7 returned a `computer` tool call for `computer_20251124` once the flag reached Bedrock, but a 400 when the flag went through dogfood's gateway, which runs `main` and drops it. Unlike the effort and context management flags, the flag doesn't need gating per model, as Bedrock accepts it on models that don't support `computer_20251124`. On Bedrock InvokeModel in us-east-2, Haiku 4.5 returned a 200 with the flag on its own and with `computer-use-2025-01-24` and a `computer_20250124` tool, whilst a made-up flag got a 400. Bedrock only rejects the tool type itself, and the model table never sends `computer_20251124` to Haiku 4.5 anyway. InvokeModel does still run the provider's `settings.model` rather than the model the chat config names, so the version can disagree with what actually runs if the two differ. That's the known model swap in #29511, and it's no worse here, as `main` picked the version from the model config too. The documented setup is one provider per model, so the two match, and the native `bedrock-runtime` protocol will remove the swap. I verified Claude Platform on AWS end to end, running Coder Agents from this branch against dogfood's AWS gateway route. Computer use on Opus 5.5 and Sonnet 5.5 sent the toolset and got a 200 on every request, across multi-step turns, an interrupted turn, a page reload, and a chat that switched to Opus 4.6 (which sent `computer_20251124`) and back. The same setup on `main` reproduced the 400. I also ran the same scenarios against dogfood's Bedrock InvokeModel route. Opus 5.5 and Haiku 5.5 got a 200 on every computer use request, with up to 22 screenshots in the history, including a chat that switched to Opus 4.6 on Claude Platform on AWS and back. That went through dogfood's gateway, so it covers what Bedrock accepts from Coder Agents, but not a Bedrock provider configured in Coder itself, which I still haven't run end to end.
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.
