Open source Grok Bot alternative, Bring your own agent and subscription: message Claude Code, Codex, Gemini CLI, Cursor, Copilot and 40+ AI agents as bots on your own computer, from iPhone, Mac, Windows, Linux or terminal. Agent-agnostic and free. Also a Muse and Dots alternative. Built in Rust.
Rust acpagent-client-protocolai-agentsai-assistantclaudeclaude-codecodexcoding-agentscursorgeminigemini-cligrok-bot-alternativeiosiphonelinuxmacosmcpopen-sourcerustself-hosted
feat(desktop): drag computer headings like on the iPhone
leepokai0a8596b04ff2
diff --git a/apps/desktop/src/renderer/views/BotRoster.tsx b/apps/desktop/src/renderer/views/BotRoster.tsxindex 43fb1495..7f72f99c 100644--- a/apps/desktop/src/renderer/views/BotRoster.tsx+++ b/apps/desktop/src/renderer/views/BotRoster.tsx@@ -10,7 +10,7 @@ import type { BotStore } from '../store/bot-store'import type { useComputerRoster } from '../store/computer-roster'import { StoreContext, useApp } from '../store/context'import { BotRow } from './BotRow'-import { ComputerRosterSection } from './ComputerRosterSection'+import { ComputerHeadingLabel, ComputerRosterSection } from './ComputerRosterSection'import { UpdateNeededCard } from './UpdateNeededCard'/** A bot being dragged among its computer's bots, and the order it has made so far. */@@ -19,9 +19,15 @@ interface BotDrag {ids: string[]}-/** The lifted copy of a dragged row: its width, and where in it the pointer holds it. */+/** A computer heading being dragged, and the section order it has made so far. */+interface SectionDrag {+ id: string+ ids: string[]+}++/** The lifted copy of a dragged row or computer heading: its width, and where in it the pointer holds it. */interface Lift {- item: RosterItem+ held: { item: RosterItem } | { store: BotStore }width: numbergrab: Pointat: Point@@ -36,7 +42,6 @@ export function BotRoster({ roster, compact, onContext }: {const app = useApp()const selected = app.selectionconst [hovered, setHovered] = useState<string | null>(null)- const [dragged, setDragged] = useState<string | null>(null)const [botDrag, setBotDragState] = useState<BotDrag | null>(null)// The drag's handlers outlive the render that started it, so they read the latest drag here.const drag = useRef<BotDrag | null>(null)@@ -44,6 +49,13 @@ export function BotRoster({ roster, compact, onContext }: {drag.current = nextsetBotDragState(next)}+ // While a heading is dragged every section folds to it (as on the iPhone) and the order follows the pointer.+ const [sectionDrag, setSectionDragState] = useState<SectionDrag | null>(null)+ const headingDrag = useRef<SectionDrag | null>(null)+ const setSectionDrag = (next: SectionDrag | null) => {+ headingDrag.current = next+ setSectionDragState(next)+ }const [lift, setLift] = useState<Lift | null>(null)const ghost = useRef<HTMLDivElement>(null)const grab = useRef<Point>({ x: 0, y: 0 })@@ -61,16 +73,47 @@ export function BotRoster({ roster, compact, onContext }: {return botDrag.ids.flatMap((id) => byId.get(id) ?? [])}- // The row lifts: a copy follows the pointer from where it was grabbed; the row's slot stays open.- const liftRow = (item: RosterItem, siblings: RosterItem[], from: Point) => {+ // The held element lifts: a copy follows the pointer from where it was grabbed; its slot stays open.+ const startLift = (held: Lift['held'], element: HTMLElement | null, from: Point) => {// A lift during the last one's settle takes over from it.if (settle.current) clearTimeout(settle.current)settle.current = null- const rect = rowRect(item)- setBotDrag({ item, ids: siblings.map((s) => s.bot.id) })+ const rect = element?.getBoundingClientRect()if (!rect) returngrab.current = { x: from.x - rect.left, y: from.y - rect.top }- setLift((last) => ({ item, width: rect.width, grab: grab.current, at: from, seq: (last?.seq ?? 0) + 1 }))+ setLift((last) => ({ held, width: rect.width, grab: grab.current, at: from, seq: (last?.seq ?? 0) + 1 }))+ }++ const liftRow = (item: RosterItem, siblings: RosterItem[], from: Point) => {+ setBotDrag({ item, ids: siblings.map((s) => s.bot.id) })+ startLift({ item }, rowElement(item), from)+ }++ const liftHeading = (store: BotStore, from: Point) => {+ setSectionDrag({ id: store.computer.id, ids: roster.sections.map((s) => s.computer.id) })+ startLift({ store }, headingElement(store.computer.id), from)+ }++ // Passing over another section moves the held one to its place. Folded, the list is short, so+ // it doesn't scroll at the edges like a bot drag.+ const headingOver = (at: Point, under: Element | null) => {+ if (ghost.current) ghost.current.style.translate = ghostTranslate(at, grab.current)+ const current = headingDrag.current+ const section = under?.closest<HTMLElement>('[data-computer-section]')+ const target = section?.dataset.computerSection+ // A section still sliding out of the way would be hit again where it was.+ if (!current || !section || !target || target === current.id || section.getAnimations().length) return+ setSectionDrag({ ...current, ids: moveInOrder(current.ids, current.id, target) })+ }++ const dropHeading = () => {+ const current = headingDrag.current+ if (!current) return endDrag()+ const target = roster.sections[current.ids.indexOf(current.id)]?.computer.id+ if (target && target !== current.id) roster.move(current.id, target)+ const section = headingElement(current.id)?.closest<HTMLElement>('[data-computer-section]')+ for (const animation of section?.getAnimations() ?? []) animation.finish()+ settleInto(headingElement(current.id))}const dragOver = (at: Point, under: Element | null) => {@@ -109,20 +152,25 @@ export function BotRoster({ roster, compact, onContext }: {edgeScroll.current = 0settle.current = nullsetBotDrag(null)+ setSectionDrag(null)setLift(null)}- // The copy settles into the row's new slot (when it's in view), then the row shows again.const drop = () => {const current = drag.currentif (!current) return endDrag()cancelAnimationFrame(edgeScroll.current)if (current.ids.some((id, index) => id !== current.item.store.roster[index]?.id)) current.item.store.reorder(current.ids)const row = rowElement(current.item)- // Measured where the row ends up, not partway through its slide.for (const animation of row?.getAnimations() ?? []) animation.finish()- const slot = row?.getBoundingClientRect()- const view = row?.closest('.roster')?.getBoundingClientRect()+ settleInto(row)+ }++ // The copy settles into the held element's new slot (when it's in view), then the element shows+ // again. Measured where it ends up, so callers finish its slide first.+ const settleInto = (element: HTMLElement | null) => {+ const slot = element?.getBoundingClientRect()+ const view = element?.closest('.roster')?.getBoundingClientRect()const visible = slot && view && slot.bottom > view.top && slot.top < view.bottomif (!slot || !visible || !ghost.current || reduceMotion()) return endDrag()ghost.current.classList.add('settling')@@ -156,15 +204,19 @@ export function BotRoster({ roster, compact, onContext }: {)}- const sections = roster.sections.map(({ computer, store, items }, index) => {+ const sectionOrder = sectionDrag ? sectionDrag.ids.flatMap((id) => roster.sections.find((s) => s.computer.id === id) ?? []) : roster.sections+ const sections = sectionOrder.map(({ computer, store, items }) => {+ const index = roster.sections.findIndex((s) => s.computer.id === computer.id)const notice = store.mismatch && !compact ? <StoreContext.Provider value={store}><UpdateNeededCard /></StoreContext.Provider> : nullconst rows = ordered(computer.id, items).map((item) => row(item, items))if (!roster.grouped) return <div key={computer.id}>{notice}{rows}</div>return (<ComputerRosterSection key={computer.id} store={store} compact={compact}- collapsed={roster.collapsed.includes(computer.id)} toggle={() => roster.toggle(computer.id)}+ collapsed={sectionDrag !== null || roster.collapsed.includes(computer.id)} toggle={() => roster.toggle(computer.id)}previous={roster.sections[index - 1]?.computer.id} next={roster.sections[index + 1]?.computer.id}- dragged={dragged} setDragged={setDragged} move={roster.move} notice={notice}>+ lifted={sectionDrag?.id === computer.id && lift !== null}+ drag={pointerDrag({ start: (from) => liftHeading(store, from), over: headingOver, drop: dropHeading, cancel: endDrag })}+ move={roster.move} notice={notice}>{rows}{!items.length && !store.mismatch && !compact ? <div className="computer-roster-empty">{store.shownConnection.kind === 'online' ? 'No bots yet' : store.connectionLabel}</div> : null}</ComputerRosterSection>@@ -178,12 +230,13 @@ export function BotRoster({ roster, compact, onContext }: {)}-/** The lifted row under the pointer (iOS's lifted cell): a smaller, translucent copy that follows it. */+/** The lifted row or heading under the pointer (iOS's lifted cell): a smaller, translucent copy that follows it. */function RosterGhost({ lift, ghost, compact }: { lift: Lift; ghost: RefObject<HTMLDivElement | null>; compact: boolean }) {+ const card = 'item' in lift.held ? `roster-row ${compact ? 'compact' : ''}` : 'computer-roster-toggle'return createPortal(<div ref={ghost} className="roster-ghost" style={{ width: lift.width, translate: ghostTranslate(lift.at, lift.grab) }}>- <div className={`roster-row roster-ghost-card ${compact ? 'compact' : ''}`} style={{ transformOrigin: `${lift.grab.x}px ${lift.grab.y}px` }}>- <RosterBotRow item={lift.item} compact={compact} />+ <div className={`${card} roster-ghost-card`} style={{ transformOrigin: `${lift.grab.x}px ${lift.grab.y}px` }}>+ {'item' in lift.held ? <RosterBotRow item={lift.held.item} compact={compact} /> : <ComputerHeadingLabel store={lift.held.store} compact={compact} collapsed />}</div></div>,document.body,@@ -247,9 +300,8 @@ function rowElement(item: RosterItem): HTMLElement | null {return document.querySelector<HTMLElement>(`[data-roster-row="${CSS.escape(refKey(item.ref))}"]`)}-/** Where a row is on screen now. */-function rowRect(item: RosterItem): DOMRect | undefined {- return rowElement(item)?.getBoundingClientRect()+function headingElement(computerId: string): HTMLElement | null {+ return document.querySelector<HTMLElement>(`[data-computer-heading="${CSS.escape(computerId)}"]`)}/** The lifted copy's `translate` that keeps the point it was grabbed by under the pointer. */diff --git a/apps/desktop/src/renderer/views/ComputerRosterSection.tsx b/apps/desktop/src/renderer/views/ComputerRosterSection.tsxindex 5466f5da..1ef8de4a 100644--- a/apps/desktop/src/renderer/views/ComputerRosterSection.tsx+++ b/apps/desktop/src/renderer/views/ComputerRosterSection.tsx@@ -1,6 +1,6 @@import { useRef, type ReactNode } from 'react'import { Icon } from '../components/Icon'-import { pointerDrag } from '../lib/pointer-drag'+import type { pointerDrag } from '../lib/pointer-drag'import { useTr } from '../lib/use-language'import { useSlide } from '../lib/slide'import type { BotStore } from '../store/bot-store'@@ -13,38 +13,23 @@ interface Props {collapsed: booleanprevious?: stringnext?: string- dragged: string | null- setDragged: (id: string | null) => void+ /** Its heading's copy is under the pointer: the section keeps its slot empty. */+ lifted: boolean+ drag: ReturnType<typeof pointerDrag>toggle: () => voidmove: (id: string, target: string) => voidnotice: ReactNodechildren: ReactNode}-export function ComputerRosterSection({ store, compact, collapsed, previous, next, dragged, setDragged, toggle, move, notice, children }: Props) {+export function ComputerRosterSection({ store, compact, collapsed, previous, next, lifted, drag, toggle, move, notice, children }: Props) {const section = useRef<HTMLElement>(null)- const tr = useTr()- const dropTarget = useRef<string | null>(null)const id = store.computer.iduseSlide(section)- const drag = pointerDrag({- start: () => {- dropTarget.current = null- setDragged(id)- },- over: (_, under) => {- dropTarget.current = under?.closest<HTMLElement>('[data-computer-section]')?.dataset.computerSection ?? null- },- drop: () => {- if (dropTarget.current && dropTarget.current !== id) move(id, dropTarget.current)- setDragged(null)- },- cancel: () => setDragged(null),- })return (- <section ref={section} className={`computer-roster-section ${dragged === id ? 'dragging' : ''}`} aria-label={store.hostName} data-computer-section={id}>+ <section ref={section} className={`computer-roster-section ${lifted ? 'lifted' : ''}`} aria-label={store.hostName} data-computer-section={id}><div className="computer-roster-heading">- <button className="computer-roster-toggle" aria-expanded={!collapsed}+ <button className="computer-roster-toggle" aria-expanded={!collapsed} data-computer-heading={id}aria-label={`${store.hostName}, ${store.connectionLabel}`} title={`${store.hostName} · ${store.connectionLabel}. Drag to reorder.`}onClick={toggle}{...drag}@@ -55,9 +40,7 @@ export function ComputerRosterSection({ store, compact, collapsed, previous, nexconst target = event.key === 'ArrowUp' ? previous : nextif (target) move(id, target)}}>- <ComputerBadge computer={store.computer} size={20} />- {!compact ? <span className="computer-roster-label"><strong>{store.hostName}</strong><span className={store.shownConnection.kind === 'online' ? '' : 'warning'}>{tr(store.connectionLabel)}</span></span> : null}- <span className={`computer-roster-chevron ${collapsed ? 'collapsed' : ''}`}><Icon name="chevron.down" size={9} /></span>+ <ComputerHeadingLabel store={store} compact={compact} collapsed={collapsed} /></button></div>{notice}@@ -67,3 +50,15 @@ export function ComputerRosterSection({ store, compact, collapsed, previous, nex</section>)}++/** A heading's badge, name, connection and fold chevron; also its lifted copy while dragged. */+export function ComputerHeadingLabel({ store, compact, collapsed }: { store: BotStore; compact: boolean; collapsed: boolean }) {+ const tr = useTr()+ return (+ <>+ <ComputerBadge computer={store.computer} size={20} />+ {!compact ? <span className="computer-roster-label"><strong>{store.hostName}</strong><span className={store.shownConnection.kind === 'online' ? '' : 'warning'}>{tr(store.connectionLabel)}</span></span> : null}+ <span className={`computer-roster-chevron ${collapsed ? 'collapsed' : ''}`}><Icon name="chevron.down" size={9} /></span>+ </>+ )+}diff --git a/apps/desktop/src/renderer/views/computer-roster.css b/apps/desktop/src/renderer/views/computer-roster.cssindex 2c6854b9..fc96b9a3 100644--- a/apps/desktop/src/renderer/views/computer-roster.css+++ b/apps/desktop/src/renderer/views/computer-roster.css@@ -4,8 +4,9 @@transition: opacity var(--layout);}-.computer-roster-section.dragging {- opacity: 0.45;+/* Its heading's lifted copy follows the pointer; the slot stays open. */+.computer-roster-section.lifted {+ opacity: 0;}.computer-roster-heading {@@ -30,6 +31,10 @@.computer-roster-toggle:hover {background: var(--bubble-agent);}+/* Headings the pointer passes over while dragging don't light up. */+.pointer-dragging .computer-roster-toggle:hover {+ background: none;+}.computer-roster-label {display: flex;diff --git a/docs/architecture/desktop-app.md b/docs/architecture/desktop-app.mdindex 90514e29..eb25632a 100644--- a/docs/architecture/desktop-app.md+++ b/docs/architecture/desktop-app.md@@ -40,7 +40,9 @@ same way; the shared desktop behavior covers macOS and Linux.When several computers are selected, the sidebar groups bots by computer, with connectionstatus and update notices in each section. Drag a heading or press Alt+Up/Down on the-heading to reorder sections. Click a heading to fold its bots.+heading to reorder sections: as on the iPhone, a dragged heading lifts (a copy follows the+pointer), every section folds into its heading, the others make room as it passes them, and+they unfold on release (`BotRoster.tsx`). Click a heading to fold its bots.Order and folded sections stay on this device; the iPhone and other computers keepindependent orders even when signed in to the same account. Filtering a computer outdoes not discard its position. One selected computer keeps a flat roster. Bots stay withindiff --git a/docs/design/ui-conventions.md b/docs/design/ui-conventions.mdindex 39876401..9a4fca56 100644--- a/docs/design/ui-conventions.md+++ b/docs/design/ui-conventions.md@@ -10,7 +10,7 @@ iPhone conversation scrolling leaves dragging, deceleration, and bottom rubber-bDo not wrap those toolbar controls in `IconButtonStyle`, hand-sized rounded backgrounds or another glass effect. The account avatar is toolbar content, with the system supplying the enclosing surface. This is the explicit exception to the custom-chrome rule below.-Connecting and reconnecting are background work. `BotStore` gives initial offline reports 1 second to recover and holds drops from online (including relay "computer offline" reports) for 5 seconds. "No access" shows immediately. Automatic read acknowledgements never open an error dialog and visible conversations are acknowledged again after reconnecting. An action taken during a reconnect (back in the foreground, a new network, a drop still inside its grace) waits for the link, up to 20 seconds, instead of failing; while one waits, headers read `Connecting…` and the conversation's connection label shows a spinner. Calls that are safe to repeat (send, stop, approvals, pin, hide, mark as read, delete) are tried again when the link drops under them. Tapping while the header says Offline because the computer can't be reached starts a fresh connection attempt and waits for it, instead of failing until the backoff gets there; a computer the relay reports as off fails at once, since the relay says when it is back. A permission card shows a spinner on the chosen option, dims the others and takes no second answer until the computer has it. The desktop app's `BotStore` (link handling in `apps/desktop/src/renderer/store/bot-sync.ts`) applies the same graces and 20-second wait. The TUI follows the same rule over loopback: a command the host can't be reached for is retried for up to 20 seconds behind its "Reconnecting…" indicator (the `hello` probe that explains an unreachable host still answers at once), and its permission cards spin on the chosen option. The "Something went wrong" dialog is left for a computer that is off, a refused device, the computer's own answers, and reconnects that outlast the wait. Background work (cloud refresh, device registration) logs connection, busy-cloud and stale-token failures instead of showing them. The iOS app disconnects only in `.background`, not `.inactive`. Connection status lives only in headers and their menus. The roster header shows a small summary (`1 connected`, `1/2 connected`, `2 offline`, or `Connecting…`). Its computer menu supports multiple selections, Show only, All computers, reconnect, and management. At least one available computer stays selected; if saved exclusions would hide every computer, the list falls back to all. Filters persist on the device. Bots sort pinned first, then in the order the user dragged them into, then by recency ([bot order](../features/computer-order.md#bot-order)). On iPhone, when more than one computer is shown, each computer gets a light heading (badge, name, connection, and "No bots yet" when empty) above its own bots; with one computer the list stays flat. Tapping a heading folds that computer's bots away (chevron; saved on the device). Long-press a heading to drag the computer with its bots up or down: while it is lifted every computer's bots fold into their headings, they unfold on release, and the order is saved on the device (`AccountStore.move`; VoiceOver: Move up / Move down). A bot moves only among its own computer's bots. The desktop app shows a flat roster. There are no connection banners. The compact desktop rail uses a computer icon for the same menu. Conversation headers show a small connection label; the desktop names the computer in its help text, the phones in the bot details' Settings (Workspace → Computer). Pull-to-refresh remains available on iPhone. Computer setup and access requests live under Manage computers; a phone asks an account computer for access only when the user taps Ask for access, never on its own.+Connecting and reconnecting are background work. `BotStore` gives initial offline reports 1 second to recover and holds drops from online (including relay "computer offline" reports) for 5 seconds. "No access" shows immediately. Automatic read acknowledgements never open an error dialog and visible conversations are acknowledged again after reconnecting. An action taken during a reconnect (back in the foreground, a new network, a drop still inside its grace) waits for the link, up to 20 seconds, instead of failing; while one waits, headers read `Connecting…` and the conversation's connection label shows a spinner. Calls that are safe to repeat (send, stop, approvals, pin, hide, mark as read, delete) are tried again when the link drops under them. Tapping while the header says Offline because the computer can't be reached starts a fresh connection attempt and waits for it, instead of failing until the backoff gets there; a computer the relay reports as off fails at once, since the relay says when it is back. A permission card shows a spinner on the chosen option, dims the others and takes no second answer until the computer has it. The desktop app's `BotStore` (link handling in `apps/desktop/src/renderer/store/bot-sync.ts`) applies the same graces and 20-second wait. The TUI follows the same rule over loopback: a command the host can't be reached for is retried for up to 20 seconds behind its "Reconnecting…" indicator (the `hello` probe that explains an unreachable host still answers at once), and its permission cards spin on the chosen option. The "Something went wrong" dialog is left for a computer that is off, a refused device, the computer's own answers, and reconnects that outlast the wait. Background work (cloud refresh, device registration) logs connection, busy-cloud and stale-token failures instead of showing them. The iOS app disconnects only in `.background`, not `.inactive`. Connection status lives only in headers and their menus. The roster header shows a small summary (`1 connected`, `1/2 connected`, `2 offline`, or `Connecting…`). Its computer menu supports multiple selections, Show only, All computers, reconnect, and management. At least one available computer stays selected; if saved exclusions would hide every computer, the list falls back to all. Filters persist on the device. Bots sort pinned first, then in the order the user dragged them into, then by recency ([bot order](../features/computer-order.md#bot-order)). On iPhone, when more than one computer is shown, each computer gets a light heading (badge, name, connection, and "No bots yet" when empty) above its own bots; with one computer the list stays flat. Tapping a heading folds that computer's bots away (chevron; saved on the device). Long-press a heading to drag the computer with its bots up or down: while it is lifted every computer's bots fold into their headings, they unfold on release, and the order is saved on the device (`AccountStore.move`; VoiceOver: Move up / Move down). A bot moves only among its own computer's bots. The desktop app's sidebar has the same headings, folding and heading drag (a lifted copy follows the pointer, plus Alt+Up/Down). There are no connection banners. The compact desktop rail uses a computer icon for the same menu. Conversation headers show a small connection label; the desktop names the computer in its help text, the phones in the bot details' Settings (Workspace → Computer). Pull-to-refresh remains available on iPhone. Computer setup and access requests live under Manage computers; a phone asks an account computer for access only when the user taps Ask for access, never on its own.Sources: `apps/ios/Views/BotListView.swift`, `AccountSwitcherView.swift`, `apps/ios/Kit/Sources/CodyncUI/Thread/ThreadView.swift`, `Bots/ComputerFilterHeader.swift`, `Store/ComputerSelection.swift`, `Bots/BotRow.swift`; desktop: `apps/desktop/src/renderer/views/ChatWindow.tsx`, `ComputerFilterHeader.tsx`, `BotRow.tsx`.diff --git a/docs/features/computer-order.md b/docs/features/computer-order.mdindex fc899b70..e97776d2 100644--- a/docs/features/computer-order.md+++ b/docs/features/computer-order.md@@ -31,7 +31,8 @@ the order. The computer moves with its bots: while the heading is lifted, everybots fold into their headings (rows kept at no height, so the system's drag keeps its place),and they unfold under their computers when it's dropped. Cancelling a drag leaves the saved order unchanged. A tap folds or expandsthe section; Move up/down accessibility actions are also available. The desktop-app supports heading drags and Alt+Up/Down on macOS, Linux and Windows.+app drags headings the same way (the sections fold while one is lifted, and the others make+room as it passes them) and supports Alt+Up/Down, on macOS, Linux and Windows.The terminal UI connects to one host, so it has no cross-computer ordering.The order never leaves the device: the cloud stores no computer order.diff --git a/web/content/docs/bots.mdx b/web/content/docs/bots.mdxindex 4e058795..cd1b6ff1 100644--- a/web/content/docs/bots.mdx+++ b/web/content/docs/bots.mdx@@ -73,6 +73,7 @@ Each bot keeps a long-term memory across sessions, which you can read on its **M- **Pin:** pinned bots stay at the top of the list. iPhone: touch and hold the bot. Desktop: right-click it. Terminal UI: `p`.- **Order:** drag bots into the order you want. The computer keeps the order, so it's the same on every device. iPhone: touch and hold a bot, then drag it. Desktop: drag it, or select it and press Alt+Up or Alt+Down. Terminal UI: `J` and `K`.+- **Computers:** with more than one computer, each has a heading above its bots. Drag a heading (iPhone: touch and hold it first) to move that computer and its bots up or down; this order stays on the device. Click or tap a heading to fold its bots away.- **Hide:** iPhone: touch and hold the bot, then **Hide from list**. Desktop: right-click it, then **Hide from sidebar**. A hidden bot sends no notifications. To bring it back:- **iPhone:** tap the account button at the top left of the Bots tab, open **Computers & settings**, and tap the eye button (**Unhide**) beside the bot under **Hidden bots**.- **Desktop:** open **Settings → General** and click the eye button (**Unhide**) beside the bot under **Hidden bots**.