What Duscode does today.

Build and ship

• From an idea to a plan to a build

  Describe what you want in your own words. Dus asks only the questions that are yours to answer, writes a plan in plain words, then builds it.

  ✓ Tests read sample ideas with a scripted model and check the questions, the plan and that technical questions never reach the owner. Tested since 13 October 2026.

  For engineers

  At most five owner questions, none technical; the plan and its brief travel with the build, and Builder mode keeps technical questions away from the owner.

  Proven by 2 automated test files, all passing on the code this page was built from.

• Reads, edits and runs commands in your project

  Dus reads your code, makes changes and runs commands in the project folder, and asks before anything you haven’t allowed.

  ✓ Tests run the agent loop with a scripted model against real files and commands, including refused and approved steps. Tested since 12 October 2026.

  For engineers

  Proven by 3 automated test files, all passing on the code this page was built from.

• Builds with tests, and checks every change

  After a change, Dus runs your project’s own checks (tests, type checks, builds) and only calls the work done when they pass. A project with no checks still works.

  ✓ Gate tests run real check commands, including failing, slow and timed-out ones, and check what Dus reports afterwards. Tested since 13 October 2026.

  For engineers

  Proven by 3 automated test files, all passing on the code this page was built from.

• Proof of Work on every task

  Each task ends with a record of the commands that ran, the checks that passed or failed, the files changed and what it cost.

  ✓ Proof tests build the record from what the engine itself ran and refuse records that were tampered with. Tested since 13 October 2026.

  For engineers

  Built from what the engine executed and recorded, never from the model’s words; a tampered record is refused.

  Proven by 3 automated test files, all passing on the code this page was built from.

• Local CI on your machine, your server or your existing CI

  Your checks run as CI on your computer or your server for each branch, with a record of every run, or in the CI you already use. No paid CI service needed.

  ✓ Local CI tests run the queue with real commands and check the records, the status shown and the failure descriptions. Tested since 13 October 2026.

  For engineers

  Proven by 3 automated test files, all passing on the code this page was built from.

Keep improving

• Scheduled jobs

  Jobs that run on a schedule, like a nightly check, each in its own session, with the result waiting for you.

  ✓ Scheduler tests run jobs on a fake clock and check each runs once, in its own session, and reports back. Tested since 12 October 2026.

  For engineers

  Proven by 1 automated test file, all passing on the code this page was built from.

Trust

• Accounts with two-step sign-in

  A Duscode account with a password or emailed links, two-step sign-in, a list of your sessions, and export or erasure of your data.

  ✓ Account tests run against a real Duscode Cloud server with an in-memory database: sign-in, two-step codes, stolen and forged sessions. Tested since 12 October 2026.

  For engineers

  Proven by 2 automated test files, all passing on the code this page was built from.

• Customers kept apart

  One customer can never see, change or remove another customer’s account, team or invites.

  ✓ Attack tests against a real Duscode Cloud server: cross-team removal, invite theft, forged cookies and tokens, admin rights. Tested since 14 October 2026.

  For engineers

  Proven by 2 automated test files, all passing on the code this page was built from.

• Keys and secrets stay sealed on your machine

  Provider keys and project secrets are kept encrypted on your computer. Dus refers to them by name; the value goes only into the command that needs it and is removed from all output.

  ✓ Vault tests check the encryption, that values never reach the model or the logs, and that commands run without your keys in their environment. Tested since 12 October 2026.

  For engineers

  Proven by 3 automated test files, all passing on the code this page was built from.

• Defences against prompt injection

  Instructions hidden in a file or a web page can’t make Dus send your data out, read your keys or get code merged around the checks.

  ✓ The real agent loop runs with a scripted model that obeys every injected instruction; the tests check the engine itself stops each attack. Tested since 14 October 2026.

  For engineers

  Proven by 2 automated test files, all passing on the code this page was built from.

• Asks you only what is yours to decide

  Money, publishing, real people’s data, legal terms and keys come to you as a short card with Dus’s recommendation; technical steps Dus decides himself.

  ✓ Decision tests classify real commands and actions and check which reach the owner, which a reviewer decides and which are blocked. Tested since 13 October 2026.

  For engineers

  Proven by 2 automated test files, all passing on the code this page was built from.

• Spending limits per task and per day

  You set what a task and a day may cost. Dus finishes the step he is on and stops at the limit, and shows the cost in pounds.

  ✓ Budget tests run tasks with scripted costs and check the stop, the wind-down and the figures shown. Tested since 12 October 2026.

  For engineers

  Proven by 3 automated test files, all passing on the code this page was built from.

