Run your first agent

This tutorial launches one agent in SASE's demo workspace and shows where to find its result.

Before you start

You need SASE installed and one supported agent CLI installed and authenticated. If you have not set those up, follow Install and set up SASE.

1. Confirm SASE is ready

Check that the command is available:

sase version

SASE prints its version and the version of its core extension.

2. Ask an agent to inspect the demo workspace

The +home project is SASE's managed demo workspace. It is separate from the directory where you run this command, so the agent works in the demo project rather than in the folder open in your shell. SASE prepares the demo project the first time you use it.

This request asks the agent to list the top-level files without changing them. Prompt instructions describe the task but do not enforce what an agent can do, so read the result before asking an agent to edit anything.

sase run "+home list the top-level files in this demo workspace; do not change files"

SASE starts the run and records its prompt and status. The command returns while the agent works, so you can continue using the terminal. The run appears on the Agents tab as soon as SASE records it.

3. Inspect the run

Open SASE's terminal interface:

sase tui

The interface opens on the Agents tab. Find the row whose prompt asks to list the demo workspace's files. The row shows the prompt and current status; select it to read the run details. Wait until the run is done, then read the agent's response in its transcript. The response is the result of this request, and the recorded prompt and status stay with the run after it finishes.

You have launched and inspected a SASE run

You have asked an agent to inspect the demo workspace and found its prompt, status, and result.

Next

• Make and review a change
• Learn about agents and workspaces

_[project]: A sase project is a named unit of work registered with SASE. _[workspace]: A sase workspace is a numbered clone of a project's primary repo, managed by the workspace store and tracked in that project's registry.json. _[agent]: A sase agent is an agent session or a single agent that does not belong to a session. _[prompt]: A prompt is the text SASE hands to a provider to start an agent turn. _[macro]: A macro is a reusable prompt triggered with #name in agent prompts. _[Patch]: A Patch is SASE's local unit of change. _[bead]: A bead is one tracked work item in SASE's git-native issue tracker. _[plan]: A plan is a persisted, approved artifact recording the intent behind agent work. _[TUI]: The TUI is SASE's terminal interface for running agents and reviewing results. _[epic]: An epic is an executable multi-phase plan run with sase bead work. _[gate]: A sase gate is a durable, command-backed request for one user decision, created when work must pause for the user. _[monitor]: A sase monitor is a monitor turn that runs one long command under a detached supervisor, so the command outlives the agent that started it. *[stitch]: A stitch is the lightweight ordered change record inside a Patch's STITCHES: section.