Test a plugin in Jacker
Before you publish, run your plugin in your own Jacker. Developer mode uses the plugin straight from its folder, so you can edit and try again without packaging.
Before you begin
- Start Jacker with plugins switched on:
JACKER_PLUGINS=1 pnpm desktop:devfrom the jacker repository. - Open a project that Jacker trusts. Plugin programs don’t run in an imported project you haven’t trusted.
Check its programs
Before loading the plugin, start its programs the way Jacker talks to them:
jacker-plugin test PLUGIN_FOLDER
For each language server, test sends initialize, then shutdown. For each stdio tool server, it sends MCP initialize and tools/list, and checks the tools against Jacker’s limits and your readOnlyTools. It prints one ok line per program, or what went wrong, with the last lines the program printed.
If the plugin declares required settings, pass them:
jacker-plugin test PLUGIN_FOLDER --config KEY=VALUE
test runs programs with the environment Jacker gives them, but not inside Jacker’s sandbox, and doesn’t test http tool servers. A program that works here can still fail in Jacker if it needs a file or folder the sandbox denies; loading the plugin shows that.
Load your plugin
- Run
jacker-plugin validate PLUGIN_FOLDERand fix any errors. - In Jacker, open Plugins in the rail.
- On the Installed tab, click Load local plugin… and choose
PLUGIN_FOLDER.
The plugin appears labelled Local, unverified. Jacker reads its folder again each time it lists plugins, so a change to plugin.json shows the next time the list refreshes.
You can’t load a folder for a plugin id you’ve already installed from the marketplace. Remove the installed one first.
Read what’s wrong
- Failing with a reason: the manifest is invalid, a file it names is missing, or a required setting isn’t filled in.
- Incompatible:
engines.jackerdoesn’t include this Jacker’s version. - A language that isn’t coloured or indexed: see the notes in Editor colouring with Monarch and Code map queries.
- A tool server that doesn’t start: Jacker’s log at
~/.jacker/logs/orchestrator.logrecords “plugin tool server unavailable for this run” with the reason.
Settings
If your plugin declares config, its row on the Installed tab has a settings form. Saving restarts the plugin’s language servers and tool servers, so they get the new values.
Unload
Click Unload…, then Unload. Jacker forgets the plugin; your folder isn’t touched.