The Workspace Settings Page That Used to Say "Coming Soon"
A workspace-level agent policy has existed in the backend since early on. For a long time, nothing could actually read or write it — here's the gap, and what finally closed it.
For a while, opening a workspace's detail page in Settings got you a card that said, essentially, "workspace configuration coming soon." That placeholder sat there for longer than it probably should have — not because nobody cared about workspace-level configuration, but because of a quieter gap underneath it.
A workspace-level agent policy — a spend ceiling per run, a list of forbidden capabilities, an approval threshold before higher-risk actions — had existed at the platform level for a long time. The backend route to read and write it was real, and the enforcement logic that narrows every agent run against that policy had been live the entire time. What didn't exist anywhere was a screen. Every workspace on the platform had effectively been running with an empty, unconfigured policy, not because anyone chose that, but because there was no way to choose anything else.
That's a specific and slightly uncomfortable kind of gap: the feature wasn't missing in any meaningful engineering sense — it was a column in a database and a well-tested enforcement path. It was missing in the only sense that actually matters to someone trying to use it.
What closed it
The fix was, honestly, unglamorous: build the form. An admin can now see a workspace's current policy, set a per-run spend cap, choose an approval threshold, and manage the forbidden-capabilities list — all against the same backend logic that had been sitting there the whole time, doing nothing because nobody could reach it.
Why this is worth telling as a story, not just a changelog line
It's a useful reminder of a pattern that isn't unique to this one page: real, working infrastructure can sit fully built and completely unused for a long time, simply because the last, least-interesting mile — the actual screen — didn't get built alongside it. The "coming soon" placeholder wasn't lying, exactly. It was just describing the gap between backend and interface more honestly than anyone probably intended.
If you manage a workspace here and haven't looked at its settings page recently, it's worth another look. The thing that used to be a stub now does something real.