Product

Your engineering team, in one app.

Dus leads. You decide.

Duscode is an app on your computer with one engineer inside it, called Dus. You describe what you want in plain words. Dus plans the work, writes the code, checks it, and brings you only the decisions that are yours. Every task ends with proof of what ran and what passed.

The Duscode workspace: tasks on the left; in the centre a finished task with a Verified card listing what works now; on the right the plan, the changed files, the checks and the live address.

The real Duscode app, with a sample project.

What it does

Six duties, one team.

The work splits into six duties. Each one ends in something you can check yourself, never just Dus’s word. Some parts are still in beta or coming; each area page below shows which, from the evidence.

Build

Plans the work, writes the code in your project’s own framework and runs your checks.

Ends in: a Proof of Work.

Ship

Commits, opens the pull request, checks it and merges when the checks pass, if you allow merging.

Ends in: a merged change.

Host

Deploys to a server you own over SSH, checks it’s healthy and keeps a one-step rollback. The first deploy is your call.

Ends in: a live address.

Watch

Checks your live system while Duscode is running, opens an incident when something breaks and asks you what to do.

Ends in: a resolved incident.

Maintain

Runs routine jobs on a schedule you set, each with its own budget and a record of every run.

Ends in: a record of each run.

Fix

Finds the cause of a failure, proves it with a test, fixes it and shows you the evidence.

Ends in: a passing test.

Everything Duscode does

Every item in one list, with how each is proven: Capabilities.

The app

What you see.

The chat in the middle, the facts on the right, and everything else one click away. These are real screenshots of the app.

An Owner’s Call in Duscode: YOUR CALL, Take card payments in the shop? Two options side by side with what each costs, means and how to undo it; Take cards is marked DUS RECOMMENDS.

Owner’s Calls: only your decisions reach you.

Money, publishing, real people’s data, legal terms and keys come to you as one card in plain words. Technical calls stay with Dus.

  • What each option costs and means
  • How to undo it
  • Dus’s recommendation, with the reason
A task in Duscode: the request with its attachments, the model and tier Dus chose with a cost estimate, four plan steps completed, and on the right the plan, the changed files and Local CI passing.

A plan before any work.

Dus reads the project and writes a plan, with an estimate of the cost. You see each step as it is reasoned, decided and built.

  • A spending limit per task and per day
  • The model it used, named on every task
  • Any AI provider, or your own keys
Duscode’s Engineer view: the Explorer on the left, a side-by-side diff of a file changed by Dus in the middle, and the chat with the task’s plan on the right.

For people who read the code.

The Engineer view puts the editor beside the chat. Every change opens as a diff you can comment on or undo.

  • Explorer, outline and timeline
  • Inline or side-by-side diffs
  • Terminal and logs in the bottom panel
Watch in Duscode: a live system with its storefront, orders API, database and certificate and their readings, and an incident about a filling disk waiting on the owner’s call.

Watch: it keeps an eye on what it shipped.

Each part of your live system with its reading, every incident with its stage, and the calls that need you.

  • Checks run while Duscode is running on your computer
  • Gaps while it was off are recorded and listed
  • Watching with your computer off coming
Duscode on a phone: the Watch tab with the system’s health and an incident waiting on the owner’s call; a tab bar with Today, Calls, Tasks, Watch and More.

Answer from your phone.

The same app on a small screen, with Today, Calls, Tasks and Watch in a tab bar, so a decision doesn’t have to wait for your desk.

Platform

On your computer, next to your code.

Duscode runs where your code lives. Your keys and secrets stay sealed on your machine, and your code goes only to the AI model answering a task. See Security

Desktop app

For Windows and Linux, with Mac coming. It updates itself, and the app checks each release’s signature before it installs it.

Download

Terminal and browser

Run duscode in a project on macOS, Linux or WSL, and work in your browser.

Install steps

VS Code

Dus in your editor’s side bar, on Pro and above.

The extension

Platform: what is ready.

  • In beta
    Any AI provider, picked per task, or your own key

    Duscode sends each task to a model that can do it at the lowest cost, across the providers you have keys for or on Duscode credits, and names the model it used.

  • Shipped
    Desktop, terminal and VS Code

    Use Duscode as a desktop app on Windows and Linux (Mac coming), as a terminal app you open in your browser, or inside VS Code.

  • In beta
    Signed updates

    Each release is signed with Duscode’s release key, and the app checks the signature before it installs an update, so a changed file is never installed.

  • Shipped
    Duscode Cloud, managed from its admin pages

    Accounts, plans, email, releases and the blog are run from Duscode Cloud’s admin pages, with every change audited, not from code.

  • In beta
    This blog and newsroom

    Posts and release notes are written and approved in Duscode Cloud; Dus drafts them, signed as AI, and a person approves everything except release notes, the weekly digest and capability news.

  • In beta
    Dus writes the news from what ships

    Each week Dus drafts what changed from the work merged and the roadmap, and a news item when a capability moves up here, using only those records. Each post lists its sources; it goes live only if it passes the publish check, and an admin can take it down in one click.

  • Shipped
    Report a problem from inside the app

    Send a problem report from Duscode, with private details removed, and hear back when a release fixes it.

For engineers

Duscode ships with presets for many AI providers, plus local models through Ollama or LM Studio and any OpenAI-compatible endpoint. Routing picks a model per task among the ones you have keys for, starts with the lowest-cost tier likely to succeed and moves up when checks fail. The app is a local server on 127.0.0.1 with a per-launch key; the desktop app, the browser and the VS Code extension are views onto it. Details: Providers.