Install from a folder
Point Wrengle at a folder on your machine and it loads the plugin from there. No marketplace to publish through and no review queue to wait on.
Plugins
Make Wrengle do something it does not do yet.
Load a plugin from a folder on your machine — one you wrote, or one you built by describing it. Each plugin asks before it can reach your notes, and you approve every change it wants to make. There is no marketplace yet, and the interface can still change between versions.
What exists today.
Deliberately local and deliberately explicit while this is still finding its shape. There is no marketplace, and that is a choice rather than a gap.
Beta
Actions that do work
Write a plugin that transforms text, calls something, or automates a step, and call it from a workflow or the command palette.
Custom views
Add your own tab, settings page, or side panel from a single HTML file. It runs sandboxed, so a broken view cannot take the app down with it.
Put it where you will find it
A plugin can add itself to the command palette, the slash menu, right-click menus, keyboard shortcuts, the status bar, and side panels.
Nothing happens without permission
A plugin asking for access is not the same as getting it. You grant each capability, and any change to your notes comes to you as a proposal to approve.
Start from a template
The built-in creator scaffolds a working plugin and shows you exactly which permissions it will ask for before it writes the folder.
Build one by describing it
Plugin Builder turns a description into a view or small app using your Wrengle colour palette. On macOS, it automatically shares preview screenshots with your selected image-capable model for visual review and repairs before installation. Built apps stay offline; workspace reads require permission and note changes remain proposals.
Pick where to start.
Building an action, adding a view, and wiring it into the interface are different jobs. Open the one that matches what you are making.
Build an action
The manifest, the action contract, asking for permissions, and the build and test commands.
Use the SDK and creator
Start from a template, use the SDK, handle errors from the host, and route note changes through an approval.
Create a view
Declare a view, ship it as one self-contained HTML file, and receive theme and selection updates from the app.
Add it to the interface
Palette entries, slash-menu items, context menus, shortcuts, status-bar buttons, settings pages, and docked panels.
Try JSON Compare
A worked example with no build step: load it, open it from the palette, and send it a selection.
Build one by describing it
Describe what you want, preview it before installing, refine it, and roll back when an edit goes wrong.