Changelog

Alpha now has one developer surface

Alpha’s MCP server, REST API, OpenAPI definition, and official TypeScript and Python SDKs now come from the same reviewed catalog. A tool added to that catalog can appear consistently in every supported developer surface. Internal administration and maintenance functions stay private.

Every API and MCP request now receives a request ID and writes to the same audit ledger. This makes failed calls easier to trace without storing secrets or sensitive arguments.

Safer onboarding and routing

The final onboarding step now refuses to start an empty ingestion. Users must connect at least one account source and save at least one destination vault first.

Drive selection now presents files and folders as a reviewable table, includes shared drives, and treats a selected folder as the parent of its matching contents. Teams and Slack use exact conversation selection instead of keyword routing.

Connected graphs that stay still while you inspect them

Graph ingestion now preserves relationships between entities instead of producing isolated nodes. The graph takes a fresh snapshot on page load and no longer restarts its layout repeatedly while new data is arriving.

Artifacts that open where the work happens

Reports, documents, charts, and workbooks now advertise the correct file type. Rich documents can include Mermaid diagrams, tables, and editable content. Artifact links can also produce richer previews in Slack when Work Object Previews are enabled for the Alpha app.

Clearer access requests and notifications

Members can request access to an existing vault instead of creating a duplicate. Vault admins receive the request in Alpha and by email, choose the person’s vault role, and can add them to other vaults during approval. Requesters are notified when the decision is made.