• Privacy mode: choose who may see your code

  Choose any provider, only the providers you name, or local models only. A refused call is never sent somewhere else instead.

  ✓ Privacy tests make calls under each setting and check that refused providers are never contacted. Tested since 13 October 2026.

  For engineers

  Proven by 1 automated test file, all passing on the code this page was built from.

• Honest claims, only from records

  What Duscode says it did comes from what ran, and what this site says it can do comes from tests that passed. Nothing is called shipped before it is proven.

  ✓ This page is generated from the test results, and every page and post passes the same honest-claims check before it goes out. Tested since 19 October 2026.

  For engineers

  Proven by 2 automated test files, all passing on the code this page was built from.

Platform

• 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.

  ✓ App and extension tests start the local server and the extension and check sign-in to the local app and the connection. Tested since 12 October 2026.

  For engineers

  Proven by 3 automated test files, all passing on the code this page was built from.

• 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.

  ✓ Settings tests change every setting through the admin pages and check it applies live, survives a restart and is audited. Tested since 19 October 2026.

  For engineers

  Proven by 1 automated test file, all passing on the code this page was built from.

• 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.

  ✓ Feedback tests send reports to a test cloud and check the masking, grouping and the “fixed in” notice. Tested since 14 October 2026.

  For engineers

  Proven by 2 automated test files, all passing on the code this page was built from.

Build and ship

• Verified merges

  Dus opens a pull request for finished work and merges it only when the required checks passed on that exact commit, if you allow merging.

  ✓ Ship tests use a fake Git host to check merging, required checks, the merge queue and that nothing merges on an older commit’s result. Tested since 16 October 2026.

  For engineers

  Proven by 3 automated test files, all passing on the code this page was built from.

• Lead mode: specialist helpers on larger work

  For a larger job, Dus plans separate tracks and gives each to a specialist helper (security, quality, operations and others) on its own branch, reviews each one against its evidence and merges them in order.

  ✓ Lead mode tests drive whole plans with scripted models: specialist roles, scope limits, reviews, failures and recovery after a restart. Tested since 13 October 2026.

  For engineers

  Proven by 4 automated test files, all passing on the code this page was built from.

• Start work from GitHub, Linear or Jira issues

  Pick an issue from GitHub, Linear or Jira and it becomes a new piece of work in its own session. Your tracker’s token never reaches the AI model.

  ✓ Integration tests use fake trackers: the issue becomes the first message of a new session and tokens never appear in events or saved sessions. Tested since 13 October 2026.

  For engineers

  Proven by 2 automated test files, all passing on the code this page was built from.

Host and run

• Deploy to your servers, with health checks and rollback

  Dus deploys to servers you connect over SSH or to the hosting platform you use, checks the app is healthy afterwards, rolls back if not, and asks you before the first deploy to production.

  ✓ Deploy tests run the deploy steps against fake servers: health checks, cancelling, rollback and the approval for production. Tested since 12 October 2026.

  For engineers

  Proven by 3 automated test files, all passing on the code this page was built from.

• Watch: incidents, standing orders and Owner’s Calls

  Watch checks your live system while Duscode is running, notices problems, fixes what your standing orders allow, verifies the recovery independently, and brings anything else to you as an Owner’s Call.

  ✓ Watch tests run checks and incidents with fake probes: detection, a restart under a standing order, an independent re-check, and escalation when a fix fails. Tested since 18 October 2026.

  For engineers

  Proven by 2 automated test files, all passing on the code this page was built from.

• Alerts by email, Slack and Teams

  Hear when work finishes, needs you or something breaks: in the app, by email, or in Slack or Microsoft Teams.

  ✓ Notification tests send through fake webhooks and a test cloud’s mail, and check messages carry only what they should. Tested since 13 October 2026.

  For engineers

  Proven by 2 automated test files, all passing on the code this page was built from.

Keep improving

• The daily brief

  One short page each day: what finished, what is waiting for you, what Watch saw, and what runs next. It says plainly when nothing was recorded.

  ✓ Brief tests build it from recorded sessions, scheduled runs and Watch incidents, and check it never says “all clear” without records. Tested since 18 October 2026.

  For engineers

  Proven by 2 automated test files, all passing on the code this page was built from.

Teams

• Team plan with seats and roles

  Invite people to your team by email; each gets a seat, and owners decide who manages the team.

  ✓ Team tests run against a real Duscode Cloud server: invites, seats in join order, roles, and that one team can never reach another’s. Tested since 12 October 2026.

  For engineers

  Proven by 2 automated test files, all passing on the code this page was built from.

