Generally available as of Oct 21, the Glean plugin's /glean_run command writes an agent as a spec.yaml plus instructions.md in your repo, runs and evaluates it from the coding agent, then publishes it to Glean's managed runtime with its permissions across 275+ enterprise sources. Only Auto mode agents are supported; Workflow mode still needs Glean's visual builder (docs).
Released Oct 20, the SDK chains Voxtral Mini Transcribe Realtime 3, a reasoning model like Mistral Small with tool calling, and Voxtral TTS 3 into one streaming pipeline that Mistral says finishes each turn in under a second, over SIP or WebRTC. Transcription starts at $0.0035/min via the API or self deployment, and Voxtral 2 callers have a migration guide since emotion moves from preset voices to inline tags…
Launched Oct 20 for Pro, Max, and Enterprise subscribers, the new mode runs planning, reasoning, and file work on device with Qwen 3.6 or the post trained PPLX Pro, working across local files plus Notes, Messages, Mail, and Numbers when you grant access. Perplexity recommends 36GB or more of unified memory, and you can still authorize cloud escalation for browsing, fresh info, or connected apps (9to5Mac)…
The Oct 21 release fixes sessions with many MCP tools showing a real API error as "prompt is too long" and running an unneeded compaction; per TurboAI, a 400 or 422 that names deferred tools now retries without them. It also fixes claude p inside cloud sessions reporting "Not logged in" when started without the session's environment variables…
The Oct 20 release gives dynamic workflow subagents native structured output on supported models, adds an assistedApprovalInstructions setting to steer Assisted Permissions, and stops local or loopback providers in providers.json from overriding Auto or your saved model. It also makes headless and SDK sessions skip MCP servers whose saved tokens need interactive sign in, and fixes the first prompt hanging silently when no model is selected…
As of Oct 19, assigning a Linear issue to Amp (or mentioning @Amp in a comment) starts a Linear Agent Session backed by an orb that runs as you, with progress and replies in Linear and the same thread viewable in Amp. A workspace admin installs Amp in Linear and can route Linear teams or projects to specific Amp projects, and each user connects Linear under Settings → Integrations & MCP…
Spotted something we missed? Start a thread.