Planning and Organization
Telemus AI provides notes, projects and task boards within a persistent workspace. Supported controls are available through the spatial app and connected Web or terminal surfaces. See the installed release's limits before relying on recovery or sharing.
Task boards
Organize tasks into To Do, Doing and Done. Ask the assistant to add work or use the available task controls. Helpers can contribute task results, but a helper summary does not certify completion. Review output before moving a task to Done.
Supported task data can be included in workspace backups. A backup does not resume running helpers or restore their authority. Imported ready/running work can require review before it becomes active again.
Notes and projects
Use Sticky Notes for short ideas and Projected Notes for longer writing. Supported spatial requests can move or expand them using room context.
Projects group related notes, tasks and artifacts. Pin a project to make the current focus explicit. Project Library manages supported projects; Project Graph helps inspect relationships. A missing source can appear as an unavailable reference rather than restored content.
Inspecting artifacts
Inspect Drawer shows available sources, activity and related context for a supported artifact. Inspect Workspace opens inspection for the current workspace. Evidence Inspection opens the Workspace Inbox review queue for evidence follow-through. Missing or ambiguous evidence is reported; a historical label is not proof of the current source version.
The Web Workspace Browser and terminal /artifacts list supported metadata,
not complete private artifact bodies or spatial restore controls. Use Web
Inspect or /artifact-inspect <artifact_id> for the limited evidence view.
The evidence view requires authentication and an active license; unauthenticated
development access is unavailable. It does not open the source content.
Explicitly private, redacted and deleted items are omitted from ordinary listings. Legacy entries without a privacy setting can remain visible. A visible title may still contain user-written sensitive information. If privacy state cannot be read safely, the view reports unavailable rather than treating it as public.
Resume and the Workspace Inbox
Workspace Resume can show the active project, recent actions, pending work, unavailable integrations and suggested next steps. Layout restored and default layout used describe different recovery outcomes.
Open Workspace Inbox or terminal /inbox to inspect supported review rows.
Depending on the row and surface, actions can include inspecting a result,
opening a task, reviewing an approval, retrying, dismissing or exporting a brief.
An unavailable action does not gain permission through a different label.
The native flat/XR inbox currently keeps approvals read-only. Use the originating approval dialog or supported Web/terminal inbox for a required approval action. After an expired or changed request, refresh and review the new row. Do not approve an older result as if it were a current action.
A dismissed row can reappear if its underlying condition changes. An empty inbox means no items are currently listed, not that every external task is complete.
Exports and privacy
A brief, a full export pack and a portable workspace bundle contain different data. A brief is a reduced summary, not a restorable snapshot. Full packs and bundles can contain task, automation and operational information that needs review.
Use the Workspace export controls, Web Workspace Import / Export, or terminal
/workspace-export where supported. Inspect the preview and resulting file before
sharing it. A successful write or an older “secrets exported: false” field does
not certify that the content is safe to share.
Eligible Web 3D brief exports offer Download brief. The offer can expire and can be cancelled. The browser determines whether saving succeeds; the offer alone is not proof of a saved file. Full-pack and portable-bundle downloads are separate capabilities and are not provided by that brief offer.
A failed export may leave a previous successful file available. Verify the reported result and destination rather than assuming the older file contains new work.
Backup and restore limits
Supported backups preserve task content, notes and workspace state within the current file limits. Oversized or invalid content can fail rather than partially restore. Older backups may omit newer kinds of data.
Import refuses conflicting identities or active task ownership where replacing those records would be unsafe. A fresh profile can help test a portable round trip. Importing a bundle and restoring a snapshot are separate actions. Private or redacted boards are not included in ordinary portable backups. Live cross-device sync is a separate workflow.
Memory and degraded services
Memory controls remain subject to current permissions and configured providers. Selecting a local store alone does not guarantee that all AI processing or embedding requests are offline.
When a provider or device connection is unavailable, inspect its reported status. Supported local artifacts and read-only exports can remain available, but cached content is not proof of current external-service state. A failed save requires attention even when other health indicators are good.