Kyle Carberry
1a87e74574
## Problem When switching between chats on the agents page, stream parts could be lost or applied to the wrong chat due to several race conditions in `ChatContext.ts`: 1. **`startTransition` deferred parts escape cleanup** — `startTransition(() => store.applyMessageParts(parts))` defers the state update. If a chat switch happens between `flushMessageParts` being called and the transition executing, old-chat parts could apply after `resetTransientState()` has already cleared stream state for the new chat. 2. **`message` event has no `chat_id` filter** — Unlike `message_part`, `queue_update`, and `status` events, the `message` event handler did not check `streamEvent.chat_id`. While the server-scoped WebSocket makes this safe in practice, it's an inconsistency in defensive programming. 3. **Brief stale message window on switch** — Between `chatID` changing and `replaceMessages()` firing (after the query resolves), the store held old-chat messages while the new WebSocket was already connected. ## Changes ### `ChatContext.ts` - Added `activeChatIDRef` to track the currently active chat ID - Guard `startTransition` callback: check `activeChatIDRef` before applying message parts, discarding them if the chat has switched - Added `chat_id` filter to `message` event handler, matching the pattern used by all other event types - Added `store.replaceMessages([])` to the chatID-change effect so messages are cleared immediately on switch ### `ChatContext.test.tsx` Four new tests covering the chat-switch lifecycle: - WebSocket closure and state reset when chatID changes - `message` event filtering by `chat_id` - `startTransition` deferred parts discarded after switch - Messages cleared immediately before new query resolves All 13 tests pass (8 existing + 4 new + 1 existing).
Coder enables organizations to set up development environments in their public or private cloud infrastructure. Cloud development environments are defined with Terraform, connected through a secure high-speed Wireguard® tunnel, and automatically shut down when not used to save on costs. Coder gives engineering teams the flexibility to use the cloud for workloads most beneficial to them.
- 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
Quickstart
The most convenient way to try Coder is to install it on your local machine and experiment with provisioning cloud development environments using Docker (works on Linux, macOS, and Windows).
# First, install Coder
curl -L https://coder.com/install.sh | sh
# Start the Coder server (caches data in ~/.cache/coder)
coder server
# Navigate to http://localhost:3000 to create your initial user,
# create a Docker template and provision a workspace
Install
The easiest way to install Coder is to use our
install script for Linux
and macOS. For Windows, use the latest ..._installer.exe file from GitHub
Releases.
curl -L https://coder.com/install.sh | sh
You can run the install script with --dry-run to see the commands that will be used to install without executing them. Run the install script with --help for additional flags.
See install for additional methods.
Once installed, you can start a production deployment with a single command:
# Automatically sets up an external access URL on *.try.coder.app
coder server
# Requires a PostgreSQL instance (version 13 or higher) and external access URL
coder server --postgres-url <url> --access-url <url>
Use coder --help to get a list of flags and environment variables. Use our install guides for a complete walkthrough.
Documentation
Browse our docs here or visit a specific section below:
- Templates: Templates are written in Terraform and describe the infrastructure for workspaces
- Workspaces: Workspaces contain the IDEs, dependencies, and configuration information needed for software development
- IDEs: Connect your existing editor to a workspace
- Administration: Learn how to operate Coder
- Premium: Learn about our paid features built for large teams
Support
Feel free to open an issue if you have questions, run into bugs, or have a feature request.
Join our Discord to provide feedback on in-progress features and chat with the community using Coder!
Integrations
We are always working on new integrations. Please feel free to open an issue and ask for an integration. Contributions are welcome in any official or community repositories.
Official
- 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
- JetBrains Gateway Plugin: Open any Coder workspace in JetBrains Gateway with a single click
- Dev Container Builder: Build development environments using
devcontainer.jsonon Docker, Kubernetes, and OpenShift - Coder Registry: Build and extend development environments with common use-cases
- 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.
- Setup Coder: An action to setup coder CLI in GitHub workflows.
Community
- Provision Coder with Terraform: Provision Coder on Google GKE, Azure AKS, AWS EKS, DigitalOcean DOKS, IBMCloud K8s, OVHCloud K8s, and Scaleway K8s Kapsule with Terraform
- Coder Template GitHub Action: A GitHub Action that updates Coder templates
Contributing
We are always happy to see new contributors to Coder. If you are new to the Coder codebase, we have a guide on how to get started. We'd love to see your contributions!
Hiring
Apply here if you're interested in joining our team.