Skip to main content

Extensibility and Plugins

Telemus AI supports reviewed plugins and reusable skills. Availability depends on the extension type, runtime, host and installed release. A listed declaration is not proof that it can execute.

Plugin controls​

Use the Plugin Manager to discover installed plugins, inspect their source and requested permissions, and enable or disable them. Supported extension types include tool actions, export providers, project-graph providers and agent helpers. Bounded read-only panels have a separate view.

Approved tools can be discovered with list_plugin_tools and invoked through call_plugin_tool, subject to the normal action policy. Installing a package, fetching its files and approving execution are separate decisions.

Review the exact package version and permissions before allowing code to run. Resource-only declarations do not grant execution or filesystem access. Public marketplace availability is not implied by local plugin support.

Runtime limits​

  • JavaScript (QuickJS): Supports reviewed code in a constrained embedded runtime. It does not provide ordinary Node.js process, network or filesystem APIs. Tool access requires the appropriate reviewed grant.
  • Python Mini: Supports limited expressions; it is not a general Python interpreter. Full scripts require a configured supported external host.
  • WASM: Supports small reviewed modules, currently limited to 64 KiB with a 100 ms execution deadline. Split larger work or use an appropriate external host where permitted.
  • Native: Built-in integrations and guarded dynamic loading are distinct capabilities. Dynamic native packages are limited to supported desktop configurations and are unavailable on Windows, mobile and Web.
  • External Node/Python: Reviewed packages can run on compatible desktop or headless hosts. They run as the current operating-system account and are not isolated from that account's ambient files, network or credentials.

Permission declarations help review and app policy; they are not an OS sandbox. A timeout cannot undo an action that already ran. Install executable packages only from sources you trust.

Read-only plugin panels​

Choose PANEL in the spatial Plugins view or open the contribution in Web Plugins. Terminal users can use /plugin-panel <extension_id>. Refresh runs the supported contribution again; Close returns to discovery.

Panels display bounded text rather than arbitrary HTML or native controls. Their view does not grant live workspace or tool access. Views are temporary and are cleared when account, profile or workspace changes. Unsupported runtimes or unavailable account context leave the panel unavailable.

Skills and MCP​

Skills are instructions that the assistant can read with skill_view and follow using available tools. They do not replace normal permission and approval rules. See Skill Library before installing executable support content.

Connected MCP servers may advertise tools, resources and prompts. Listing a resource does not download it, and listing a prompt does not apply it.

  • mcp_resource_read reads an advertised resource using its exact server and URI.
  • mcp_prompt_get retrieves an advertised prompt and its supported arguments.
  • server: "local" selects the supported local catalog.

A disconnected server, unavailable transport or unsupported response reports a failure. An external MCP server operates within its own trust and access boundary; review that server before connecting it.

Browser side panel​

Supported Chrome/Edge side-panel and Firefox-sidebar packages can show Telemus chat beside the current page. Capture or Send shares bounded page context after a user action with the configured Telemus dashboard. Routine browsing is not continuously captured by this workflow.

Configure the intended dashboard and its credential in extension settings. Check the destination before sending private page content. The full workspace remains a separate action.

Unavailable extension workflows​

Generic plugin execution does not support arbitrary import handlers, workspace processors or lifecycle hooks. Private text importing is not yet a usable end-to-end workflow. Its protected editor and private-body controls are unavailable; do not paste private import text into shared chat or terminal history as a workaround. An internal or development control does not grant access.