Governance you can verify

Putting AI agents to work across a company means deciding the terms they operate under. Origin sets those terms on the endpoint itself, so an agent works the way you decided, and what it does becomes a record you can review.

Policy can be displaced, though. Another system in your environment can set its own terms for the same agent, and from that point yours are not the ones in effect. Nothing about it looks wrong. The machine stays enrolled and healthy, the agent keeps working, and the record coming back from it quietly thins out.

Origin now watches the policy it set, and tells you when something has taken precedence over it or changed what it depends on. The finding stands for as long as the condition does. Governance you cannot verify is an assumption, and this is the part that makes it a fact.

Available per organization, on macOS and Windows.

Shared canvases

Until now a canvas lived in the browser that built it. You could assemble exactly the view your team needed for Monday and be the only person who ever saw it.

Canvases and the kernels behind them are now stored with your organization, so building one makes it available to everyone you work with. They follow the drilldown: open the same canvas on a single endpoint or one person and every widget re-runs narrowed to what is in front of you. Forking a built-in canvas gives the team something to work from rather than a private copy.

Editing changed too. Drag cards to reorder them and group them into rows, drag the divider between two cells to set how much width each one takes. What you arrange is what renders, in view mode and in exports.

The people behind the prompts

A hostname is not a person. As AI spreads across a company, understanding the work means knowing who it belongs to and how that person fits into the organization.

Directory integrations are now generally available for Microsoft Entra ID, Google Workspace, and Okta. Connect the directory you already maintain and Origin brings its people, groups, and organization details into the graph. When an endpoint can be matched to its directory owner, Explore rolls that person's activity together across devices, with their department and email alongside it.

All three integrations can sync a full directory. Microsoft Entra can instead start with selected groups, including nested membership, so a focused rollout does not require bringing in the whole organization.

Microsoft 365 Copilot, in context

AI adoption does not stop at developer tools. With Microsoft 365 Copilot, the same people are working with AI in Word, Excel, Outlook, Teams, and Copilot Chat.

Enable capture on a connected Microsoft Entra directory, and Origin brings those conversations into the same activity view as the rest of your captured AI work, attributed to their authors. The same review workflow now covers coding agents and the work happening across Microsoft 365.

Signals

Signals are deterministic rules that annotate the graph. Each looks for a specific, well-understood pattern in prompt text, tool calls, tool results, or tool definitions, and marks the exact activity where it matches. A signal is a finding, not a guess: it fires because a rule matched, not because a model thought something looked off.

The first set we’re publishing is security detections, on by default and maintained by Origin: credential and financial data, prompt injection, risky commands and exfiltration, tool poisoning. Each firing is anchored to the activity it found, so you can jump straight from a finding to the surrounding trace, or read it as a dimension across the fleet in Explore.

Role-based access control

Not everyone who uses Origin needs the same view of it. Until now, everyone who wasn’t an admin collapsed into a single "Member" role, so access was effectively all or nothing.

Role-based access control replaces that with a set of built-in roles that allow for more granular control, assigned by admins from User Management. Enforcement runs across both the interface and the underlying data: each role sees only the sections it should, analytics queries are scoped to the endpoints and data it’s allowed to read, and prompt content stays gated even for users who can see that a signal fired. Roles can map to your directory groups, so access follows the structure you already maintain.

The proxy-less agent

Version 1.5.15 introduces a proxy-less agent for collecting AI prompt activity from endpoints without placing anything in the network path.

The agent captures supported prompt activity directly from AI tools on the machine and ties it to the person, device, and surrounding endpoint activity. Prompts land in the same context graph as processes, files, and network connections, and show up in the same traces, analytics, and inventory, so teams can investigate AI-assisted work alongside the rest of the endpoint record.

Proxy-less collection requires no traffic interception, certificate changes, or new network trust. Install the agent and supported activity starts flowing into Origin. For organizations starting their AI visibility journey, this is the fastest path to a live record of AI work, and everything it captures carries forward as endpoints later move to the full agent.

The full agent remains the deepest view of an endpoint, observing activity on the wire in addition to endpoint context. The proxy-less agent is designed for faster deployment and coverage of tools that report their own activity.

Both paths build the same graph of AI work in Origin.

Managed rollout controls

Not every environment tolerates updates the same way. Some fleets want every endpoint on the newest agent as soon as it ships; others need version changes to follow their own validation and rollout schedule.

Agent auto-update is now a configurable policy, so Origin can adapt to either. Leave it on and endpoints stay current automatically. Switch it off and update timing moves into your own deployment tooling, while endpoints keep capturing and reporting as before. Turning it back on later requires no reinstall.