Start with the right sources in the right vaults
You can now review every connected account, routing rule, selected folder, and destination vault before the first sync begins. Alpha will not launch an empty ingestion, and Drive, Teams, and Slack show the exact files or conversations you approved.
Shared Drive folders are included, selecting a folder covers its matching contents, and private Slack channels clearly explain when Alpha must be invited first.
Follow connected work without a moving graph
The knowledge graph now preserves relationships between people, systems, decisions, problems, and source evidence. It loads a fresh snapshot when you open the page, then stays still while you inspect it instead of restarting its layout during ingestion.
Reports, briefs, charts, and workbooks now open with the correct file type and can include readable diagrams, tables, and source-backed recommendations. Artifact links can also render richer previews in Slack when Work Object Previews are enabled.
Use the same scoped knowledge from code and AI clients
You can now access Alpha through MCP, the REST API, and official TypeScript and Python SDKs. Each surface uses the same reviewed public capabilities and vault boundaries, while administration and maintenance operations remain private.
Every API and MCP response includes a request ID, giving support and developers a safe way to trace failures without recording secrets or sensitive arguments.
Improvements and fixes
- Members can request access to an existing vault instead of creating a duplicate.
- Vault admins receive access requests in Alpha and by email, choose the vault role, and can add the requester to more vaults during approval.
- Requesters are notified when access is approved or rejected.
- Microsoft connections request the combined permission set so adding Outlook, Teams, or OneDrive no longer removes another Microsoft service.
- Slack detects an installation that is missing channel-join permission and offers a reconnect action.