PlayerZero AI Players now launch directly from Slack conversations. Use shortcuts, app mentions, or message actions to create Players without leaving your support channels—complete with workflow context, conversation threads, and attached images automatically captured. Players created from Slack carry multi-origin provenance tracking, storing the channel and thread references for full auditability.What this means for your teams: Support engineers eliminate context switching between Slack and the dashboard — every conversation thread becomes investigation provenance automatically. Engineering managers convert bug reports into tracked investigations automatically. QA teams capture reproduction steps inline during testing. Product managers preserve feature requests with full conversation context. Every investigation step is documented.
We added public document sharing for Player artifacts with granular access control. Toggle any AI-generated document between private and public, then share a stable URL with external stakeholders — no authentication required for public documents.What this means for your teams: Customer success shares investigation summaries with clients without granting platform access. Technical writers embed AI-generated documentation in external wikis with stable URLs instead of copy-paste. Support managers provide detailed responses via ticketing systems with full context preserved. Engineering teams collaborate with external partners using links that maintain metadata — player name, creation timestamp, and investigation provenance — without manual export overhead.
PlayerZero now learns from past investigations and surfaces relevant context automatically. The memory system captures your knowledge and leverages it to improve response quality over time — like a digital immune system that gets stronger with every exposure.What this means for your teams: Senior engineers document tribal knowledge that surfaces automatically in future investigations. Support teams build a searchable knowledge base from resolved issues without manual wiki maintenance. QA engineers record test scenarios and edge cases discovered during investigation—AI suggests similar patterns when relevant. Engineering managers track architectural decisions with their rationale, accessible through semantic search instead of scattered documentation. Every investigation strengthens the system, reducing duplicate work and improving response consistency across teams.
We replaced the legacy workflow editor with a full-screen visual builder. Design your backlog stages, draw connections between them, and configure transition rules through an intuitive node-and-edge interface — no more parsing text-based configuration. The builder validates workflow integrity in real-time, showing warnings on stages with no incoming or outgoing connections. Auto-reorganize uses a hierarchical layout algorithm to clean up complex workflows when things get messy.What this means for your teams: Iteration speed increases dramatically — drag to reorganize, draw to connect, click to configure. Engineering managers, DevOps engineers, Support leads, and Product managers more easily design and update their issue triage, incident root cause analysis, customer request escalation, and feature discovery workflows to match, or even improve upon, their existing internal processes.
We introduced org-scoped repository lifecycle controls and human-friendly configuration names for all SCM connectors. Administrators now activate, deactivate, or delete repositories at the organization level with type-to-confirm safety guards — governance without project-by-project management overhead.New org-scoped endpoints manage repository state with cascading updates to all project references. When you toggle a repository’s active state at the org level, the change propagates to every project automatically. All SCM providers (GitHub, GitLab, Bitbucket, Azure) now support optional configuration names, displayed as “Configuration Name (Provider Type)” for clarity. Reconnect actions preserve all project associations.What this means for your teams: Engineering directors, security administrators, and DevOps engineers govern code visibility and access across multiple teams from a central control plane with clear ownership requirements — only org owners can delete repositories. IT administrators audit connected repositories for compliance using friendly names instead of cryptic IDs. Reconnection becomes painless when tokens expire or permissions change — refresh tokens without recreating the entire integration.
We added session renaming with real-time updates across all connected clients. Assign meaningful names to long-running investigations instead of relying on timestamps—better organization, better team coordination.The rename action appears in the player title bar dropdown. Validation enforces trimmed, non-empty strings with a 70-character maximum. Every connected viewer sees the title change instantly without page reload.What this means for your teams: Support engineers organize multiple concurrent investigations with descriptive names instead of hunting through timestamps. Engineering teams track related debugging sessions across sprints by naming them after features or issues. QA engineers label test runs by scenario or build number for faster retrospective analysis. Find past investigations in seconds using meaningful names instead of remembering when something happened.
We introduced message-level deep linking throughout Player threads with persistent “Copy Link” actions for assistant and deep-research messages (or a hover button for user messages), and smooth scroll-to-message navigation. Share precise references to AI responses or user questions—no more “scroll down to the part where it talks about authentication.What this means for your teams: Engineers reference specific AI analysis in code review comments with clickable links instead of vague descriptions. Support teams share exact responses when escalating to engineering — “look at this message” becomes a URL. Deep links include full conversation history, so context is never lost.
We redesigned error presentation in Player conversations to show friendly headers with collapsible debug details. Errors now surface first-line summaries inline — full diagnostics available behind a toggle when you need them.What this means for your teams: End users encountering errors see manageable incidents with clearer next steps.
