Watch on YouTube
Watch on Vimeo
Dave Ahr, a developer relations engineer at Coder, demonstrated how Coder workspaces give coding agents a controlled place to run, rather than a developer’s laptop. Workspaces are lightweight, ephemeral environments that can run as a Kubernetes pod, a process on a VM or bare metal server, or a Podman or Docker container. Ahr stressed that Coder is self-hosted, not software as a service (SaaS). Each workspace comes from a Terraform-written template, which Coder uses because most companies already have Terraform skills. Platform and security teams can build security bundles into a template and either let users pick one at creation or lock one in. Templates also set allowed destinations, such as GitHub or specific Go, npm, and Python package sources, and Ahr confirmed for a delegate that a template can restrict packages to a specific artifact repository and pin versions. He described a workspace as a “virtual laptop in the cloud” and recalled challenging a developer who refused to give up his laptop to explain how he would manage the cost and governance of 500 copies of Cursor running locally. Ahr also showed Coder Agents, which he nicknamed the “Coder Concierge” because customers increasingly use it to write templates and set up Coder while running Claude Code or Kiro in their workspaces, and he said he used it to build the demo environment.
Ahr then walked through an architecture he built with AWS that runs Coder workspaces on Amazon EKS with Nitro sandboxes, lightweight VMs with hardware-level isolation. Each workspace container comes preloaded with Claude Code, the Kiro command-line interface (CLI), shell tools, and source code, and runs under a restricted pod security policy with a Squid proxy controlling outbound traffic. When an agent needs to write to an S3 bucket, a pod identity agent issues short-lived, just-in-time credentials instead of standing ones. Agents never hold model API keys. Each one holds a credential only to the Coder control plane, which verifies it and calls Amazon Bedrock or Anthropic on the agent’s behalf using credentials Coder keeps. Coder connects to the customer’s identity provider, such as Okta or Microsoft Entra, and applies role-based access control, so when an employee leaves, their access ends without any keys to track down and rotate. Ahr added that Coder’s open-source product includes features that benefit individual developers, while enterprise features such as AI governance are paid.
In the live demo, Ahr connected to a workspace through code-server, which Coder created, and noted that Coder also connects to VS Code Desktop, Kiro, Cursor, Windsurf, and other IDEs that support remote connections, with about 50 milliseconds of latency in the demo. When he asked Claude Code to fetch several websites, the workspace blocked the unapproved domains. The AI Gateway logged each session and its tool calls under the admin settings, giving teams a date, time, and session ID to investigate further in tools such as Datadog, Grafana, Splunk, or Amazon CloudWatch, though Ahr said Coder is not trying to replace existing observability stacks. Customers who use a different gateway, such as Envoy, get their logs from that tool instead. Workspaces can also run on a schedule, such as a large bank that stops them at the end of the week and restarts them Monday while keeping their storage. Asked what he sees in the market, Ahr described a wide gap between companies like Spotify running multi-agent systems and companies that don’t know where to start, along with a rise in citizen developers outside engineering who need guardrails. He said the early rush toward AI agents has slowed after incidents such as PocketOS and Replit, and that companies still need software and security gates to stop agents from acting outside their intended limits.
Personnel: Dave Ahr, Jiachen Jiang
Thank you for being part of the Tech Field Day community! Our mailing list is a great way to stay up to date on our events and technical content, and we appreciate your signup.
We promise that we’ll never spam you, send ads, or sell your information. This list will only be used to communicate with our community about our events and content. And we’ll limit it to no more than one message per week.
Although we only need your email address, it would be nice if you provided a little more information to help us get to know you better!