Developers
Build extensions for what people copy.
Turn copied text into a useful view, a transformation, or an action. ClipsX provides the clipboard workspace; your extension adds the workflow.
One clip. A useful result.
Rewrite is a first-party example: selected text goes to the configured generation model, and the result stays beside the original clip.
Copied text
hey can you send the updated diagram before friday? need it for the review
Rewrite · Business
Attached result
Could you send the updated diagram before Friday? We need it for the review.
Illustrative workflow and generated output. A local generation model is required for Rewrite; results need review.
Build the workflow. Reuse the workspace.
Work with selected content
Add detectors, views, transformations, and actions for supported clip formats. Keep the first version focused on one useful task.
Use host-managed capabilities
Declare the input, model, or network access you need. ClipsX manages consent and provider credentials; your package works through the documented contract.
Keep results useful
Transformer results remain attached to their source clip. People can inspect, compare, copy, or save them without replacing the original.
From source to your first local run
- 01
Build
Start with the Rewrite source and its pinned WebAssembly contract. Follow the guide to build a local archive.
- 02
Validate
Run the package checks against the same host revision. Review the manifest, requested permissions, and generated archive.
- 03
Try it in ClipsX
Import through Developer Mode, enable the package, and run it on harmless sample text. Inspect the result before copying it.
Explicit permissions. Clear limits.
- Packages have no ambient clipboard history, filesystem, shell, or network access. Additional access goes through declared host capabilities.
- Model-backed workflows need a configured provider. Local views and transformations can work without an LLM, depending on the package.
- Validation and signatures help check compatibility and package provenance. They do not guarantee safe behavior or useful output.
- A local archive is for development. Registry distribution has a separate release and catalog review process.
Available today: desktop extensions. A hosted public API is not available.
Help build the ecosystem
Explore a package you use, report a reproducible issue, or discuss a new workflow before building it. Keep package work and desktop host changes in their respective repositories.