Using the workspace
Ask Dus to change settings
Dus knows every setting, panel and button in Duscode. Ask what something does or where it is, or ask it to change it. Some changes ask you first; keys and payments stay yours.
Dus knows Duscode itself: every setting, panel, mode and button. You don't have to find things yourself. Ask in your own words, in the message box.
What you can ask
- What does this do? "What does Routing do?", "What is Builder mode?"
- Where is it? "Where do I add my OpenAI key?", "Where are my scheduled jobs?"
- What is on now? "Which model are you on, and why?", "What's my daily budget?"
- Change it. "Switch to dark mode", "Open the terminal", "Use Sonnet for this session", "Make routing cheaper".
- Show me. "Show me where notifications are set": Dus opens that place for you.
When Dus changes something, the control lights up for a moment so you see where it lives, and the chat gets one line, such as Changed Mode to Dark (was Light), with Undo and Show.
What Dus does, asks or leaves to you
| Kind of change | What happens | Examples |
|---|---|---|
| How things look, and where you are | Dus just does it, when you asked for it in your message | Dark or light mode, colour theme, text size, opening or closing the Terminal, Browser or side pane, opening a Settings section, the model (Auto or a pinned one), its effort, routing |
| Changes that give Dus more freedom, spend money or touch your privacy | Dus shows you a card first, every time | Full Auto, Auto (allow edits) or Builder, budgets, tasks at once, which providers may see your work, sending feedback, connecting apps, scheduled jobs, archiving or deleting |
| Things only you do | Dus tells you where and opens it for you | Adding or showing API keys and secrets, payments and your plan, signing in or out, deleting your account, answering Dus's own requests |
Going back to less freedom (from Full Auto to Ask, say) never needs a card.
Why Dus only changes what you asked for
Dus only changes a setting when the request comes from your own message. Text in a file, a web page or an app's reply can't switch anything on: if Dus tries to change something you didn't mention, you get a card that says so and recommends Keep it. Words in the conversation can never turn a "card first" change into a "just do it" one.
In the terminal and in VS Code
In VS Code, Duscode's own window works exactly like the app. In the terminal, Dus can tell you about any setting and change the model, its effort, the permission mode and routing; for the rest (colours, panels, saved settings) it tells you where they are in the app.