Published June 13, 2026 under Apache 2.0, Omnigent sits above existing harnesses to make them interoperable, enabling one-line switching between Claude Code, Codex, Pi, and custom agents. It adds contextual security policies (e.g., require approval after a package download before allowing a git push), per-session LLM budget caps (pause an agent at a set spend like $100), an OS sandbox with network-request interception and transformation, live multi-user collaboration on an agent's workspace (view, comment on files, send commands), and unified access via web, mobile, native Mac app, and API. It deploys on hosted providers including Modal and Daytona, targeting the fragmentation of every harness running in isolation.
2026-04-29 / SKILLSDatabricks Ships Unity AI Gateway: MCP Governance with On-Behalf-Of Agent Permissions, Fine-Grained Tool Access Control, and End-to-End Agent ObservabilityDatabricks merged AI Gateway into Unity Catalog as Unity AI Gateway, extending enterprise governance to agentic AI by controlling which agents access which MCP servers, APIs, and LLMs with the same permissions model used for data. The key feature is on-behalf-of (OBO) user execution for MCP calls, ensuring agents operate with the requesting user's permissions rather than broad service credentials, preventing unauthorized data access. The platform provides a unified API across models with built-in fallbacks, rate limits, guardrails, and end-to-end observability that attributes costs across models, teams, and workflows. 2026-04-16 / SKILLSDatabricks Unity AI Gateway: Agent Governance with On-Behalf-Of User Execution, MCP Permissions, and Cross-Model Cost AttributionDatabricks extended Unity Catalog into agentic AI with Unity AI Gateway, applying enterprise governance (permissions, auditing, policy controls) to how agents access LLMs and MCP servers. The key feature is on-behalf-of (OBO) user execution: when an agent calls an MCP server, it runs with the requesting user's exact permissions, not a shared service account — if a user can't access a Salesforce record, neither can their agent. Also includes end-to-end observability across LLM and MCP calls with cost attribution per model, team, and workflow.