Getting Started

Quickstart

Run one narrow Pulse AI loop from setup to reviewable proof.

The first useful loop

Use the quickstart after Pulse AI is installed, the workspace is initialized, and any required provider keys are configured. The goal is one successful loop: create a narrow item, dispatch it, collect evidence, and review the result.

Pulse AI is not a blank chat window. The board item is the operating contract, and the workspace files are the durable source of truth.

Start from one outcome

Pick a task with a visible result, such as:

  • Update one docs page.
  • Validate one website route.
  • Fix one visible copy or empty-state issue.
  • Create one Knowledge Item from a small research finding.

Write the item so an agent can tell what success means. Include the target surface, the expected proof, and anything that must not be changed.

Dispatch the smallest coherent unit

For a single item, run it directly or place it into a focused Workday. Do not start a full sprint when the useful first proof is one small outcome.

During the run, watch the task and dispatch state. A completed chat response is not enough. You need the board item, changed files, validation output, screenshot, or Knowledge Item that proves the work.

Review before done

When the item reaches review, inspect the evidence:

  • Did the task stay inside scope?
  • Did validation run against the right files or route?
  • Did the output include a Knowledge Item or deliverable when required?
  • Is there any follow-on work that should be tracked instead of hidden?

Only the user moves work to done. Review is the point where you decide whether the proof is strong enough.

What good first proof looks like

A good first Pulse AI run leaves a board item with completion notes, specific validation, and a reviewable artifact trail. For setup-oriented work, useful proof can be a visible product state, a route screenshot, a passing command, or a Knowledge Item stored under .pulse/knowledge.

If the item stalls, inspect the task file and dispatch fields before retrying. If validation fails, fix the root cause and rerun the same check.

Next

← PreviousInstallationNext →API Keys & Providers