Other ways to work

Terminal app

Use Duscode in the terminal with duscode chat, including its slash commands, approvals, model pinning and cost summary.

duscode chat runs Dus in your terminal instead of the browser. It's the same engine, with the same routing, tools, gate, budgets and journal.

bash

cd ~/code/my-app
duscode chat            # or: duscode chat ~/code/my-app

It prints the folder, the providers with keys, and a › prompt. Type a task and press Enter.

What you see

◆ model · tier · reason: the model chosen for the task, and why
● tool lines for each action, with ⎿ and its result. File paths are clickable links in terminals that support them.
coloured diffs for edits, and $ command for commands
▲ when Dus switches to a stronger model, ⚠ for a provider fallback, ◇ when the context is compacted
✔ verified: project checks pass, ✗ not verified: project checks still fail, or … couldn't verify in time: <command> was still running after 10 minutes (not a failure: run it yourself)
after each task: the model, the session cost and what was saved compared with the top tier

Approvals

Before an edit or a command, Dus shows what it wants to do and why, then asks:

Allow? [y]es / [n]o / [a]lways for this tool:

y (or just Enter) allows it.
a allows it and every later use of the same tool in this session.
n, or anything else, refuses.

When Dus asks a question, it lists numbered options with the recommended one marked. Type a number, or type your own answer. Enter takes the default.

Slash commands

Command	What it does
`/help`	List the commands
`/model <id>`	Pin a model, for example `/model claude-opus`
`/model auto`	Go back to automatic routing
`/models`	List the available models with their tier and price per million tokens
`/cost`	Session cost, the top-tier equivalent and what was saved, then usage per model
`/mode [ask\|auto\|plan]`	Show or set the permission mode. `/yolo` is short for `/mode auto`.
`/undo`	Put the files back as they were before the last task that changed them
`/team`	The other sessions working in this project: where, on what, and what they claimed and changed
`/exit`, `/quit`	Leave

Keys

Ctrl+C while Dus is working stops the task.
Ctrl+C at the prompt leaves.

On exit, duscode chat prints the cost summary and where the journal is.

Choosing a model at start

Set DUSCODE_MODEL to pin a model for the whole run:

bash

DUSCODE_MODEL=claude-sonnet duscode chat

Differences from the browser workspace

The terminal app works in the folder you start it in. It has no worktree sessions, previews or Git view.
It joins the project's other sessions as Terminal (Sessions working together): it sees them, they see it, its edits respect their claims, and their messages print as ✉ from … lines, never as your words.
It doesn't write the usage history behind Settings → Usage, and its spending isn't counted towards the browser workspace's daily budget.
Its sessions aren't saved for the browser workspace.