Launch is the start, not the end.
Software needs looking after once it is live: checks that run every night, dependencies that age, certificates that expire. This page shows what Dus does for that today, and what is still coming.
What is ready, from the evidence.
Each stage below comes from the same record as Capabilities, so this page and that one always agree.
- In betaThe 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.
- ShippedScheduled jobs
Jobs that run on a schedule, like a nightly check, each in its own session, with the result waiting for you.
- ComingA 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.
- ComingProactive maintenance
Dus keeps dependencies up to date, acts on security advisories and reminds you before certificates and domains expire.
- ComingSelf-improvement
Dus notices what slows him down on your projects and proposes a fix for each, for you to accept.
- ComingThe Work Ledger
Every job in one ledger: done, failed, being redone, and what is still owed, with any day’s history.
Today
The daily brief
One short page each day: what finished, what is waiting for you, what Watch saw, and what runs next. When nothing was recorded, it says so plainly instead of filling the space.
Scheduled jobs
Turn any request into a job that runs on its own: “run the tests and fix anything that fails” every weekday at 09:00, a dependency check every Monday, a review every Friday. Each run is a new session in its own copy of the project, with its own budget, and the result waits for you.
For engineers
A job repeats daily, on weekdays, weekly or every 1 to 168 hours. Each run gets its own git worktree, so it never touches your checkout or another session. The budget per run is $2 by default and at most $50. Runs use Auto mode inside their worktree; Full Auto only when you tick it and the OS sandbox is on. Details: Scheduled jobs.
Coming
None of these is built yet, and none has a date. We list them so you know where Duscode is going, not as something you can use today.
- A backlog and a weekly plan. Dus keeps a list of what your product needs next and proposes a plan for each week, for you to approve.
- Proactive maintenance. Keeping dependencies up to date, acting on security advisories, and reminding 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 place: done, failed, being redone and still owed, with the history of any day.