Every client project, with proof.
One Duscode serves all your projects. Each job runs in its own session on its own branch, each project can have its own budget, and every task ends with a record you can hand to the client: what was done, what checked it and what it cost.
Many projects, one app
The sidebar lists every open project with its sessions, and you can work in several at once. Open a client’s repository from GitHub, GitLab or Bitbucket, or an existing folder.
Separate sessions
Each piece of work can run in its own copy of the project on its own branch, so two jobs never edit the same files. Sessions in one project see each other’s claims and wait for each other’s merges.
Budgets you set
Limits per task and per day, which a project can set for itself. Dus finishes the step it is on, stops at the limit and asks.
Proof per task
Each task ends with a Proof of Work: the commands that ran, the checks that passed or failed, the files changed and the cost. Export it as Markdown or a single HTML report.
Pull requests that explain themselves
A pull request opened from Duscode starts with the proof of each task on the branch and the commands to run the checks again.
Routine work on a schedule
Dependency checks, test runs or reviews on a schedule you set, each run in its own session, with its own budget and a record.
Their code stays where it is.
Duscode runs on your computer, next to the code. Client keys and secrets stay sealed in an encrypted vault on your machine and never reach an AI model.
- Privacy mode
- Choose any provider, only the providers you name, or local models only. A refused call is never sent somewhere else instead. Useful when a client sets rules about where code may go.
- Their servers, their CI
- Checks run on your machine, a server or the client’s existing CI. Deploys go to servers the client owns, over SSH, and the first one to a target always waits for an Owner’s Call.
- Their branch rules
- Branch protection always applies. Dus never bypasses a required check or review.
What is ready, and what is coming.
We would rather tell you now than have you find out on a client deadline. Each person runs Duscode on their own machine today, with their own sessions, budgets and Proof of Work. The stages below come from the evidence.
- In betaTeam plan with seats and roles
Invite people to your team by email; each gets a seat, and owners decide who manages the team.
- ComingA 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.
- ComingRooms: 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.
- ComingA view for your clients
Show a client the progress and proof of their project without giving them your workspace.
- ComingCollaborators 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.
More on Teams, and on routine work for each client on Keep improving.