Alpha program

Known Issues & Limitations

Last updated: August 2, 2026 · Production release 0.10.1

coThink is in an Alpha phase. Features marked Preview or Alpha in the product may change, produce incomplete results, or require administrator configuration. See also our Terms of Service (Beta, Preview, and Experimental Features).

Preview Features

• Document Intelligence — extraction and search over uploaded documents uses deterministic/heuristic pipelines. OCR and advanced parsers may be disabled; verify critical facts independently.
• Meeting Intelligence — analysis of meeting transcripts and notes is heuristic, not human-reviewed, and must not be treated as authoritative records.
• Included AI — platform-managed AI on the free path is subject to daily fair-use limits and shared model availability. Connect your own provider (BYOM) for higher volume or model choice.

Flag-Gated Rollouts

Onboarding v2, subscription redesign, and some guidance surfaces may not be enabled for every workspace during Alpha. Administrators enable cohort flags per integration/docs/alpha-scope.md.

Integrations

• Google and Microsoft 365 / Exchange Online calendar/mail connectors are in Alpha scope (microsoft-integration); production connector smoke evidence is collected per release.
• On-prem Exchange (EWS plugin) follows the same connector smoke/evidence bar as other integrations and may require administrator configuration.

Entitlements & administration

• Plan, feature-matrix, and enterprise RBAC enforcement run in enforce mode in production and staging inventories. Denied actions are blocked server-side.
• Inventory drift checks (rbac:drift), observe-mode comparison harness, feature-entitlement route audit, and OpenAPI drift run in Integration CI.
• Privacy retention jobs may run in dry-run mode until purge enforcement is enabled in production inventory.
• Marketplace and session-library publication safeguards are under Alpha scope review.
• Third-party App Store — public executable third-party installs are enabled in production (MARKETPLACE_PUBLIC_EXECUTABLE=true) for Team+ plans when packages are signed by a verified publisher, sandbox-attested, and not quarantined. Package sandboxing is enforced: third-party UI runs in a sandboxed iframe host, and third-party tools run through a Worker/WASM tool host (allowlisted imports only; no in-process third-party JS). Platform-admin quarantine kill-switch and publisher key revoke remain available for incident response.

Operations

• Production deploy and public health smoke are automated; backup/restore drill and RPO/RTO acceptance require operator sign-off.
• Runner pool separation and token rotation require Gitea administrator actions outside the application repository.

Reporting Issues

Report Alpha defects through your workspace administrator or sign up and contact support channels documented in the incident runbook. Include tenant slug, route, and approximate time (UTC).

Scope reference: Alpha scope document