Your Playbooks are now Skills, and can be referenced in Workflows, manually invoked with a slash command, or called by the Player when it thinks a Skill is relevant to its task. You can upload existing agent skills from other tools into PlayerZero and use them for your own work, as well as allow your team to discover and use them for your shared work. Import a .zip file or, if you really like what a Player did in a single thread, click Create skill on that response to quickly make a new skill and save it to your organization’s skills library.Teams can capture richer, reusable expertise and let PlayerZero draw on the exact materials a task needs. The Skills you already depend on keep working, now with room to grow.
The Workflow Inbox has been redesigned around a sidebar you curate. Pin the workflow inboxes you care about, expand each one into its stages, and see a live count badge on each inbox and stage so you always know where work is waiting. Your sidebar layout, including which workflow groups are collapsed, now persists between visits.People who run several workflows can focus on the ones that matter to them and tell at a glance which stages need attention, without rebuilding their view every time they return.
The Recent Threads page moved sorting and filtering into the header row of each column, and added a new Workflow Inbox column showing a thread’s workflow and current stage for quick filtering alongside the thread’s creator.Scanning a busy project takes less work, and threads waiting on a stage approval now raise the same attention indicator as threads waiting on a question, so nothing that needs you looks idle.
Project owners can now set a default workflow for each team role in their system (engineering, support, product, etc.), so the right workflow is preselected whenever that kind of work begins. Your home page also remembers your workflow choice per project and per role: take on a new role and its default applies until you choose your own, and a Reset to Default action clears your choice whenever you want.Teams start work in the intended workflow without hunting for it, and each person gets a home that reflects how they actually work.
Require Approval Before Agents Take Privileged Actions
You can now require human approval before an agent runs a privileged action, meaning writes and destructive operations. Turn it on for a single workflow from that workflow’s settings, or turn it on organization wide in Organization Settings under General, where it applies everywhere and takes precedence over the per-workflow setting. When an agent reaches one of these actions it pauses and asks, and the request can reach you in Slack or Teams as well as in the thread.Teams keep a human in the loop exactly where it matters without slowing down everything else, and can set the guardrail broadly or enable it only for the workflows that touch sensitive work.
PlayerZero can now send you a direct message in Slack or Teams when a thread needs something from you specifically. Direct messages previously covered only workflow stage approvals; they now also carry collaboration questions raised for a particular person and requests to approve a privileged action. Turn on Send direct messages for a project in Organization Settings under Collaboration, and choose the scope: all questions, direct questions only, or workflow approval questions only.Whoever a question is meant for gets it where they already work and can answer in place, so a thread waiting on one person no longer sits idle until someone happens to check the channel.
You can now speak instead of type. A microphone button in the chat composer and on the home page turns your words into text live, so you can draft a prompt hands-free and then accept it, cancel, or keep editing before you send.Composing a longer prompt or capturing a quick thought is faster.
When a project owner opts in, PlayerZero can now read the screenshots and documents attached to Linear tickets, bringing Linear to parity with Jira and Zendesk attachment import. Consent is off by default and available only when the Linear integration is enabled for the project.Investigations that start from a Linear ticket can use the images and files the ticket already carries, so PlayerZero works from the full context instead of the ticket text alone.
New Relic and Aha! are now recommended MCP connections you can add from settings with guided, prefilled setup.Teams can bring observability data from New Relic and product plans from Aha! into PlayerZero’s context quickly, using the same standard MCP connections as the rest of your tools.
One Personal Access Token for MCP and the Browser Extension
PlayerZero now issues a single kind of credential for personal integrations. Create a Personal Access Token from your user settings, choose whether it is for the browser extension or for PlayerZero’s MCP, and scope it to the projects it is allowed to reach. This update replaces the separate per-project token page previously used for MCP connector tokens.Anyone connecting an editor over MCP or setting up the browser extension follows the same short path, with clearer scoping and one place to rotate or revoke access.
PlayerZero now connects to OAuth-protected MCP servers that enforce stricter standards, such as token audience binding.More third-party MCP servers work with PlayerZero out of the box, so connecting the tools your team already uses is smoother.
