getting started / quickstart

Quickstart

A first-session path that teaches Ambient through useful work instead of marketing copy.

Developer Previewllms.txtSource evidence
Progressive Discovery Pi receives compact context first and asks for bounded slices of state only when the task requires them. Progressive Discovery Pi receives compact context first and asks for bounded slices of state only when the task requires them. starts stableasks just enoughacts with evidencerepairs narrowly Bounded context loop small prefixtyped readsvalidator feedback 1 Stable prompt Policy summaryCurrent taskKnown tools 2 Discover ListSearchDescribeRead evidence 3 Act Use toolValidate outputPersist artifact 4 Repair Clear errorNarrow retryKeep trace
Pi receives compact context first and asks for bounded slices of state only when the task requires them.
Product screenshots

Main shell

The main Ambient Desktop shell combines chat, workspace context, navigation, and evidence panels in one local developer workstation.

Ambient Desktop main shell with chat, sidebar, and workspace controls.

First Useful Run

The quickstart gets a user from an empty Desktop session to a real inspected result: ask Ambient to understand a small repo task, let it propose a plan, inspect sources, and produce a visible artifact or Git summary.

Ambient works best when the user keeps evidence visible: plan, source files, tool output, rendered artifact, and final changes.

Suggested Flow

  • Open a workspace and ask for a narrow change or explanation.
  • Review the generated plan before allowing high-impact actions.
  • Use Project Board when the task becomes multi-step or ambiguous.
  • Inspect right-panel evidence such as file previews, browser proof, plugin diagnostics, and Git summary before accepting the result.

Progressive Discovery

Avoid dumping the whole repository into one prompt. Ambient is designed around bounded discovery tools and validation feedback, and the quickstart models that behavior.