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, the project Explorer stays beside the file preview. Open several files in sequence and each one gets its own tab, without switching between a separate directory page and preview page.

The Explorer follows familiar code-editor conventions:

• Create a file or folder, refresh, or collapse the tree from the toolbar.
• Right-click a folder or empty space to create, upload, paste, or run actions at that location.
• Rename or delete files and folders, and copy their paths. Deletion always asks for confirmation.
• Download files generated by an agent or add them directly to the current message.
• Drag the divider to resize the Explorer. NextClaw remembers the width and only uses an overlay when space is genuinely tight.

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. On a narrow screen, use the Explorer button in the preview header to reveal the tree temporarily and continue in the same preview context after choosing another file.

To use a file in the current message, choose Add to chat from its action menu. In a text file, you can select a passage first and add only that excerpt. Files, folders, and selected text appear as visible references in the composer. See Tasks and sessions for the full workflow.

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: Tasks and sessions, Inspect task results, and Panel Apps.