The first bot can't be deleted even after another bot is the Chief of Staff
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 43/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- typescript
- Domain
- backend
Research direction
Read server/store.ts around deleteBot and server/default-bot.ts around defaultBotPatchRefusal and ensureDefaultBot; trace how the default bot marker and its ledger are updated when a bot is deleted. Check the bot deletion and patch route tests, then add coverage for deleting the former default bot after another bot becomes Chief of Staff. Done means the former default bot can be removed while the current Chief remains protected and the helper ledger behaves as intended.
Written by the indexing model from the issue text.
Description
What happened
The bot this place made first — the starter, marked as the helper (defaultBot) — can be hidden from the sidebar, but it can never be deleted, and that does not change once another bot is the Chief of Staff. Delete answers:
dusk bot can't be deleted or archived. To take it off the sidebar, choose Hide in its menu, …
Verified on an isolated fixture (nothing of mine touched):
Dusk is the first bot, marked defaultBot
PATCH Dusk {sidebarHidden:true} 200 <- Hide from sidebar works
PATCH Dusk {hidden:true} 400 same "can't be deleted or archived" sentence
DELETE Dusk 409 same sentence
make Bravo chief 200
(make Charlie chief) 200 Dusk's crown is cleared, as it should be
DELETE Dusk 409 still refused, chief or not
So the crown is not what blocks it. The refusal keys on the marker, not on the role:
server/store.ts:1478—deleteBotthrows for anybot.defaultBot.server/default-bot.ts:29(defaultBotPatchRefusal, used byserver/routes/bot-patch.ts) —hidden: trueis refused for the same bots.server/default-bot.ts:145(ensureDefaultBot) — a place that has had its helper never gets another one made (if (Object.hasOwn(ledger(...), person)) return null), so the marker effectively pins that row for the life of the place.- Nothing in the UI can move the marker:
takeArrivingDefaultBotmoves it only when a move brings another place's helper in.
The Chief's Hide being refused is intended (it is a different guard, bot-patch.ts:447, and I am not asking for it). This is only about the first/former bot.
Why it reads as a bug from here: the first bot is the throwaway starter. People rename it, use it for a while, then set up real bots and move the Chief of Staff; what is left is an ordinary-looking row that refuses Delete and offers only Hide — which keeps the bot, its conversations, its memory, its workspace folder and any routine it owns alive, with no way to remove them.
Steps to reproduce
- New install: the starter bot is the only bot and the Chief of Staff.
- Make another bot the Chief of Staff (the starter's crown is cleared).
- Right-click the starter → Delete: refused with the notice above, whatever the crown says.
- Right-click it → Hide from sidebar: works, and it is the only way out the app offers.
Version
0.2.17
Platform
macOS
Engine
No response
Logs or screenshots
Measured: DELETE defaultBot 409, PATCH {hidden:true} 400, PATCH {sidebarHidden:true} 200, before and
after another bot is the Chief.
What would settle it, in order of what the code already supports:
1. Let the marked bot be deleted once the place has another bot: clear the marker with it, and let the
ledger record that this place's helper is gone (ensureDefaultBot already knows how to adopt an
existing bot instead of creating one, should the person want a helper again).
2. Or offer "Make … my helper" so the marker can move to another bot, after which the old first bot is
an ordinary bot and deletes normally.
3. Whatever the rule, the notice should name the helper as the reason — and stop pointing at a settings
switch that is not in Settings → General (filed separately as #74).
- Dominant language
- TypeScript
- Stars
- 277
- Forks
- 27
- Avg merge
- 2h 47m
- Merged PRs (30d)
- 1
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from DuskBotAI/duskbot
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
Maintainers usually reply within 1 day
-
After uninstalling an own server, the desktop app stays on it and shows Cloudflare's Error 1033 pageOpen
Difficulty 3/5 1-2 days Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
install.sh --tailscale replaces whatever the host already serves on tailnet port 443Possibly taken @viniciusbregoli claimed this today. Open
Difficulty 4/5 3-5 days Newbie friendliness 25/100
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
Maintainers usually reply within 1 day
All issues in DuskBotAI/duskbot
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
vercel-labs/ui#865 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
outline/outline#14638 · 1 comment ·
Maintainers usually reply within 1 day
-
wayfinder:grilling
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
patricktree/cup#484 ·
-
bot:ai-assisted component:platform-js status:untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
midnightntwrk/platform-js#69 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
Maintainers usually reply within 1 day