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.

Improvements

IT & rolloutIT teams can keep selected organizations on their own agent rollout schedule instead of receiving automatic agent updates.

IT & rolloutWindows deployments can omit the full network capture component when supported prompt activity is collected through another approved path.

EndpointsPrompt records keep a model label even when response-side usage data is incomplete.

EndpointsOrigin now reports the AI tools installed on every endpoint, even ones that aren't running full activity capture, so AI tooling is visible across the whole fleet instead of only on monitored machines.

EndpointsEndpoint inventory now finds more AI tools, including the Claude and Codex desktop apps and command-line tools installed in less common locations that earlier versions could miss.

IT & rolloutSupport reports can include attachments up to 250 MB, making it easier to send larger logs and diagnostic bundles.

Fixes

Codex capture no longer records unrelated background beacon traffic.

Fresh Windows wizard installs no longer fail before local agent data is initialized.

Endpoints with no assigned policy no longer restart repeatedly during session processing.

Windows endpoints installed without the full network capture component no longer restart repeatedly when that component is absent.

Perplexity web searches now appear as their own trace turn.

Chat exports no longer loop through forked conversation branches.