Trust

• Billing that can’t go below cost

  No plan, top-up or task can cost Duscode more than you pay, so prices stay sustainable. Included usage is shown in pounds, with a warning before you run out.

  ✓ The margin proof checks every plan and pack against the most expensive model, card fees and a pessimistic exchange rate. Tested since 13 October 2026.

  For engineers

  Proven by 2 automated test files, all passing on the code this page was built from.

• Commands run in a sandbox

  Where the system supports it, commands run with access limited to the project and the network hosts it needs.

  ✓ Sandbox tests try to escape the project folder, reach the network and read secrets, and check each attempt is refused. Tested since 12 October 2026.

  For engineers

  Proven by 3 automated test files, all passing on the code this page was built from.

• Secure sign-in in the apps it builds

  When an app has sign-in, Dus checks it against a published security standard (OWASP ASVS) and runs attack tests on it, and reports each control as proven or not.

  ✓ Identity tests run the attack pack against sample apps and check each control’s result. Tested since 18 October 2026.

  For engineers

  Proven by 1 automated test file, all passing on the code this page was built from.

• A UK company, under UK GDPR

  Duscode is made by Yiontech Ltd in Huddersfield. Export or erase your account data yourself; the legal pages are drafts until a solicitor has reviewed them.

  ✓ Account tests export and erase an account’s data and check nothing of it is left. Tested since 12 October 2026.

  For engineers

  Proven by 2 automated test files, all passing on the code this page was built from.

Platform

• 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.

  Routing tests check the choice for each kind of work, the cost limits and what happens when a provider is unavailable.

  Proof not current: its tests haven’t passed on the latest code yet, so it isn’t listed as shipped.

  For engineers

  Proven by 3 automated test files, not all passing on the latest code yet.

• 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.

  ✓ Release tests publish signed releases to a test cloud and check that an unsigned or changed one is refused. Tested since 19 October 2026.

  For engineers

  Proven by 2 automated test files, all passing on the code this page was built from.

• 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.

  ✓ CMS tests check every state, permissions, sanitising, attacks in every field, feeds and the publish check. Tested since 19 October 2026.

  For engineers

  Proven by 2 automated test files, all passing on the code this page was built from.

• 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.

  ✓ Autopilot tests run weeks on a fake clock with fake records: each kind of post, the publish check stopping overclaims, nothing published with its switch off, and nothing written twice. Tested since 19 October 2026.

  For engineers

  Proven by 1 automated test file, all passing on the code this page was built from.

Build and ship

• Live agent cards: named AI teammates

  Each AI helper at work shows as a live card with its name and role, always labelled as AI.

• One-click job catalogue and job profiles

  Start common jobs in one click, each with a job profile that sets exactly what that job may touch.

• Bring your projects from other coding agents

  Move a project you started with another coding agent into Duscode, with its instructions and history.

Host and run

• Hosting recommendations and set-up

  Dus recommends where to host your software (a VPS, a large cloud, a hosting platform or shared hosting) and sets it up with you.

• Buy and connect domains without breaking email

  Buy a domain and point it at your app hands-free, keeping your email records working. Spending and DNS changes stay your decision.

• Phone alerts

  An urgent problem rings or texts your phone.

• The always-on runner on your server

  A small Duscode runner on your own server keeps working and watching while your computer is switched off.

• Duscode hosts your software for you

  Duscode runs the software it builds on servers it manages, so you don’t need your own.

Keep improving

• A continuous backlog with a weekly plan

  Dus keeps a backlog of what your product needs next and proposes a plan for each week, for you to approve.

• Proactive maintenance

  Dus keeps dependencies up to date, acts on security advisories and reminds you before certificates and domains expire.

• Self-improvement

  Dus notices what slows him down on your projects and proposes a fix for each, for you to accept.

• The Work Ledger

  Every job in one ledger: done, failed, being redone, and what is still owed, with any day’s history.

Teams

• A shared team workspace across machines

  See each other’s work, decisions and budgets in one place, from any computer, with shared budgets and permissions per role.

• Rooms: people and AI specialists together

  A room where your people and AI specialists work a problem together: raise a hand, wrap up into decisions with credit to who made them, and two approval gates before anything ships.

• A view for your clients

  Show a client the progress and proof of their project without giving them your workspace.

• Collaborators abroad, with UK data-transfer agreements

  Work with collaborators outside the UK, with the UK International Data Transfer Agreement (IDTA) built into how access is given.