Skip to main content
Extensions recognize, preview, transform, or act on compatible copied content. No optional package is installed by default. Try visualization without an LLM, then add generation when needed.

​
Install and review

  1. Open Extensions in ClipsX and browse the catalog.
  2. Review package details, provenance, version, permissions, and prerequisites.
  3. Install and enable the package using its controls. Grant only access you understand.
  4. Open a compatible clip and select its available preview or transformation.
Signatures and checksums establish provenance and integrity, not a guarantee of safety. Updates can change behavior and require renewed permission review.

​
Try a Mermaid visualization

Install and enable first-party Mermaid, then copy:
Open the captured text and choose the available Mermaid view. Inspect the diagram alongside the original. This requires no generation model. If unavailable, check enablement, content compatibility, and package diagnostics.

​
Try a Rewrite transformation

  1. Create a chat preset in Models and assign it to Extension text generation in Usage & defaults.
  2. Install first-party Rewrite and review its generation permission.
  3. Copy Please send the updated meeting agenda before Thursday.
  4. Open the clip, choose Rewrite, and select Concise or another available setup.
  5. Run it, inspect the result tab, and compare with Original before copying or pasting.
Generated text can change meaning. Save as new clip creates an independent clip; attached results remain associated with the source. Automatic rules are optional and configured separately. Start manually.

​
Automate matching copies

For repeated work, select a built-in or saved setup in the extension’s Automation rules. Add an optional Only run when… question to evaluate copied text with General decisions before the operation runs. Rewrite uses its generation assignment to write the result. Test conditions on harmless samples and review rule order; only the first matching rule runs for each operation and capture. See Conditional extension automation for setup, priority, consent, and recovery. Results stay attached to the original; automation never copies or pastes.

​
Understand the boundary

Bounded WebAssembly packages do not receive ambient access to all history, files, or the network. Network destinations and external navigation must be declared and granted for the exact release. Generation uses the host’s configured provider. Review permissions after updates. Credentials and grants do not sync automatically. Authenticity is separate from trust in the author’s behavior.

​
Disable or recover

Disable unwanted packages through their controls. Repeated failure can quarantine a package: inspect diagnostics, prerequisites, and permissions before enabling it again. Original clips are preserved. Deleting a source removes its attached results. See Local AI recovery and Troubleshooting.

​
Build extensions

The developer guide and Rewrite implementation cover authoring. You do not need them to use a package.