Ethan
196c61051f
> **PR Stack** > > 1. #23351 ← `#23282` > 2. **#23282** ← `#23275` *(you are here)* > 3. #23275 ← `#23349` > 4. #23349 ← `main` --- ## Summary Replaces raw error strings and infinite "Thinking..." spinners in the agents chat UI with a structured live-status model that drives startup, retry, and failure UI from one source of truth. This branch also folds in the frontend follow-up fixes that fell out of that refactor: malformed `retrying_at` timestamps no longer render `Retrying in NaNs`, stale persisted generic errors no longer outlive a recovered chat status, and partial streamed output stays visible when a response fails after blocks have already rendered. Consumes the structured error metadata added in #23275. Retry-After header handling remains in #23351. <img width="853" height="493" alt="image" src="https://github.com/user-attachments/assets/5a4a1690-5e22-4ece-965c-a000fd669244" /> <img width="812" height="517" alt="image" src="https://github.com/user-attachments/assets/e78d28ce-1566-48ca-a991-62c6e1838079" /> <img width="847" height="523" alt="image" src="https://github.com/user-attachments/assets/e5fd7b60-4a3c-4573-ba4c-4e5f6dbfbdc3" /> ## Problem The previous AgentDetail chat UI derived startup, retry, and failure behavior from several loosely connected bits of state spread across `ChatContext`, `AgentDetailContent`, `ConversationTimeline`, and ad hoc props. That made the UI inconsistent: some failures were just raw strings, retry state could only partially describe what was happening, startup could sit on an infinite spinner, and rendering decisions depended on local booleans instead of one authoritative model. Those splits also made edge cases brittle. Invalid retry timestamps could produce broken countdown text, persisted generic errors could linger after recovery, and streamed partial output could disappear if the turn later failed. ## Fix Introduce a structured live-status pipeline for AgentDetail. `ChatContext` now normalizes stream errors and retry metadata into richer state, `liveStatusModel` centralizes precedence and phase derivation, and `ChatStatusCallout` renders startup, retry, and terminal failure states with shared copy, provider attribution, status links, attempt metadata, and guarded countdown handling. `AgentDetailContent` and `ConversationTimeline` now consume that single model instead of juggling separate error and stream booleans, while usage-limit messaging stays on its explicit path. The result is a timeline that shows consistent state transitions, preserves accumulated assistant output across failures, suppresses stale generic errors once live state recovers, and has focused model, store, and story coverage around those behaviors.
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.