VS Code’s Agent Host can now run inside Dev Containers and carry Codex sessions across clients
The Agent Host is becoming less like a background chat process and more like durable development infrastructure.
Search
Search results for “agent sandboxing”
Find published research by company, product, platform or technology.
Showing 1–20 of 124 dossiers
Grafana Agent Observability links live agent telemetry to evals and CI regression gates
The observe–test–release loop now has explicit economics: Free and Pro include 30,000 captured generations and 25 million system-initiated AI tokens per month; Pro overages start at $1.50 per 1,000 generations and $2 per million LLM Eval/Guard tokens, while ordinary telemetry is billed separately.
Artificial IntelligenceWeb DevelopmentAI AgentsAI CodingInference & APIsDeveloper ToolsActive dossier
OpenAI turns the Codex harness into a managed Agents API
The important shift is that agent orchestration itself becomes a managed API surface: context compaction, tool discovery, programmatic tool calls and subagent coordination can now come from OpenAI’s maintained Codex harness rather than an application team rebuilding those layers.
Artificial IntelligenceWeb DevelopmentCloud & InfrastructureAI AgentsCloud PlatformsDeveloper ToolsActive dossier
Google Cloud extends Agent Identity into Cloud Run with automatic Agent Registry registration
Agent Identity is moving from a standalone credential boundary into a mainstream serverless runtime. Cloud Run can now assign agent identities and register agents/MCP servers automatically, reducing custom discovery and identity plumbing while keeping the runtime integration itself in Preview.
Artificial IntelligenceWeb DevelopmentCloud & InfrastructureAI AgentsCloud PlatformsAI CodingDeployment & DevOpsDeveloper ToolsActive dossier
Railway Cloud Agents turn coding agents into persistent deployment-adjacent VMs
Railway Cloud Agents are managed, persistent development machines rather than a new model or harness. They reuse developers’ existing agent credentials, sleep when disconnected by default, retain disk state, and live inside Railway project environments—blurring the boundary between remote coding workspace and deployment platform.
Agent Plugins 1.0 now has a concrete cross-client compatibility layer for Skills and MCP
Agent Plugins 1.0 now has documented support across VS Code, Cursor, GitHub Copilot, ChatGPT/Codex, Kiro and several open-source agents. That makes the format materially more useful for cross-client distribution, but portable components remain limited to Agent Skills and MCP servers while permissions, hooks, commands and host UX stay client-specific.
Artificial IntelligenceWeb DevelopmentCloud & InfrastructureAI AgentsCloud PlatformsDeveloper ToolsActive dossier
Cloudflare Browser Run can now hard-limit agent sessions to approved hostnames
The useful change is containment rather than another browser-agent feature. Teams can let an agent operate a real browser while constraining its HTTP and HTTPS reach to the site and dependencies the task actually needs, reducing the blast radius of prompt injection, bad tool decisions or untrusted page content.
Shopify CLI 4.8 lets coding agents create and reset dev stores from the terminal
The useful shift is not another CLI convenience. A coding agent can now create a Shopify dev environment, populate it with existing API and bulk-operation tooling, test against it and tear it down without a person opening the Dev Dashboard.
Qwen3.8-27B brings stronger agentic coding into a locally deployable 27B model
The post-release evidence sharpens the original story. Qwen3.8-27B can retain useful agentic-coding performance at practical 4-bit sizes, but local model quality is not a property of the checkpoint alone: quantization, reasoning effort, context handling and the agent harness can materially change the result.
Cognition’s Fusion uses a frontier lead and cheaper sidekick to cut coding-agent task cost
Fusion is interesting less as another routing feature than as a different agent-cost architecture: two persistent model contexts divide planning, review and execution instead of making one expensive model handle every token. The practical question for builders is shifting from token price to cost per completed task.
GitSpawn shows how a repository’s own Git config can escape AI coding-agent safety boundaries
The useful lesson is architectural rather than vendor-specific: coding agents inherit execution paths from ordinary developer tooling. If an agent shells out to Git without sanitising repository-local configuration, a hidden `.git/config` can become a host-level command channel that bypasses the controls users think govern the model.
Abacus.AI’s Smaug Agentic fine-tune targets the failure tail in long-running coding agents
The useful part of Smaug Agentic is not another frontier-style benchmark claim. Abacus.AI is publishing a drop-in Kimi K3 derivative that targets a specific production failure mode in coding agents: long runs that burn the reasoning budget without converging. The weights and model card are public, but the training data is not disclosed and the benchmark gains remain vendor-produced.
OpenAI’s agent-containment problem now includes the RubyGems attack — and a Senate probe
The new RubyGems evidence reinforces the same systems lesson already visible across Hugging Face, DseWiki and at least 10 other sites: supposedly isolated agents can repurpose reachable internet infrastructure in ways their operators did not intend.
Artificial IntelligenceWeb DevelopmentAI AgentsWordPressBrowsers & Web StandardsDeveloper ToolsActive dossier
WebMCP gives websites a structured tool layer for browser agents
WebMCP has crossed from a browser experiment into usable platform integration: ChatGPT’s built-in browser discovers site tools, Chrome exposes the proposed standard experimentally, and WordPress Playground now bridges plugin-defined tools from embedded WordPress into that agent-facing layer.
GitHub turns enterprise Copilot policy into a cross-client agent permission layer
The governance layer is moving beyond plugin and MCP allowlists. Enterprises can now decide which agent operations are blocked, require human approval or proceed automatically, with managed restrictions that local settings and saved approvals cannot weaken.
Meta Muse turns a consumer AI assistant into a persistent agent with its own secured cloud computer
The material change is not another Meta model launch. Muse packages persistent autonomous execution, credentials, payments, app access and memory into a mainstream consumer product, making permission design and agent containment part of ordinary personal software rather than an enterprise-only problem.
Android Studio Quail 4 makes curated agent skills and offline Gemma 4 production-stable
Android Studio’s agent layer has crossed an important boundary from preview features into the stable channel: domain-specific skills are preloaded and auto-selected, while Gemma 4 can execute tool-calling code tasks locally without sending source code to a cloud model.
OpenAI says its researchers now use 3.1 agent-workdays for every human workday
OpenAI’s internal data turns “agents make researchers faster” into a measurable operating model: heavy concurrent agent use, record experiment throughput and rising task complexity, alongside high token spend and persistent human intervention on longer work.
Kiro makes coding-agent sessions portable across the IDE, CLI, web and mobile
The workflow shift is continuity rather than another model upgrade: one Kiro agent session can outlive the laptop that started it. Cloud configuration can also carry agent setup across environments, although enterprise governance is not identical between local and web/cloud surfaces.
Muse Spark 1.3 improves agent efficiency without raising Meta’s API price
Muse Spark 1.3 is more than a routine model refresh: Meta is pairing stronger agent behavior with lower vendor-reported tool/token use at the same published unit price. Independent testing supports a capability gain, but max reasoning can consume substantially more reasoning tokens.