Processes
For code, data, and file work, your UFO uses an isolated computer attached to the conversation. It can read and write files, install project dependencies, run tests, and start local services.
Commands
Section titled “Commands”Your UFO runs commands in the conversation workspace. Command output is evidence, but a successful command does not prove the user-facing result.
Ask for the focused checks that match the work:
Run the unit test for the changed module, build the web application, and inspect the page in a browser at desktop and phone widths.
Local services
Section titled “Local services”Your UFO can start a local web server to inspect an application. A local address is not a result you can open. Ask for a hosted site when other people need access.
Files and persistence
Section titled “Files and persistence”The workspace belongs to the conversation. Continue in that conversation when later work needs its files and state. Share important output in the conversation.
Do not use the work session as production hosting, permanent storage, or a system of record. A deployed service, shared file, connected system, or hosted site must hold the final result.