Session workspace

The session workspace keeps the current project's files and follow-up work beside the conversation. For local documents, codebases, and generated apps, this is often where the real deliverable lives.

Project files

After you choose a working directory, browse and open its files. New or modified files should appear in that directory or in the output directory you requested.

Previews cover Markdown, code, HTML, common documents, spreadsheets, and presentations. HTML can switch between source and rendered output, while code changes can be reviewed as diffs.

Open files

Open files stay available while you move between the conversation, source, and output. Reopen the real file after the agent changes it.

Subtasks

Split complex work into subtasks with explicit inputs and deliverables. A research task might separate source collection, data cleanup, and summary writing, while the parent session performs the final review.

Session schedules

Scheduled jobs connected to the current work can also appear in the workspace. Recheck their working directory, prompt, and destination whenever the project configuration changes.

Good defaults

• Use the narrowest useful project directory.
• Ask for a change plan before bulk edits.
• Keep source files and write outputs to a separate directory.
• Verify the real artifact, not just the chat summary.

Related: Inspect task results and Panel Apps.