Skip to main content

Release Depth and Public Readiness

These docs describe Telemus AI's capabilities, availability, and current limitations.

Current status: public accounts and subscriptions​

Anyone can create a Telemus account and subscribe through Stripe. Verify your email before signing in. Account signup and billing are public; app availability depends on the platform and release channel. See Get the app for available downloads and access instructions.

Quest testing channels may require a separate Meta release-channel invitation. A Telemus account or subscription does not replace that invitation or establish that a build is available in every store. A successful local test does not establish production readiness on every device or with every connected service.

Research-to-plan-to-review-export-resume workspace loop​

The intended end-to-end experience is:

  1. Complete onboarding and connect or defer an AI provider.
  2. Start research from the workspace.
  3. Review outputs and pending actions.
  4. Export a read-only handoff pack through supported export controls.
  5. Close the app and resume the same project and workspace.

This workflow remains under validation. Check the active build, platform support, and the limitations published for that release before relying on it for important work. Keep separate backups where your workflow requires them.

Current support boundaries​

  • Platform availability, installation, licensing, and connected services vary by build. See Platform Support and Installation.
  • Cross-device workspace synchronization depends on the configured service and supported devices. Peer-to-peer sessions remain private testing functionality; do not assume production invite, conflict-resolution, or recovery support.
  • Some cloud-drive setup and mobile notification workflows require operator configuration and are not available as complete self-service flows.
  • Avatar availability and capabilities vary by build. Testing access does not grant permission to redistribute application assets.
  • Only supported extension types are callable. A listed or discoverable integration is not necessarily configured or available in your installation.
  • Browser-based clients are flat interfaces. They are not a supported production XR surface.
  • Third-party native plugin distribution and a public plugin marketplace are not announced production features.

Before installing​

Check Get the app for your platform, then confirm how to obtain updates, recover your account or licence, report a problem, and export your work. Follow the instructions for your release channel. Where a channel is invitation-only, access is limited to that channel and does not announce general store availability or platform certification.

See Permissions and Data Handling for execution defaults and privacy controls, and Release Readiness for the checks used to assess releases.