Changelog #14

Devboxes

Coding agents are great until they take over your computer for 20 minutes. Devboxes give agents their own isolated cloud VM to work in, so you can keep going.

Pick a repository, pick a size, and in seconds you have an environment with your code checked out and ready to go. The agent runs there. You keep working.

Isolated by default. Devboxes are designed with isolation as a feature, not a constraint. Agents cannot escape the Devbox or access anything outside it. You can safely run an agent without the interruption of approving every command.

Run multiple workstreams in parallel. Agent refactoring in one Devbox, a test suite running in another, a proof of concept in a third. Jump between them whenever you're ready.

Connect however you want. Browser-based VS Code, SSH, or CLI port forwarding, whatever fits your flow.

Devboxes run on the same infrastructure as your CI, with full access to Namespace's build caching.

Learn more →

Trust Relationship Management

You can now securely access your Namespace resources from anywhere using OIDC-based trust relationships. This makes it easier to authenticate external workloads like CI pipelines or cloud services without managing long-lived credentials.

To get started, check out the new CLI commands for managing trust relationships, or head to the new Trust Relationships tab under Workspace → Federation in the Namespace cloud console.

• CLI reference: Trust Relationships
• Cloud console: Trust Relationships

Extended Cache Support

We've expanded our caching integrations to cover more toolchains, making it easier to speed up builds whether you're running in CI or working locally.

sccache

Two new commands make it simple to set up sccache with Namespace:

• nsc cache sccache create-token: generate a scoped token for sccache access
• nsc cache sccache setup: configure sccache to use Namespace as its remote cache backend

Gradle

Gradle caching has gotten a round of usability improvements, with simplified token management for both CI workflows and local development.

In a workflow, use short-term credentials bound to the runner:

nsc gradle cache setup --init-gradle /path/to/init.gradle
gradle --init-script=/path/to/init.gradle build

From a local workstation, generate a user-bound token with a configurable expiry:

nsc gradle cache create-token --expires_in 7d
nsc gradle cache setup --token token.json --user

This sets up your Gradle cache config in the Gradle user home using a token tied to your current user. If the user is removed from the workspace or their permissions change, the token is automatically invalidated and it can be manually revoked at any time.

Self-Service SSO Configuration

Workspace admins on an Enterprise plan can now configure SAML SSO directly from the dashboard. Set up your identity provider, manage SSO-enforced domains, and enable directory auto-join without reaching out to support.

• Workspace access documentation
• Cloud console: Workspace settings

Summary

That's a wrap on the highlights from the last few weeks. Devboxes let agents do their thing without taking over your machine, trust relationships make it easier to connect external workloads without the hassle of long-lived credentials, expanded cache support means faster builds across more toolchains, and SSO management is now fully self-service. Check out the changelog for the full list of changes.