Getting started

The manual. One page per feature, and each page is the whole feature: a build-it-yourself walkthrough first, then every key, every rule, and a complete example — for a person reading top to bottom and for a model fetching one page to author a file.

In order:

  1. Install — the extension, and the one prerequisite that is not obvious.
  2. Agent SDKs — GHCP, the default provider for AI tasks and specs, and what an agent session is given. claude is the other SDK provider; eight more come in over ACP (item 11). Everything that is not an AI task works without any of them.
  3. AI chat — the Chat sidebar and the chat editor tab: one conversation that belongs to no spec and no workflow.
  4. Tasks — tasks.yml, a library of commands. Start here: values, templating and anchors are covered once, on this page, for both formats.
  5. Workflows — one pipeline: stages, tasks in order, an AI draft, a human gate, and one task per item with foreach:.
  6. Variables — every built-in variable on one page: the anchors, params, vars, env and run.context, and the one resolution order.
  7. Spec-driven development — requirements, design, plan, implementation, with a decision between each. The shipped styles, their exact prompts, and writing your own.
  8. Plugins — the last, smallest thing that executes. The eight that ship, and writing your own in plain JavaScript.
  9. package.json scripts — your existing npm scripts, listed beside everything else.
  10. settings.json — the engine’s one configuration file.
  11. Agent Client Protocol — adding an agent this build has no dedicated provider for, like Kiro, as provider: on an ai@1 task.
  12. Workspaces — where “here” is: folder, workspace and profile scopes, and what changes when you open a .code-workspace.
  13. Steering files — your project’s rules for the AI: which ones every chat gets, and which ones the AI loads by topic only when it needs them.
  14. Plugin apps — giving a plugin its own page in the run and spec panels: every file, the whole lw API, and what the page cannot do.
  15. Evaluator — running one eval set on several runtimes and models at once, and comparing what each one scored, how long it took and what it used.

Table of contents


Back to top

Local Workflows is a VS Code extension. Everything it does is declared in a YAML file you own.


- 13-Oct-2026 02:53 PM +0000