Plugins and extensions

Jesusdiazrivero/langweave-plugins is the packaged form of langweave. Each package carries two things:

• The server — the same hosted https://api.langweave.tech/mcp the manual setups add, over HTTP with OAuth.
• The language-mode skill — the standing instructions that tell the model to fetch your profile before it replies, stay inside its limits, and log the words it used. The server sends the same rules on its own; the skill keeps them in front of the model in long sessions.

Path in langweave-plugins	For
.claude-plugin/marketplace.json, plugins/langweave/	Claude Code — below
gemini-extension.json, GEMINI.md	Gemini CLI — see Gemini CLI
skills/language-mode/SKILL.md	the same skill, where gh skill, Zed and Copilot look for one

Claude Code

The plugin is the one-step install for Claude Code: the server and the skill together.

1. In Claude Code, add the marketplace:

   /plugin marketplace add Jesusdiazrivero/langweave-plugins

2. Install the plugin from it:

   /plugin install langweave@langweave

3. Restart Claude Code if it asks you to, then run /mcp, choose langweave and Authenticate. Sign in on lexmem’s page in the browser and allow access.

If you have not chosen a language yet, do that at app.langweave.tech — every tool says so until you have.

Caution

If you already added the server with claude mcp add, remove that entry (claude mcp remove langweave) so Claude Code does not run two copies of the same server.

To update it, run /plugin marketplace update langweave.

Gemini CLI

The extension’s gemini-extension.json adds the hosted server, and GEMINI.md — the same skill body — is loaded into context, because Gemini CLI has no skill loader. Install it with gemini extensions install; the steps are on the Gemini CLI page.

The skill on its own

skills/language-mode/SKILL.md is the skill alone, at the top level where gh skill, Zed and Copilot look for skills. It does not add the server; connect that first, as on Any MCP client.

Nothing in it is edited by hand

Every file in langweave-plugins is generated from this repository on each release, so wording fixes go upstream rather than to that repository. The skill holds only the part of the contract that does not change between releases — the limits, the known words and what to introduce next always come fresh from the server — so an old copy is still a correct one.