Using the workspace

Work pane, Project details and Files

Duscode's layout: the sidebar, the chat, and a work pane that opens on demand for files, diffs, Preview, Terminal and Tests. Plus Project details, Files (Ctrl+P) and Search (Ctrl+K).

The workspace is the sidebar on the left and the chat. Nothing else is on screen until you open something: then a work pane opens beside the chat, so a preview or a diff appears only when you need one.

The sidebar

The rail on the left holds New session, Search, Files, Team, Memory & skills, Scheduled and the sessions of the project chosen in the top bar. You can drag it wider or collapse it with Ctrl/⌘+B. See The sidebar.

The work pane

These open in the work pane, each as a tab:

The pane shows only what's open. Close a tab with its ×. Closing the last tab closes the pane, and the chat gets the full width again.

• Hide it with its close button or Esc (when the cursor isn't in the code or a text box). Its tabs, and any unsaved edits, are kept: the top bar shows a button with how many are open, and Ctrl/⌘+\ brings them back.
• Resize it by dragging its left edge. Double-click the edge to reset it. The chat always keeps at least 320 pixels.
• On a phone the pane covers the screen. ← Back returns to the chat.

Terminal

A real shell in the session's folder, or on your servers over SSH, with tabs, split, find, copy and paste, and Send to Dus. Beside your terminals, Dus's commands lists every command Dus ran in this session with its output and exit code, and Preview log shows the session's dev server. See The terminal.

Tests

Run tests runs every check the project has (see Verification gate) and shows:

• a summary: All N passed or N of M failed
• each check with its exit code, duration and output. Failed checks are opened for you.
• Ask Dus to fix them, which sends the failures to Dus as a new task

The tab shows ✓ or the number of failures. You can't run the checks while Dus is working in that session.

Project details

1. Click the project's name at the left of the top bar.
2. Choose Project details (or click the project you're in, which is ticked).

Each fact about the project and this session is here, and only here:

• Project. The folder, the Branch, the Architecture (click to choose or change it), the Sandbox (see Command sandbox), and Tests (gate) with each check's last status and Run tests.
• AI model. The model answering now, whether it's pinned or routed by task, which providers are connected, and Manage (opens Settings → Models & keys). To change the model, use the model picker in the top bar.
• Deploy. Where the project runs, its address and last deploy, with Deploy again and Rollback, or Put it online before the first deploy. See Deploy your app.
• This session. Cost so far, Estimated savings compared with the top-tier model, Model usage, and Activity: what Dus ran and why it was allowed.

Dus's plan for a multi-step task is in the chat.

Files

Click Files in the sidebar, or press Ctrl/⌘+P, to see the project's file tree for this session. In an isolated session, that's the session's worktree. Files Dus added or modified are marked A or M, and unsaved files ●. Use New file to create a file and the refresh button to reload the tree. The tree skips folders such as .git, node_modules, dist and .worktrees. Pick a file to open it in the work pane.

Search

Press Ctrl/⌘+K, or click Search in the sidebar, to open Search over the chat. It finds file names and text in the current session's files as you type. It's literal and case-insensitive, and needs at least two characters. Results are grouped into Files and Text. Use ↑/↓ to move and Enter to open a file at the matching line.