For Power Users and Operators
Telemus AI provides diagnostic and operational controls in the native app, Command Center and terminal. Their availability depends on the connected host, platform, permissions and installed build. A status view reports what it can observe; an unavailable result is not a successful check.
Command Center
Command Center brings together conversations, tasks, automations, skills, memory, files, networking and host diagnostics. Use its sidebar and More menu to find panels. Smaller screens use a collapsible navigation menu.
The dashboard controls the configured host. Its filesystem, account and provider access are not automatically the same as those of a standalone browser workspace. Opening 3D Workspace uses the supported configured spatial view; it does not grant another device license or copy private chat into that world.
Sign in through the normal dashboard login or app-provided launch link. Hosted access requires the operator's secure deployment. Do not paste tokens into the address bar or a support conversation. Dashboard login, account linking and workspace permission remain separate checks.
The native Show Command Center action opens the supported dashboard for that app. Where a host capability is unavailable, the panel should explain the limit rather than claim an operation succeeded.
Conversations and tasks
Command Center provides session history, pinning, model preferences where
supported, and conversation controls such as /help, /new, /status,
/compress, /stop and /retry. Read the active conversation label before
sending, particularly when a channel destination is selected.
Kanban and Todos show the host's task boards. Supported actions include creating and updating tasks, selecting boards, and reviewing ready, running, blocked, completed or archived work. An assigned task or accepted dispatch is not proof that the task completed.
Some native features remain spatial-only, including particular games, camera capture and popup interactions. A dashboard status card for one of these features does not create a browser equivalent. Check Platform Support for the current boundaries.
Memory and files
The Memory panel can show supported local notes, profile information, history and recall settings. Changes require the applicable confirmation. Review the selected profile before importing, restoring or rolling back information.
Host file ingestion and private-text import have additional local-access restrictions. A remote dashboard cannot use an unavailable import workflow merely because it is authenticated. Supported private imports require the complete local review; ordinary tool approval is not a substitute.
Spaces can identify dedicated working folders on supported hosts. A filesystem checkpoint is different from a room resume snapshot. Checkpoints are unavailable for a filesystem root, the canonical user/service home, and folders that overlap the checkpoint store. Add an appropriate project folder through Spaces before using Checkpoints. Do not bypass the scope restriction.
When an import or repair reports that the change completed but its final audit record did not, inspect current state before retrying. A warning after a committed change does not mean that nothing happened.
Diagnostic status and recovery
Open Workspace Health in Command Center or use /doctor in the terminal.
A check can be healthy, degraded, unhealthy, unavailable, unconfigured, timed out
or skipped. An optional unconfigured feature is different from a failed feature.
A healthy status snapshot is not proof that a complete real-world workflow ran.
Follow the check's preservation and recovery guidance. Keep existing work, skill files, pairing and pending messages. Do not clear application data or resend an uncertain action to make a warning disappear.
After a repair, perform the relevant functional check: recall a known memory,
open an expected skill, hear a short spoken reply, or verify a new channel message
after resolving pending delivery. Run safe repairs and /doctor fix still
require confirmation. If recovery fails, give support the check name and error
code, not keys or private message content.
Observability and support
Use Observability or show_observability to inspect available agent activity
and recent actions. Telemus Operations shows available session, channel,
approval and host-status information. These views can be incomplete when a host
cannot supply the relevant observation.
The Safe Action Audit Log shows retained records of governed actions. A resolved confirmation records a decision; it does not prove that every later step of the task completed. The same pending approval can be reflected in native, Web, terminal and supported channel controls.
Support tools include:
show_support_bundleandexport_support_bundleto review or save a redacted diagnostic bundle.email_support_bundle, the Send via email action or/support-emailto save the bundle and open a draft in your own mail app. Review the file and attach it as instructed. Telemus does not send the email for you.crash_report,export_crash_reportand Error Dashboard for available local error information./inspect <output_id>to read an output's evidence report, or/inspectto list the current workspace inbox.
An empty error report is not an all-systems health certificate. Some error and usage sources are not instrumented on every platform. Model-usage estimates can be unavailable and should not be mistaken for a provider's billing statement.
Telemetry
Telemetry collection is opt-in. Use telemetry_status, telemetry_opt_in,
telemetry_opt_out and telemetry_export to inspect and control supported
collection. Opting out clears the pending analytics queue. Local crash reports
are a separate diagnostic feature.
Native, Web and terminal controls observe the connected host's telemetry state. They do not independently turn on collection on another device.
Temporary hosted-browser diagnostics
Support may enable a short hosted-browser diagnostic window and provide an explicit diagnostic link. A normal link does not start a new trace. Follow support's instructions to reproduce the issue once and stop collection afterward.
The bounded trace records lifecycle/error occurrence, timing, fixed categories and a short-lived random identifier. It does not collect page text, messages, raw error stacks, cookies, identity, full URLs or query values. It does not change your authentication or graphics settings. Browser termination can prevent the last events from arriving, so a trace is evidence for investigation rather than a guaranteed diagnosis. Server log retention is separate from the temporary identifier's lifetime.
The DevTools Console
The native DevTools Console supports the commands advertised by your build for inspecting state and debugging supported plugins. The in-world console keeps recent history and supports scrolling. A long display can be marked truncated; that is not proof that the underlying result was empty.
Command Center's Web DevTools panel is a restricted console. It is not a general remote interface to every native debug action. Use dedicated Web panels for supported product operations or an authorized platform tool for the required local workflow. Authentication does not bypass normal execution policy.
Browser automation also depends on its host. A supported desktop or companion can control its available browser. App-owned mobile/Web browser controls have a narrower scope and do not imply control over Mobile Safari, unrelated apps or arbitrary external websites. A synthetic screenshot or key event is reported as such; it must not be treated as captured page pixels or a native keyboard action.
The Networking Center
Use the Networking Center to inspect configured hubs, connection state and available NAT/STUN/TURN diagnostics. A successful connectivity probe is separate from workspace permission and completed sync.
For user actions, limits and recovery guidance, see Connectivity and Collaboration and Cross-Device Synchronization.
Skills, plugins and MCP
The Skills and Plugins panels show the supported catalog and installed items. Review a skill or plugin before enabling it. Installation or discovery does not grant new tool permissions.
The MCP Center shows bridge status and available tool, resource and prompt catalogs. A configured server is not necessarily connected. Read failures remain errors rather than appearing as an empty successful catalog.
Supported Web controls can retrieve an advertised MCP resource or prompt. The
terminal provides /mcp-resources, /mcp-prompts,
/mcp-resource-read <server> <uri> and
/mcp-prompt-get <server> <name> [arguments_json]. Retrieval follows the same
access and action policy as other tools. Catalog listings do not automatically
include private resource contents.
Supported desktop hosts can expose local authenticated MCP or ACP interfaces. Check the capabilities reported by the actual host. Local transport availability does not authorize exposing a listener publicly or imply that mobile and browser builds host the same service.
Scheduled jobs
Use Automations in Command Center, Cron Center in the native app, or
/cron in the terminal. /jobs, /j and /tasks are terminal aliases for the
schedule list.
| Terminal command | Purpose |
|---|---|
/cron status <id> | Read current schedule status. |
/cron history <id> | Read retained run outcomes. |
/cron pause <id> | Pause the schedule. |
/cron resume <id> | Resume an eligible schedule. |
/cron run <id> confirm | Request a new manual attempt. |
/cron delete <id> confirm | Delete the schedule. |
A manual attempt can repeat earlier side effects. It is not continuation of an old run or approval for every later action. A queued or running state is not completion. Blocked, cancelled, interrupted, skipped and error outcomes must be read separately from a successful result.
Required approvals remain required during scheduled work. A confirmation can resolve one action without resuming the original full task. Check the final receipt and output before requesting another attempt. Restart-interrupted or uncertain work may remain paused for review.
Create or update a schedule
Supported terminal clients use /cron create <JSON> and
/cron update <id> <JSON>. New schedules are enabled unless explicitly created
paused. Start paused when reviewing a new job:
/cron create {"name":"Daily summary","message":"Summarize tasks","schedule_kind":"every","every_ms":86400000,"enabled":false}
/cron update job-id {"enabled":true}
Supported fields include name, message, enabled, delete_after_run and
schedule_kind with its corresponding interval, cron expression or time.
Supported API clients can use authenticated /api/crons management routes.
Unknown fields and unsupported options are rejected rather than silently ignored.
Per-run model, reasoning and timeout options require a supported isolated job and
trusted local operator. Their displays are read-only in Web and native Cron
Center; use supported terminal/API or manage_cron controls to set them. A
selected model applies to that job, not global settings. A timeout requests
cancellation; it does not undo work already performed.
Channel-created schedules belong to their originating conversation. A remote channel cannot silently select another destination. Sending a result to a channel requires a supported delivery target and does not guarantee provider delivery.
Supported Linux/macOS hosts can use installed IANA time zones. Other builds may support only UTC. Unavailable zones are refused, never silently converted to UTC. Daylight-saving transitions can skip a missing local time or repeat a local time; choose the schedule with that behavior in mind.
An update can preserve omitted fields. If a create, update or run loses its connection, inspect status and history before retrying. Keep one active scheduler for a task while migrating it; two enabled copies can both run.
Terminal and process controls
The terminal TUI provides command suggestions, history and structured status
views for the connected host. /help lists supported commands. Terminal access
uses the host's existing permissions and action policy.
On supported Linux/macOS desktop builds, the in-app terminal can open a local
terminal session. terminal_sessions, terminal_new, terminal_kill,
terminal_send and terminal_send_control provide supported controls.
Sending input means sent, not that its command succeeded. If delivery fails,
inspect the terminal before retrying because part of the input may have arrived.
Unsupported or read-only terminal views refuse input.
Background process status and cancellation do not imply that all side effects are reversible. Use the result and exit status to decide what to do next.
Channel operations
Channels Center and Web Operations → Channels show connector setup, connection status and supported engagement controls. Test Connection reads current health; Setup complete only records that setup requirements were filled. Supported probes can be cancelled without changing saved provider credentials.
Use the channel conversation's own controls for active work. /compact requests
a history summary; /think selects a supported reasoning setting for subsequent
turns. These preferences do not change other conversations or the host's global
settings. Read channel controls
for approval, privacy and delivery limits.