infiniti.rewrite source and run it locally. You will finish
with a .clipsx archive and a transformation result attached to a harmless sample
clip. This is a guided build of an existing package; use it to learn the contract
before making a new package with your own identity.
Prerequisites
- Git, Node.js with npm, and Rust installed through rustup.
- The native Tauri build prerequisites for your operating system: the wrapper builds a tool from the desktop repository.
- A ClipsX desktop build compatible with Extension API v3.2. Confirm that the source tooling and installed app support the same contract; a newer source checkout does not upgrade your installed app. Check the extension contract and available desktop builds.
- A working generation model for the runtime exercise. Follow Local AI setup. Building and validating the archive does not require Ollama to be running.
sdk/wit/clipsx-extension.wit
and the host WIT aligned; do not change the API version to bypass compatibility errors.
Get the source
Run these commands in a new working directory. The two checkouts must be siblings for the default wrapper to locate the host:git rev-parse HEAD in each checkout. This guide does not require building or
releasing a new desktop installer.
If your host checkout is elsewhere, set CLIPSX_REPO to its absolute path in the
current shell before running package commands:
Build and validate the archive
From theclipsx-extensions checkout:
test command checks compatibility, manifest, assets, limits, and component
structure. It does not run the model or verify a desktop interaction. The output
archive is a local development artifact, not a published or signed release.
Import it into ClipsX
- Open Settings → Extensions → Developer.
- Enable Allow local packages.
- Choose Install local .clipsx package and select
dist/rewrite-local.clipsx. - Read the requested permissions before consenting. Rewrite requests selected input and generation; it also declares capabilities for optional copy-triggered automation.
- Find Rewrite under Installed and ensure it is enabled.
infiniti.rewrite. If you already have the registry
version installed, this is the same package identity, not a separate demo. Review
the existing installation before replacing it.
Developer Mode permits unsigned packages; leave it off when you no longer need
local imports. Existing permissions still apply.
Verify a first result
- In Intelligence → Models → Usage & defaults, assign a chat preset to Extension text generation. Verify its connection and model are available.
- Copy this harmless sample:
- Open the clip and choose Rewrite, then Business.
- Run the transformation. Inspect the result and compare it with Original.
- Copy the result deliberately, or choose Save as new clip to keep an independent clip.
Understand and change the example
Read these source files before changing behavior:- Manifest: package identity, permissions, the transformer, parameters, named setups, and activation.
- Rust guest: generation requests, validation, output, and tests.
- Pinned WIT: the guest/host interface.
package script is limited to its listed first-party packages. New packages use
the host CLI’s pack, validate, inspect, and test commands described in the
contract.