Writing Jacker plugins
These pages are for developers who want to add a language or agent tools to Jacker. After reading them you can build a plugin, try it in your own copy of Jacker, and package it for the marketplace.
They don’t cover how Jacker loads plugins internally.
What a plugin can add
A plugin adds one or both of the following:
- Language pack
- A language Jacker doesn’t know yet. It can give the code map symbols for that language, colour it in the editor, and run a language server for completions, diagnostics, and go-to-definition.
- Tool pack
- Tools that agents can call, served by an MCP server. Agents on every engine (Claude Code, Kimi Code, Codex, OpenCode, LangChain) get them.
Plugins can’t add panels, commands, or themes to Jacker’s interface.
Pages
Start here:
Reference:
- The plugin.json manifest
- What a plugin’s programs can reach
- Code map queries
- Editor colouring with Monarch
- Guidelines for MCP servers
Shipping:
The author kit
jacker-plugin is the command-line tool for authors. It starts a plugin from a template, checks it, starts its programs to see that they answer, and packages it. It's one file that runs with Node 22 or later.
To get it, download it and check it:
curl -fsSLO https://storage.googleapis.com/evolve-491413-jacker-plugins/kit/jacker-plugin.cjs node jacker-plugin.cjs --version
That address always serves the newest version. Each version is also kept under its own name, with checksums, so you can pin one:
curl -fsSLO https://storage.googleapis.com/evolve-491413-jacker-plugins/kit/jacker-plugin-1.0.0.cjs curl -fsSL https://storage.googleapis.com/evolve-491413-jacker-plugins/kit/SHA256SUMS | shasum -a 256 -c -
Run it with no arguments to see its commands. The examples in these pages call it jacker-plugin; make an alias, or replace jacker-plugin with node PATH/jacker-plugin.cjs:
alias jacker-plugin="node $PWD/jacker-plugin.cjs"
To browse what others have published, see the plugin marketplace.