Using the workspace

Changes and the editor

Review Dus's edits as change cards and side-by-side diffs, then open and edit files yourself in the built-in editor, with saving, conflict handling and new files.

Change cards

Every edit Dus makes appears in the chat as a card with:

  • the file path. Click it to open the file.
  • new for a file Dus created
  • the number of lines added and removed
  • the changed lines side by side, Original | Updated. Only the changed parts are shown. Long changes show 40 rows and a Show all N lines button.
  • Open in editor

On a narrow screen (a card under 620 px wide), the diff switches to one unified column.

The reason Dus gave for the change is on the approval card and in the journal.

At the end of a task, N files changed in this task lists every file once. Review expands its diff and Hide changes collapses it.

The editor

The editor is a full code editor (Monaco, the editor inside VS Code) in the work pane beside the chat. Each open file or diff is a tab with its own ×.

Open a file by:

  • clicking a path in the chat or a change card
  • choosing a file in Files (the sidebar, or Ctrl/⌘+P)
  • selecting a result in Search (Ctrl/⌘+K, or Search in the sidebar)

Then:

  • Save with Ctrl/⌘+S or the Save button. Unsaved tabs show ●.
  • Format with Shift+Alt+F, and turn on Wrap for long lines. Both are in the status bar.
  • Go back with ← Back or Esc, which returns to the tab you came from.
  • Close a tab with ×. Duscode asks before discarding unsaved changes.

Files over 2 MB don't open in the editor.

When a file changes on disk

If Dus (or anything else) changes a file you have open:

  • a tab without unsaved edits reloads by itself
  • a tab with unsaved edits shows changed on disk while you had unsaved edits, with Compare, Use disk version and Keep mine

Duscode also refuses a save based on an old version of the file, so you never overwrite a change without seeing it. In the same way, Dus can't edit a file that changed while you were reviewing its edit.

New files

In the Files tab, click + New file. Enter a path relative to the project, such as src/utils/date.ts, and click Create.

Diffs against the last commit

To compare a file with the last commit, open Git (the branch button in the top bar, or Ctrl/⌘+Shift+G) and click the file. The dialog closes and the file opens as a read-only, side-by-side diff tab (marked Δ) titled file: HEAD ↔ working. See Git, commits and pull requests.

In VS Code

When the workspace runs inside the VS Code extension, file links and diffs open in VS Code's own editor and diff view instead.

Something missing or wrong? Email support@duscode.com.