Desktop workspace
Editor, meetings, search, settings, and agents in one native app that runs on the user machine rather than in a browser tab.
Developers
Build on top of a workspace that runs on the user's machine.
Write actions and custom views that load from a folder, run in a sandbox, and ask before touching anything. No marketplace to get through, and no server in the middle.
Major parts.
What you are building against. It is a local extension surface today — we are not promising a broader platform yet.
Available
Local application core
Storage, search and embeddings, Local Whisper, plugins, and background jobs run on the device. Generative AI uses the cloud route you chose — your own provider key, or Wrengle AI — and every network boundary is documented.
Plugin host
Finds your plugin, registers its views, validates its actions, and runs it in a sandbox. Anything it wants to reach is gated behind a grant the user approves.
Plugin API
Shared contract types and a local SDK to build against. The interface can still change between versions, and there is no distribution channel in v1.
Where to start.
The plugin docs cover building an action, adding a view, requesting access, and what is not possible yet.
Introduction
BetaWhat Wrengle is, what it is not, and how to read availability labels.
Getting started
BetaOpen the app, create a vault, write notes, and check limitations before relying on workflows.
Dictation and voice control
BetaTalk to write into a note, or drive the app by voice. Setup, accuracy settings, what stays local, and how to fix it when it mishears you.
AI and privacy
BetaWhich AI runs where, what each one receives, and how to keep a piece of work entirely on your machine.
Workflows
BetaBuild a workflow, try it safely, then schedule it. Includes what approval gates catch and where the scheduler stops.
Retired local AI models
BetaWhat changed, how legacy choices stay non-executable, and how to remove old app-owned model files without touching speech or search assets.
Terminal
BetaA shell inside your workspace, with per-vault startup settings, restored sessions, and commands drafted from workflows.
Integrations and actions
BetaCreate Gmail drafts behind an exact-request approval, create Jira issues from the editor with account-backed Atlassian OAuth, or use configured webhook actions. See the availability table before relying on any connection.
Vault and backup
BetaWhat lives in the vault, what to back up, and why git history is not a full backup.
Sync across your computers
BetaWhat syncs between your own computers, what Wrengle stores and can read, and how to turn it off or remove a vault from the server.
Known limitations
BetaCurrent beta caveats across downloads, meetings, AI, plugins, and platform support.
How Wrengle works
BetaWhat stays on your machine, what crosses the network and when, and what plugins can reach.
Plugins overview
BetaWhat a plugin can add to Wrengle, how you install one from a folder, and what it has to ask permission for.
WASM plugin actions
BetaBuild a plugin that does work: declaring what it needs, getting access granted, and troubleshooting it when it will not load.
Plugin UI contributions
BetaPut your plugin where you will actually reach it — command palette, slash menu, right-click menus, shortcuts, status bar, and side panels.
SDK and plugin creator
BetaStart from a template, use the plugin SDK, and handle the approval step when your plugin wants to write something.
Plugin views
BetaAdd your own tab to the workspace from a single HTML file, and pass the current selection into it.
JSON Compare tutorial
BetaA worked example with no build step: load the JSON Compare plugin, open it from the palette, and send it a selection.