Perplexity Ships GLM 5.2 Orchestrator That Matches Claude Opus at One-Third the Cost

Perplexity just shipped a research preview of a new orchestrator model for Perplexity Computer, its cloud-based multi-model agent platform. The model is an adapted version of Z.ai's GLM 5.2, post-trained specifically for the Computer harness, and it is already live. The headline claim: near-frontier agent performance at roughly one-third the cost of Claude Opus.

What Perplexity Computer actually does

Perplexity Computer is a multi-model AI agent that accepts a natural-language prompt and autonomously plans, browses the web, manipulates files, and calls APIs to deliver finished artifacts. Built on Perplexity's internal orchestration framework, it routes each subtask to a specialized frontier LLM and chains tool operations into end-to-end workflows without manual intervention between steps.

Perplexity's bet is that the next frontier isn't "better answers" , it's execution. Instead of replying with text, Computer is designed to take an outcome you describe, turn it into a workflow, and then delegate tasks to sub-agents that do the work in the background. Until now, the central reasoning engine driving all of that orchestration was Claude Opus, which is powerful but expensive to run at scale across every task in a workflow.

The new orchestrator: GLM 5.2, adapted for agents

The new model is not a general-purpose release. It is a version of GLM 5.2 that Perplexity post-trained specifically for the Computer agent harness , meaning the model was further trained on agent-specific tasks, tool use patterns, and the Computer environment's particular demands. Under the hood, GLM 5.2 is a 744B total parameter Mixture-of-Experts architecture with 40B parameters activated per token, supporting configurable thinking modes for step-by-step reasoning.

GLM 5.2 delivers a solid 1M-token context and has undergone months of specialized training for long-horizon coding agent scenarios, covering high-value tasks such as large-scale implementation, automated research, and performance optimization. That makes it a natural fit for an orchestrator role, where the model needs to maintain state across many steps and tools without losing track of earlier decisions.