Getting Started

Installation

Install Pulse AI, reload the editor, and open the workspace Pulse AI should manage.

Before you install

Pulse AI runs as a VS Code-compatible extension inside a project folder. Start with:

  • VS Code or a compatible editor that can install VSIX extensions.
  • A project folder you can write to.
  • Permission to reload the editor window after install or upgrade.
  • Provider accounts or CLI tools for the agent routes you plan to use.

Installation only adds the extension. Your usable Pulse AI setup begins when the extension can see a writable workspace and create its local .pulse files.

Install the extension

Install Pulse AI from the extension listing when available, or install the provided VSIX with the editor extension installer. After installation, reload the editor window so the extension host starts the installed version.

If you are testing a packaged VSIX, verify the installed extension rather than trusting the filename. A stale extension host can keep showing old behavior until reload.

Open the right folder

Open the project folder Pulse AI should manage. Avoid opening a parent folder that contains unrelated projects unless you want Pulse AI to treat that parent as the workspace.

The workspace choice matters because Pulse AI stores board items, Knowledge Items, preferences, dispatch context, and proof artifacts under that folder. If you initialize the wrong folder, later agents and reviewers will read the wrong source of truth.

Launch Pulse AI for the first time

Open the command palette and run Pulse AI: Open App Shell. If the workspace has not been initialized, run the initialize flow before dispatching work.

On first run, expect Pulse AI to introduce the workspace and the first dispatch path. The current onboarding source routes the user toward Lobby, Workday, Today's Items, and the first task dispatch instead of stopping at setup.

Proof that installation worked

A working installation has all of these:

  • Pulse AI command palette entries are available.
  • The app shell opens in the editor.
  • The active folder is writable.
  • The workspace can hold .pulse files.
  • Reloading the editor does not remove the Pulse AI commands.

Do not treat install as proven just because a package command completed. The visible editor runtime and the workspace files need to agree.

Common install blockers

If Pulse AI commands do not appear, confirm the extension is enabled, reload the window, and open a writable project folder. If the UI still does not appear, use the Help Center recovery article instead of repeating the same install step.

Having trouble with setup? See Help Center: I installed Pulse AI but nothing appears and Workspace setup fails or .pulse is missing.

Next

Next →Quickstart