Improve Adoption and Efficiency in 2.31
What's New in 2.31
This release makes it easier for engineering teams to adopt autonomous workflows without breaking developer flow or giving up the governance controls enterprises require.
VS Code + Coder Tasks Integration Now Generally Available
Developers live inside their IDE. Every context switch to a browser tab to trigger a workflow, check logs, or monitor an agent breaks that flow. Coder Tasks is now built directly into the VS Code extension, so engineers can launch and manage autonomous AI agents without ever leaving their editor.
- Create and launch Tasks from the IDE: Select a workflow template, configure parameters, write a prompt, and kick off a Task — all from a dedicated Tasks view in the VS Code sidebar.
- Monitor and control without switching tabs: View agent chat logs, check Task status, pause or resume the workspace, and download audit logs directly from the Task History panel.
- Enterprise-grade by default: Every Task runs inside a secure Coder workspace with the correct repos, credentials, and network access already configured — no broad external access, no ungoverned SaaS compute.
To get started, upgrade to the latest version of the Coder VS Code extension. Read more in our blog.
Improved Lifecycle Control for Coder Tasks in Beta
When a task goes idle, it pauses automatically, freeing compute resources. While paused, a snapshot of the last conversation messages is visible in the UI and CLI. On resume, agents with session persistence restore their full context and continue working.
- Resume from where you left off: Pause and resume tasks from the CLI, API, or Tasks UI. Agents that support session persistence pick up exactly where they stopped.
- Pay only for active work: Intermittent Tasks no longer require always-on workspaces, reducing costs without changing how engineers work
Our Claude Code module has been updated for session persistence, and we are actively working to update our other agentic modules.
Share Access to a Coder Workspace in Beta
When something goes wrong in a workspace, getting another engineer in to help is still surprisingly hard. Without a first-class sharing mechanism, teams fall back on Slack threads, port forwarding, or external tools like VS Code Live Share — none of which give a collaborator true environment-level access. Shared Workspaces fixes that.
- Share the full environment, not just the surface: Collaborators sign in with their existing Coder account and get access to the same files, tools, services, and running processes — without becoming the workspace owner.
- Built for debugging and incident response: Bring in a teammate or support engineer to troubleshoot in real context, where the issue is actually happening.
- Auditable and policy-governed: All shared access is logged, revocable at any time, and respects your existing Coder policies. Premium deployments can restrict or disable workspace sharing entirely.
AI Bridge Client Tracking
You can now identify AI clients such as Claude Code, Codex, and Mux in the AI Bridge logs based on the user agent for improved cost attribution, usage insights, and compliance.
View the full changelog on GitHub. If you have questions or feedback, join the conversation on Discord or email us directly!