Using the workspace
Notifications
The bell in the top bar holds what needs you and what happened while you were elsewhere. Open any item, take its next step from the list, and tidy it with Clear and Undo.
The bell in the top bar is Duscode's list of notifications. It holds two kinds of thing:
- What needs you: Dus is waiting for your approval or your answer, a task stopped at its budget, or a scheduled job is waiting for you.
- What happened while you were looking elsewhere: a task finished, its checks failed, a deploy ended, a restart interrupted a task.
The number on the bell counts what you haven't read. When something needs you, the number turns amber and counts only those items, so you can see at a glance that Dus is waiting.
Opening an item
Click an item to go straight to its session, at the task it is about. It opens in the same page and marks the item read.
Each item says what happened, which session, which project and when. If the same thing happened several times in one session (for example the same task finished three times), it shows once with ×3. Click Show all 3 to see each one.
Taking the next step
Many items offer what to do next, right in the list:
| Item | Next step |
|---|---|
| Session needs you | Open the card: opens the session at the approval or question. |
| Stopped at its budget | Raise budget: add £1, £3 or £5 to that task's budget. Then open the session and say "carry on". |
| Checks failed / Not done | Fix it: Duscode asks first, then starts a task in that session to find out why and fix it. Open just takes you there. |
| Interrupted by a restart | Continue: picks the task up where it stopped. |
Items that need you leave the Needs you list by themselves once you answer them, wherever you answered.
Filters
At the top of the list:
- Needs you: only what is waiting for you. The bell opens here whenever something is waiting.
- Unread: what you haven't read yet.
- All: everything, with what needs you always at the top.
Read, unread and dismiss
Hover an item (on a phone, the buttons are always there) to:
- Mark read or Mark unread (the dot shows unread items).
- Dismiss it with ×.
Mark all read is at the top of the list. Clear read and Clear all are at the bottom. Clearing never removes what still needs you. After a clear or a dismiss, Undo brings the items back for a few seconds.
Opening the bell doesn't mark everything read: you decide what is read.
Keyboard
| Keys | Action |
|---|---|
| ↑ / ↓ | Move between items |
| Home / End | First or last item |
| Enter | Open the item |
| Delete | Dismiss the item |
| Esc | Close the list |
Housekeeping
- Read items older than 30 days are removed automatically.
- The list is kept by Duscode on your computer, so it is the same in every window and tab, and survives a restart.
- Notifications carry only the project, the session's title and what happened: never code, output or secrets.
Asking Dus
You can ask Dus to clear my notifications, mark them all read or show what needs me. It only changes the notification list; anything that still needs you stays until you answer it.
Where else notifications go
Desktop notifications, Slack and Teams are set up in Integrations, and quiet hours in Settings. Those choices decide what leaves Duscode; the bell always has everything.