Plans and help
FAQ
Answers to common questions about Duscode, covering models and providers, cost, privacy, git, working offline, teams, and how Duscode compares with editing by hand.
Which model does Dus use?
It depends on the task. Duscode routes each task to a fast, standard or frontier model from the providers you have keys for. You see the choice and the reason in the chat, and you can pin one model in the model picker in the top bar. See Routing and costs.
Which provider should I start with?
Anthropic or OpenAI. Either gives you all three tiers with no configuration. With both, Duscode can fall back from one to the other when a provider is overloaded. See Providers and models.
Can I use a local model?
Yes, through Ollama or LM Studio, or any OpenAI-compatible server. Turn the provider on and list your models in the config. Local models must support tool calling. Small local models may struggle with large tasks. See Local models.
Can I use my ChatGPT or Claude subscription instead of an API key?
No. Duscode uses official API keys only, as the providers' terms require for tools like this.
How much does a task cost?
It depends on the model and how much code the task reads. A small fix on a fast model often costs a fraction of a cent, and a large change on a frontier model can cost dollars. Every task shows its cost, and budgets cap each task at $2 and each day at $20 by default.
What does "saved" mean?
The difference between what a task cost and what the same tokens would have cost on the top model. It's an estimate of what routing saved, not a bill.
Does Duscode see my code?
No. Duscode runs on your machine and sends code only to the AI provider you chose, with your key. See Your data and keys.
Does it work offline?
Duscode itself runs locally, but Dus needs to reach your AI provider. With a local model (Ollama or LM Studio) it can work without internet access. Paid plans are checked with a licence that works offline for a few days.
Will Dus change files without asking?
Only what the permission mode allows. In Ask everything asks; in Auto work inside the session goes ahead and anything reaching outside asks. Pushes, deploys, migrations and secrets ask in every mode, sudo and force pushes are never allowed, and any task can be undone.
What happens to my main branch?
Nothing, until you merge. Each new session in a git project works on its own branch in its own worktree. Merge into main runs your checks first, and Duscode never force-pushes. See Sessions and worktrees.
Can I see my app while Dus works on it?
Yes. The Preview in the work pane (Alt+P) runs the session's app inside Duscode and reloads as Dus edits. When Dus tests the app in its browser, you watch each click and check live in the same tab. See Live preview.
Can I run several tasks at once?
Yes. Start more sessions with New session, one per task. Each has its own branch and its own preview port. Dus can also start worker agents for parts of a task.
Does it understand my framework?
Pick the project's architecture blueprint (Next.js, Laravel, Django, NestJS and 20 more) and every agent follows its structure and conventions. Add your own rules in DUSCODE.md.
Can my team use it?
Each developer runs Duscode on their own machine with their own keys. Committed project files (DUSCODE.md, .duscode/config.json, project skills) are shared through git. Team plans with shared policies and central budgets are coming.
Does it work on Windows?
Yes, through WSL 2. Duscode runs inside WSL and you use it from your Windows browser. See Install.
Where do I report a bug or ask for a feature?
Email support@duscode.com. For bugs, include the output of duscode doctor.