Skip to main content
Changelog Masthead Background
Back to changelog
v2.39

Project-Level Memory for Coder Agents in 2.39

What's new in 2.39

Give Coder Agents your conventions, context, and skills once, at the project or organization level, and every chat builds on them. Platform teams can also trace any workspace connection end to end and see every editor their developers use.

Coder Agents: Shared context and admin controls

Set conventions, skills, and model access once instead of repeating them in every chat or organization.

  • Organization skills and instructions: Admins publish skills and instructions once per organization, can limit them to specific groups, and every change is recorded in the audit log.
  • Manage model access in Terraform: The coderd Terraform provider can now set which users and groups can use each Coder Agents model, and configure Claude Platform for AWS. View the provider release.
  • Projects: Group related chats in projects with shared memory, instructions, and skills, so each new chat builds on the last one.

Script ordering for templates

Template authors can set the order coder_script resources run with the new coder_script_order data source, so dependencies install before an IDE or AI coding agent starts. It's in beta, opt-in, and requires Coder Terraform provider v2.20.0 or later. Learn more in our documentation.

More improvements

  • Trace any workspace connection end to end: VS Code, JetBrains Toolbox, coder ssh and the web terminal tag each session with one ID across client, server and agent logs, so platform teams can find why a connection dropped in a single SIEM search, without debug flags. Learn how to trace workspace connections.
  • See every editor your developers use: Template Insights, connection logs, and Prometheus now track each editor by name, including VS Code forks such as Cursor. See the connection logs and Prometheus docs.
  • VS Code extension 1.17: Developers now see a warning when a startup script fails or times out. Version 1.17.0 also includes a security fix, so we recommend updating. Learn more in our documentation.

Security updates

We've recently patched several disclosed vulnerabilities. Check our security advisories, and watch for new releases on GitHub to hear about patches first. For updates on vulnerabilities we have patched, visit the Coder Trust Center.

Breaking Changes

  • #30466: A migration rewrites the connection_logs table under a lock that blocks reads and writes, about 50 seconds per 10 million rows. Plan a maintenance window for large deployments.
  • #29796, #29906: Template insights and the coderd_insights_applications_usage_seconds metric now report per app. In the API, type is replaced by method. In the metric, application_name is now display_name. Update dashboards, alerts and scripts.
  • #30150, #30140, #30199: coder update and coder users edit-roles --roles now ask for confirmation, so scripts need -y. coder update also returns an error if the restart fails.
  • #31262: Template builds fail if a coder_app URL uses an unsafe scheme such as javascript:. Check templates before upgrading.
  • #30256: API keys created from a scoped token can't go beyond that token's scopes.

View the full changelog on GitHub. If you have questions or feedback, join the conversation on Discord!