Skip to content
| Marketplace
Sign in
Visual Studio Code>Other>CakeSlice.aiNew to Visual Studio Code? Get it now.
CakeSlice.ai

CakeSlice.ai

CakeSlice.AI

|
3 installs
| (0) | Free
Sign in to CakeSlice.ai and browse, open and save your cake files from VS Code.
Installation
Launch VS Code Quick Open (Ctrl+P), paste the following command, and press enter.
Copied to clipboard
More Info

CakeSlice.ai for VS Code

Work with your cake files in VS Code, and take the lessons on CakeSlice.ai. This extension only reads from CakeSlice.ai. It has no admin features and nothing is pushed or published from it: your files stay on your computer, and lessons are published from the desktop editor by admins.

  • Local files: *.cakeflow, *.cakedoc and *.cakechart files in your workspace open in the editors below by default and save to disk, in the same format as the desktop app. "New Cake Flow" / "New Cake Doc" (Command Palette, the side bar, or right-click a folder in the Explorer) create one in your working directory. No sign-in is needed.
  • Cake docs open in a rich-text editor (Tiptap, as in the desktop app); cake flows open on the diagram canvas (@glyphlab/diagram-react); a .cakechart opens as an animated preview. Stories open as JSON.
  • Lessons: the side bar lists the lessons on CakeSlice.ai, a chapter at a time. Anyone can see them. Starting one (downloading a chapter) needs a signed-in account, and a members-only chapter also needs a membership.
  • Sign in (only for those) uses the OAuth device flow, as the desktop editor does; the session token is kept in VS Code's SecretStorage.

Docs are read and write including their chart, flow and story blocks (drawn from the copy each holds; delete or move them, and insert new ones from the .cakeflow, .cakechart and .cakestory files in your working folder, with no sign-in) and command blocks. Flow scenarios, history and decisions are kept as they are but not shown. A doc with a block type this editor does not know opens read-only so nothing is lost.

Develop

npm install
npm run compile

Press F5 in VS Code (with this folder open) to launch an Extension Development Host.

The device-flow client id cakeslice-vscode must be listed in DEVICE_CLIENT_IDS in website/lib/auth.ts.

Tests (npm test) cover the lesson code (the archive reader, the cache, the download and unpack flow against a fake site) and need Node 22.18 or newer; they run through the tsx in ../editor. They do not start VS Code.

The webviews are bundled with esbuild from the sibling ../editor workspace (npm run compile), so install that workspace's dependencies first.

The side bar

The CakeSlice.ai side bar lists cake files in two sections, each file with an icon for its kind (flow, doc, chart, story):

  • In this folder: the cake files in your working directory, kept up to date as files come and go. Click one to edit it.
  • Lessons: the site's lessons that come as chapters (see "Lessons by chapter" below). Click a lesson's play button to start it, or a chapter to open it.

Lessons by chapter

A lesson on CakeSlice.ai is a few chapters, and each chapter is one archive (a zip) holding the whole lesson as it stands once that chapter is reached: its doc and diagrams, the tests, and a reference solution. Only admins publish lessons.

  • Start a lesson (the play button on a lesson, or CakeSlice.ai: Start Lesson) opens its first chapter; click any other chapter to move to it. The first time, you choose the lessons folder (the workspace folder, or another one). It is remembered; CakeSlice.ai: Choose Lessons Folder changes it. Nothing is written outside it.
  • Each lesson gets a folder there: <lessons folder>/<lesson>/.lesson/ holds the chapter's files (the lesson, to read), and <lessons folder>/<lesson>/user/ is yours, made empty and never written to again. The chapter's doc and diagrams open for you.
  • Clear the downloads. CakeSlice.ai: Clear Downloaded Lessons (Command Palette, or the … menu of the side bar) deletes the chapters kept on this computer. It does not touch the lesson folders you started or your own code; a chapter you need again is downloaded again, which needs a sign-in.
  • Downloaded once. A chapter is checked against the size and sha256 the site lists and kept under the extension's storage, so it opens again without a connection, and a chapter you have is marked downloaded. With no connection the side bar shows the lessons and chapters listed last time.
  • Starting a lesson (downloading a chapter) needs you to be signed in. Anyone can see the lessons and their chapters; a visitor who tries to start one is asked to sign in. A members-only chapter (shown with a lock) also needs a membership; the sign-in is sent to CakeSlice.ai only.
  • Safe to open. The archive is read before anything is written: only relative paths inside the folder, no encryption, sizes and checksums that match, limits on file count and size. A chapter is unpacked beside .lesson and swapped in, so a failure never leaves it half replaced.
  • Changes in .lesson are noticed: moving to another chapter asks before it replaces files you edited there. Your own user/ folder is never touched.

Publishing to CakeSlice.ai is for admins only, so your own files stay local and are not listed on the site.

The title bar has New Cake Flow, New Cake Doc, Refresh and a Sign In / Sign Out icon, and the last row of the list, highlighted, signs you in or out.

Node content

The icon on a node opens its content in a drawer under the canvas, as in the desktop app: the node's Markdown (with an Edit content button), its Decisions, Code links and Systems design answers. Edits save into the file like any other change. A code link opens the file in VS Code (links are paths inside your working folder). Drag the bar above the drawer to resize it; Esc or ✕ closes it.

Scenario player

The CakeSlice.ai side bar has a Scenario player section below the file list (collapse or expand it like any section; "Play Scenarios" in the Command Palette or the ▶ in a flow's title bar brings it up). It plays the scenarios of the .cakeflow that is in front: pick a scenario, set its inputs, then play, pause, step, seek and change the speed. A ▶ Play button in the top-left of the flow canvas does the same from the diagram: it opens the player and plays the scenario (it becomes ⏸ Pause while playing, and is disabled when the flow has no scenarios). The step on screen is lit on the flow's canvas (Focus fades the rest, Follow moves the view to the current node). It follows you between flows, and updates as you edit the flow or its scenarios.

Scenarios are made and edited in the desktop app, by the chat assistant (see Chat), or by hand in the file; the player runs them.

Chat

In VS Code's chat (agent mode) the assistant can use the cake tools on the .cakeflow, .cakedoc and .cakechart files of your working folder. Open the tools picker to see them (they start with cake_), or just ask:

  • "Add an Orders API and an Orders DB to designs/orders.cakeflow and connect them."
  • "Make a bar chart of p99 latency by endpoint in charts/latency.cakechart."
  • "Write docs/overview.cakedoc describing designs/orders.cakeflow, and embed the flow and the chart."
  • "Write a scenario in designs/orders.cakeflow where a refund over $100 is declined." (it reads the diagram, writes the scenario and checks it against the diagram's nodes and edges before saving).
  • "What does the Orders node do?" (it reads the file and answers).

The tools are the desktop assistant's own (diagram-agent-tools, chart-agent-tools, scenario-core), writing the desktop editor's file formats. Edits go through VS Code's documents, so an open editor updates as the assistant works, and undo works. A .cakechart opens as an animated preview.

Other assistants (Claude Code, Cursor, …)

The same tools run as a stand-alone MCP server over stdio:

{ "mcpServers": { "cakeslice": { "command": "node", "args": ["<this folder>/out/mcp-server.mjs", "--root", "<your project folder>"] } } }

(Use it in one assistant at a time with VS Code's chat, or the tools appear twice.)

  • Contact us
  • Jobs
  • Privacy
  • Manage cookies
  • Terms of use
  • Trademarks
  • Your Privacy Choices
  • Consumer Health Privacy
© 2026 Microsoft