Cloud Workspaces

Control the agents that run while you sleep.

From virtual machines and containers to Coder workspaces: wherever your agents run, Bay finds and steers them.

Why autonomous agents are hard to secure

Teams now run agents like Claude Code, Codex, Gemini CLI and GitHub Copilot in clusters, cloud workspaces and hosted sessions, where they work for hours with real permissions and no one watching.

Most never mean any harm. But a determined agent with a vague goal will find a way around, and the tools you already have can’t see inside the container. Bay can.

How it works

Every agent in your cloud workspaces, surfaced

Discover every agent across virtual machines, Kubernetes, Coder workspaces and hosted sessions, along with the MCP servers and skills each one uses.

The Bay console listing the AI tools it has found, with session and risk counts

Know what each agent can reach

See which credentials, secrets and permissions each cloud agent can reach, and lock down the risky ones before a long-running task puts them to use.

Two Bay finding summaries, one critical and one resolved, with severity and affected endpoints

Steer agent behavior at runtime

Intent-aware enforcement on every tool call. Bay sees the whole session, not just the last action, so it knows what the agent is trying to do. When no one’s around, it steers the agent back on course instead of pausing the work.

Bay policy update suggestions, each offering to change an action from block to warn

Every autonomous session, on the record

Full transcripts of prompts, actions and MCP calls - traceable to the person behind each session.

Two Bay finding summaries, one critical and one resolved, with severity and affected endpoints

Every agent in bounds, wherever it works.

The same agent can run on a device, in a browser and in a cloud workload, reaching the same systems and data each time. Bay learns how your organization works and applies one set of policies everywhere, so nothing slips between tools.

See it in action

Frequently asked questions

Hosted AI agents are AI agents that run in the cloud rather than on a person’s device. Examples include Claude Code sessions in the cloud, Claude Cowork tasks that keep working after a laptop closes, and coding agents running in Coder workspaces, containers or Kubernetes. Bay secures hosted agents wherever they run, so every agent in your cloud workloads stays within your policies.

Bay secures Claude Code in cloud environments the same way it does on a device. It reasons over the whole session, from prompt to tool call to system action, and understands what the agent is trying to accomplish. Whether Claude Code runs on the web or on your own infrastructure, Bay allows, asks, denies or steers each action in milliseconds.

Bay secures long-running AI agents by reasoning over the whole session, however long it runs. It remembers every step and understands the goal behind the agent’s actions. When a long-running agent drifts from its task or reaches for something it shouldn’t, Bay steps in without stopping legitimate work.

Yes. Most teams start in simulation mode to see how their hosted agents behave, then turn on enforcement once policies are tuned. Nothing is blocked until you decide it should be.

Live in 5 minutes. Tailored in an hour.

Works with your stack without replacing it.