Recued Kitchen

Write and validate Recued recipes, packs and compositions in VS Code. Get local Problems, completion, navigation and source review, use your editor's AI tools, and optionally open and save Kitchen drafts through MCP.

New to Recued? Visit recued.com to download, install and set up Recued first when you want to run your recipes and packs or connect Kitchen drafts. Follow the server installation and first-device setup, then create the contract and MCP connection described below.

Local authoring, validation and documentation work offline. No Recued account, server, MCP connection or AI provider is required to get started.

Start in two minutes

1. Install Recued Kitchen from publisher recued and open a folder for your source.
2. Run Recued: New Recipe and save it as greeting.recipe.json.
3. Edit the greeting and run Recued: Validate Current Source. Select findings in the Problems panel to jump to their source.
4. Run Recued: New Pack and save it as example.pack.json to try pack authoring.
5. Run Recued: Open Documentation for the bundled getting-started, AI, Kitchen-draft and feature-reference guides.

Requires VS Code 1.102.0 or later. Source files use names such as *.recipe.json, *.pack.json and *.composition.json; corresponding .jsonc names are recognized, but the contents must be strict JSON. Use Recued: Set Document Type for another filename.

What you can do

• Author all three source types. Create complete starters and edit standalone or inline recipes, pack manifests and compositions.
• Validate locally. See shared authoring diagnostics in Problems, inspect exact ranges, use supported reviewed Quick Fixes and scan a folder or workspace.
• Navigate your source. Use completion, hover, Outline, F12, references and supported Rename actions for local declarations and inputs.
• Inspect generated artifacts. Preview and explain compiler output or compare generated changes before using a pack or composition.
• Author with AI. Give your existing native VS Code AI provider bundled reference, local declaration discovery and latest-buffer validation tools.
• Work with Kitchen drafts. Optionally browse, open, compare and explicitly save authorized drafts, review revision conflicts and recover uncertain transfers.

Validation checks static source rules. Installing packs, executing recipes and granting server access are separate actions.

Choose your workflow

Use your existing AI setup

Enable Recued Authoring Reference, Recued Workspace Operations and Recued Validate Source in Chat's tool configuration alongside the normal editing tools. Run Recued: Author with AI, choose a source type, review the prompt, select Copy Prompt and Open New Chat, paste it, add your goal and submit.

The agent can read the bundled guide, discover local pack operations, edit the selected file and validate its latest buffer. Recued: Improve with AI works with an existing saved source. Problems also offer Explain Problem with AI and Fix Problem with AI where supported.

Recued: Enable AI Authoring for This Workspace previews optional scoped instructions and a reusable prompt. Existing files are preserved. Your AI provider's setup and native permission controls remain in effect. A Recued MCP connection is not required for this local workflow.

Optional Kitchen connection

1. Visit recued.com, follow Get started to install and start your Recued server, and pair the webclient with the code shown by your server.
2. In the paired webclient, open Contracts → Others → + New contract. Name it, for example, VS Code Kitchen, enable MCP tools and select Create contract.
3. Open that contract's Ops tab, search for Kitchen and enable the four operations below. New contracts grant nothing by default.
4. Open the contract's Connect tab, select Create a key and copy the key while it is shown. Use the full MCP URL in the connection examples on that tab.
5. In a trusted VS Code workspace, run Recued: Set Up MCP Connection and enter that URL and key. HTTPS is required outside localhost. Setup reports how many of the four Kitchen tools are granted; with all four enabled it reports 4 of 4.

Setup also makes the connection available to VS Code's native MCP support. These connected tools are separate from the three local AI authoring tools above. Server grants determine what the key can discover and call; the extension does not enable grants for you.

Use the Kitchen Activity Bar view to find and open work in progress. Send to Kitchen imports new source; Save to Kitchen submits an edited draft. A local file Save is a separate action. Writes follow Recued's approval policy. Conflicts require review, and uncertain transfers can be resumed or their exact stored source recovered. Pending writes are not replayed automatically after restart.

The bundled Kitchen drafts guide covers setup, permissions, comparisons, conflict resolution, recovery and disconnecting. See also Connect to Recued. You can use a self-hosted disposable realm to try the connected workflow.

Documentation and account-free evaluation

Run Recued: Open Documentation to open any bundled guide locally:

• Getting started — installation, your first recipe and pack, filenames, validation and local operation calls.
• Author with AI — provider setup, authoring prompts, Problem actions and workspace instructions.
• Kitchen drafts — optional MCP setup, explicit saves, owner changes and recovery.
• Feature reference — detailed input, schema, navigation and source-review tools.

To evaluate the extension without an account, create and validate a recipe, introduce an invalid version and inspect its Problem, restore the version, then create and validate a pack. Open the bundled guides to confirm offline documentation. These steps require no backend credentials.

Public format references are available in Recipe authoring and Pack authoring. The bundled reference tools match this extension build; online material can describe a newer release. Learn about Recued at recued.com.

Data and permissions

Local editing, validation and documentation stay in VS Code. AI prompts, attached source and tool results are handled by the AI provider you select. Optional MCP requests go to the endpoint you configure. Connection keys are stored in VS Code SecretStorage; pending transfers may retain source in local workspace state for explicit recovery. Keep service secrets in connections and review source before sending, installing or running it.

License

AGPL-3.0-only.