Guides

Recued Kitchen for VS Code

Write and check recipes and packs in VS Code. Use AI or send drafts to your own Recued server.

Recued Kitchen is the VS Code add-on for Recued source. It edits recipes, packs and compositions. A recipe is a list of steps. A pack is a box you can install. A composition sets out its parts and actions.

The add-on checks source as you type. It can show errors, fill in keys and find names. It can also use your VS Code AI tools. You can send drafts to the Kitchen on your server.

Local edits and checks need no account or server. You can read the built-in guides offline, too.

#Get Recued first

To run your work, first get Recued. Install the server and start it on your computer. Pair the webclient with the code your server shows. The webclient is the app in your browser.

Keep your server running when you use connected drafts. You can skip this setup for local edits and checks.

#Install the add-on

Install Recued Kitchen from the VS Code Marketplace. Check that the publisher is recued. You need VS Code 1.102.0 or later.

Open a folder for your source. Run Recued: Open Documentation from the Command Palette. Choose a built-in guide to read it offline.

#Make your first recipe and pack

  1. Run Recued: New Recipe.
  2. Save it as greeting.recipe.json.
  3. Change the greeting, then run Recued: Validate Current Source.
  4. Open the Problems panel. Select a problem to jump to its source.
  5. Run Recued: New Pack. Save it as example.pack.json and check it, too.

Each new file starts with a full example. Replace the pack's example names and API URL with your own. It does not call that API as you edit.

Use Recued: New Composition for a composition on its own.

#Name your source files

The add-on knows these file names:

Source File name
Recipe greeting.recipe.json
Pack example.pack.json
Composition example.composition.json

The source is JSON, a text format for data. Names ending in .jsonc work, too. But the source must still be strict JSON. Comments and trailing commas are errors. For another file name, run Recued: Set Document Type.

#Check and explore your source

Use the Problems panel to find errors. Try changing version from 1 to "bad". Check the file and select that problem. Then restore 1 and check again.

Use Outline to move between parts of a file. Hover over a key for help. Use completion to fill in known keys. F12 follows names to local source. Quick Fixes offer edits where a known fix is safe.

Recued: Validate Folder and Recued: Validate Workspace check files that are not open, too. A source check does not run your recipe. It does not test the API you plan to call.

#Set up your editor's AI

Use the AI model you set in VS Code. Its own sign-in or provider key still applies. To add one, run Chat: Manage Language Models. See VS Code's model guide.

Open a folder you trust. In Chat's tool picker, switch on these tools:

  • Recued Authoring Reference: read the guide built into this release.
  • Recued Workspace Operations: find actions declared in local packs.
  • Recued Validate Source: check the latest text in the editor.

Keep the usual file-editing tools on, too. This local AI flow needs no Recued MCP key. Your chosen AI provider handles prompts, source and tool results.

#Ask AI to write or improve source

Run Recued: Author with AI and choose a source type. Review the prompt. Choose Copy Prompt and Open New Chat. Paste it, add your goal and send it.

Use Recued: Improve with AI for a saved file. Problems can also offer Explain Problem with AI or Fix Problem with AI. Review each edit and check the result.

Recued: Enable AI Authoring for This Workspace can add scoped guide files and a prompt. It shows you the proposed files first. It keeps files that already exist. VS Code's own tool prompts still apply.

#Make an MCP contract

Do this when you want to open and save server drafts. MCP is a shared language that apps use to call your server's tools. A contract is the saved list of what one app may do.

  1. In the paired webclient, open Contracts → Others → + New contract.
  2. Name it, such as VS Code Kitchen.
  3. Switch on MCP tools and choose Create contract.
  4. Keep this contract active and its MCP tools door on.

A door is a way in that you open on purpose. Closing it takes that access away. Creating the contract does not grant tools by itself.

#Grant the four Kitchen tools

A grant is a yes you give ahead of time. Open the contract's Ops tab. Use Find an operation to search for Kitchen. Switch on these four grants:

Operation What it lets this connection do
core.kitchen.draft.import Send source to a new Kitchen draft
core.kitchen.draft.list List drafts made through this connection
core.kitchen.draft.get Read source from those drafts
core.kitchen.draft.update Save edits after checking the draft's revision

Each grant is separate. New contracts grant nothing by default. These tools do not install packs or run recipes. Other actions need their own grants.

#Connect VS Code to your server

  1. Open the contract's Connect tab. Choose Create a key.
  2. Copy the key while it is shown. Recued shows its value only once.
  3. Find the full MCP URL in that tab's connection examples.
  4. In a trusted VS Code folder, run Recued: Set Up MCP Connection.
  5. Enter that URL, then the contract's key.
  6. Check that setup reports 4 of 4 Kitchen tools are granted.

Your server must be reachable from VS Code. Use the full URL, such as https://your-server.example/mcp. HTTPS is required outside localhost. HTTP works for localhost, 127.0.0.1 and [::1].

Setup also adds the server to VS Code's native MCP support. The four server tools are separate from the three local AI tools above. The draft commands work without an AI model.

#Open and save Kitchen drafts

Run Recued: Send to Kitchen with your local source open. Review the draft name, then send it. Open Recued: Show Kitchen or use the Kitchen icon in the Activity Bar.

The view lists drafts made through this connection. An empty list can be normal before your first send. Select a draft to open its source.

Edit it, then run Recued: Save to Kitchen. A normal file Save only saves your local file. It does not send a Kitchen write. For an unlinked local file, Save to Kitchen first lets you pick a draft and compare it. A second Save to Kitchen sends the source.

Installing a pack or running a recipe is a separate action in Recued.

#Review approvals and conflicts

Recued's write rules still apply. If it asks you first, review the action on your paired device. Cancelling the wait in VS Code does not cancel an action already sent.

Recued: Compare with Kitchen shows local and server source. If someone changes the server draft, the add-on refuses to overwrite it silently. Use Recued: Resolve Kitchen Conflict to review the versions and edit the result. Then choose Recued: Save Reviewed Resolution.

Recued: Open Latest Kitchen Source opens the newer source on its own. It keeps your current buffer.

#Recover an uncertain transfer

If a reply was lost, run Recued: Resume Kitchen Transfer. It checks what happened or resumes waiting. Pending writes do not replay by themselves after a restart.

Recued: Recover Kitchen Transfer Source opens the stored source without sending a write. Pending transfers may keep source in local workspace state. Recued: Forget Kitchen Transfer Tracking stops local tracking. It does not cancel a server action.

#Keys, access and disconnecting

VS Code keeps the connection key in its secret store. The add-on does not put it in your project files or change the server's grants.

Run Recued: Disconnect to remove the saved connection. Local buffers and recovery records stay. To take back server access, turn off the key on the contract's Connect tab. Other apps using that key lose access, too.

A new key does not gain access to drafts from the old key. Use a current, contract-owned key. If an old key still lacks the tools, make a new contract with the four grants. Check the grants again if setup reports fewer than four tools.

#More help

The built-in guides match the add-on release you installed. Online pages can describe a newer release. Keep service keys in named connections. Review source before sending, installing or running it.

Recued Docs

Search documentation

Start typing to search the documentation.