One instrument. One useful task.
Run the task and inspect its output
Step 1: A task receives a seal
Run a shell task or saved Quest.
Still frames · every step is available
“Run the task and inspect its output.”
Run a shell task or saved Quest.
See who does what
Choose the task, workspace and permitted scope.
Run a shell task or saved Quest. Start here: Terminal or Quests → command.
Output and exit status are inspected.
A flourish cannot stand in for command completion.
Copy an example instruction
Illustrative task shared across these lessons. Adapt the scope and file ownership to your project. Try the complete example and inspect its tests →
Add a saved-filter control. Keep the change focused. Inspect the existing filtering behaviour, implement the control, and run the relevant checks. Ask a separate agent to review the diff without editing it. Collect its findings and resolve confirmed issues before proposing a commit.
Before you start
Open the repository workspace. A Quest is a saved task from its `.code-workspace` configuration; Bash Terminal is an interactive shell.
Illustrated explanation · The scene explains the workflow. Follow the guide to perform it in the app.
About this demonstration
Instructions reviewed against product 1.5.119. Authored illustration; no application execution is claimed.