What changed from Vault
Preserved concepts, current contracts, explicit non-parity.
Vault was the Oversine implementation. Chroma is the Versine monorepo. The company
remains Oversine, Inc. Old source documentation is preserved in the repository's
apps/docs/archive/vault at commit 28f614609aba8c3673c098923b1e63ff586c75bf.
It is historical, not published as current integration guidance.
Carried forward
The platform keeps its own authentication/session layer, Versine acts as the OIDC provider, agents complete a browser-bound code handshake, and the user retains control. The platform and agent quickstarts now live at the same docs paths.
Deliberate differences
| Legacy material | Current behavior |
|---|---|
| Oversine branding / auth dashboard | Versine; separate Console and My |
| Multiple broker recipes | Auth0 only; Okta and other brokers deferred |
approve_sign_in | complete_authentication_handshake with code + exact page URL |
| OAuth connector registration/login | Manually created revocable MCP bearer connections |
| Partner tool catalog / read-write permissions / execute_action | Not implemented |
@oversine/react, hosted button script, legacy SDK versions | No compatible published Chroma package promised |
/auth, /me, partner JWT exchange | Use current discovery; these are not current public routes |
confidential_code / public client setup | Confidential Auth0 client; S256 or explicit nonce profile |
| Automatic agent acceptance of platform terms | Versioned human approval when platform legal fields exist |
Legacy amr: ["agent"] | Namespaced provider claim; downstream mapping is explicit |
| Dashboard deletion/export/30-day automation | Contact-based requests; no self-service deletion/export UI |
| Old grant tombstone and tool-concurrency guarantees | Do not infer them from historical design notes |
Documentation and policy changes
The current guides add Google, organization onboarding, encrypted optional details, exact-200 webhooks, My/Mobile approvals and operational/test boundaries. Terms and Privacy have been rewritten as current-feature drafts; deployment, retention/legal bases and final adoption still need owner review.
Policies
Read Terms of Service and Privacy Policy. They name Oversine, Inc. as the legal entity and Versine as the product. A review banner is not an assertion that counsel has approved the documents.