bise for desktop :* · v0 · a proposal for the user

every feature of the terminal app, in a window of its own. same product, same words, same marks. the terminal taught us what matters; the window only adds what a terminal can't do well: real clicks, images inline, a palette, notifications, a place in the menu bar.

one thread per repo. the sidebar lists your repos like chats. picking one opens its thread with main. there's no "new chat": a repo is the thread, forever (compaction keeps it short).
you still talk to main. the agents live in the panel on the right. click one to talk to it directly, esc to come back.
a sans to read, mono where it means something. a sans for everything you read (the thread, the sidebar, settings): Geist (the user's pick); the buttons below swap it to compare. JetBrains Mono for the wordmark, the marks (:* ∿ ✓ ? ψ ✉ $ ƒ), keys, code, paths and commands. in the history, the sans is someone talking to you (you, bise, a report) and the mono is the machine at work (calls, folds, messages between agents): it reads like a log, and you skip it without trying. the same palette, lowercase. "mono everywhere" is there to compare.
quiet by default. calls fold into one row, messages between agents stay small, what needs you waits in the inbox above the composer. ⌘E opens everything.
keys feel like a mac app. every shortcut is a ⌘ key (the user: « utilisons commande pour plus de choses »): no ctrl, no ⌥ to learn. hold ⌘ to see them where they act.
closing the window doesn't stop the work. agents keep running; bise stays in the menu bar and tells you when something needs you.

the reading font:

keys · terminal → desktop

terminal	desktop	why
⏎ · tab · ↑	⏎ send · ⇧⏎ new line · tab queue · ↑ edit the last	unchanged
ctrl+1-9	⌘I the inbox	⌘G is "find next" on a mac. I for inbox
ctrl+o	⌘E open or close everything	⌘O opens a folder in every mac app
ctrl+f / cmd+f	⌘F find · ⌘G older · ⇧⌘G newer	the mac habit, now without the terminal's config
⌥0-9 · ⌥↑↓	⌘0-9 main, agent N · ⌘[ ⌘] previous / next agent	⌘ + number switches views in mac apps; ⌘[ ⌘] is back / forward
ctrl+c	⌘. interrupt · ⌘Q quit (asks: agents stop)	⌘. is the mac "stop"; ⌘W keeps them running
ctrl+r	⌘R or the mic in the composer: record, any key stops	no reload in a desktop app, so ⌘R is free
ctrl+`	⌘J terminal panel	the VS Code panel key; ⌘` already cycles windows on a mac
an item open: ctrl+n / ctrl+p · ctrl+x	⌘] ⌘[ next / previous item (←→ still work) · ⌘⌫ close it	⌘⌫ is "remove" in Finder and Mail
esc	esc back · ⌘W closes the window, the agents keep running	you said yes
ctrl+v	⌘V, or drop a file anywhere	drag and drop is the desktop's gift
hold ctrl	hold ⌘ to see the keys where they act	same idea, the mac modifier
/ commands	/ in the composer, and ⌘K for everything	the palette adds agents and repos
(new)	⌘O add a repo · ⌘⇧[ ⌘⇧] previous / next repo · ⌘, settings · ⌘\ sidebar · ⌥⌘\ agents panel	a window with several repos

what the desktop adds · and what it keeps out

adds	because
a repos sidebar	one thread per repo is the rule; the window can hold them all, with their state (∿ n · ? n · ✓)
notifications, dock badge, menu bar	the whole point is that you look away. bise taps your shoulder only when something lands in your inbox. ✓ done shows in the menu bar and the thread, never as a notification
clicks everywhere	a call opens in place, an agent opens its thread, a file in "changed" opens its diff, a ✓ opens the report
images inline	screenshots you paste and the ones agents make show as images in the thread
the ⌘K palette	a way in for people who don't know the commands yet
keeps out	no tabs, no split view of 4 agents, no "new chat". the thread stays the one place. more windows = more repos, never more threads

questions for you

decided · one window, the repos in a sidebar.
decided · ⌘ for everything: ⌘I inbox, ⌘E open everything, ⌘J terminal, ⌘[ ⌘] agents, ⌘⌫ close an item.
decided · notifications for the inbox only.
decided · closing the window keeps the agents running, in the menu bar.
decided · Geist to read, JetBrains Mono for the marks, keys, code and the machine at work in the history.
open · the stack: the terminal app's Rust core behind a Tauri window would keep one engine for both. main's call; the screens don't depend on it.