Repository navigation
Let a person pick Kite Bot: their Bots first, each as a kite - #1837
Open
jerelvelarde wants to merge 2 commits into
Open
jerelvelarde wants to merge 2 commits into
jerelvelarde wants to merge 2 commits into
Conversation
Kite Bot is a skin like OpenDuet, OpenDots and OpenFuse. Its frame keeps OpenBot's sidebar shell and replaces the conversation list with one that leads with Bots: Needs you (the Bots waiting on the person, from the attention read the app already makes), Pinned, every Bot in a steady order with the open Bot's conversations nested under it, and Groups for conversations with several Bots. Home shows the Sky, every Bot's kite with what needs you first, in place of Explore Bots. Each Bot is drawn as a pixel kite in the colour slot its orb uses, with a status pixel beside it and eyes only on contact. Shared pieces this moves: `Skin` gains an optional `home`, `BotLook` gains "kite" (BotOrb draws the kite in its place), and app-sidebar exports `AppSidebarFooter` and `ConversationMenu` so both frames use the same destinations and the same right-click menu. `kitebot` joins SKIN_IDS and the API's skin enum, with the generated client regenerated. Motion across the app: a page change cross-fades the page while the frame around it holds (the router's view transition, typed "page"), wherever the page sits in OpenBot's sidebar inset, which is OpenBot's own frame, Settings, Admin and Kite Bot; the other skins' frames swap pages as before. A theme or skin change cross-fades the whole app, and interactive elements ease their colours over 120ms. The page is named for the transition only while one runs: a permanent view-transition-name makes a stacking context that put the page's fixed overlays under the sidebar. Reduced motion turns all of it off.
jerelvelarde
requested review from
MikeRyanDev,
davidmckayv,
dustywusty,
guidovizoso,
mxmzb,
samjulien and
tylerslaton
as code owners
November 18, 2026 18:30
oasdiff counts a new value in a response enum as breaking, since a client written against the old list could meet one it does not know. A build from before Kite Bot reads a skin id it does not know as `openbot`, as it already does for any unknown skin, so the two lines let exactly this addition through and nothing else.
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The problem
OpenBot's own frame lists conversations. Somebody who works with a handful of Bots tends to think
in Bots ("where is Ledger with the close?"), and the list makes them remember which conversation that
Bot is in. What waits on them is a mark on the Bots link in the footer, so finding out who is waiting
takes a trip to the Bots page.
Moving around is abrupt too. A page change swaps the main area in one frame, and a theme or skin
change repaints the whole app at once, so the app reads as separate pages rather than one place.
The approach
Kite Bot is a skin like the others. It sets a
FrameandbotLook: "kite", and uses one newoptional slot on
Skin,home, to replace Explore Bots under the composer. Every page, route,dialog and footer destination stays OpenBot's own. The footer (
AppSidebarFooter) and aconversation's right-click menu (
ConversationMenu) are now exported fromapp-sidebar, so the twoframes cannot drift apart.
The sidebar leads with Bots. Its sections are:
Bots keep a steady order, pinned first and then by name, because ordering by activity would move rows
under the pointer. It is all derived in
skins/kitebot/roster.tsfrom the three reads the app alreadymakes (Bots, conversations, attention), with no new endpoint and no new polling.
Each Bot is a pixel kite in its orb's colour slot, so it keeps its colour across skins. Its state
is a pixel beside the body: blue while it works, amber while it waits. The face shows only on contact:
Small faces stand by rather than follow the pointer: they blink, and now and then glance one pixel
aside. Reduced motion stills all of it.
The Sky, on home, shows up to eight Bots: waiting first, then working, then the most recently
busy. It holds its height while loading, so the composer does not jump.
Motion across the app. These change OpenBot itself, not only this skin:
page. The page fades outover 90ms and rises 4px into place over 220ms, while the frame holds still. This happens wherever
the page sits in OpenBot's sidebar inset (OpenBot's own frame, Settings, Admin and Kite Bot); the
other skins swap pages as before.
with its own transition keeps it.
The page is named for the transition only while one runs. A permanent name makes the page a stacking
context, and a probe showed that put the page's fixed z-50 overlays under the sidebar.
The cost is worth naming: every page change now runs a view transition. In Chrome, on a dev build,
the new page was ready at about 140ms and settled by about 430ms. Browsers without view transitions,
and anybody who asked for less motion, get the old swap.
What is not covered
kitebot. This PR adds it toSKIN_IDSand theAPI's skin enum and regenerates the client, but carries no server change. Until the back end takes
the new id, picking Kite Bot shows the picker's existing "Couldn't save that skin" message and puts
the previous skin back.
is answered empty. Bot attention is answered with Ivy waiting on two approvals, so Needs you has
something to show. Everything else is this branch against a real back end and database.
Verification
All of this ran on this branch, on
release/1.1at v1.1.0.typecheck,lintandformat:checkare clean.bun test shared api: 467 pass, 9 skip, 0 fail.appsuite: 4256 pass, 322 skip, 0 fail. An earlier run had one failure that did notrepeat, and I did not capture which test it was.
New tests:
kitebot-roster.test.ts: each Bot's state, the steady order, what nests under a Bot, unread, Needsyou, Groups, the Sky's order and line, and which Bot opens out for a path.
kitebot-frame.test.tsx: the frame and home rendered against a fake of the API. It covers eachsection's links, Needs you's tall eyes, the open Bot keeping its eyes while another wakes only under
the pointer, the nested conversations, the footer reaching every destination, and the Sky.
bot-kite.test.tsx: colour slots matching the orbs, contrast in both themes, faces only on contact,a one-pixel glance, eyes on whole screen pixels, a still body at 32px and under, and kites wherever
orbs are drawn.
view-transition.test.ts: a page transition only on a path change, never on first paint or forreduced motion.
avatar-skin.test.tsx(extended): kites where Bots are kites, a group of two kites, and only KiteBot opting in to them.
Checked by hand in headless Chrome against the local stack:
Merge notes
This is based on
release/1.1at v1.1.0, the version it is meant to ship on. The same changeapplies to
mainwithout conflicts. It moves these shared contracts:Skingains an optionalhome.BotLookgains"kite".SKIN_IDSand the skin enum gainkitebot. oasdiff counts a new response enum value as breaking,so
api/accepted-breaking-changes.mdgains a line for each of the two preferences operations. Abuild from before Kite Bot reads the id as
openbot, as it reads any skin it does not know.app-sidebarexportsAppSidebarFooterandConversationMenu.defaultViewTransition, which reaches every page.The
python harness regressionsjob fails onrelease/1.1itself, not on this change. The basebranch leaves the harness's model clients unpinned, and langchain-anthropic 1.7.11, released today,
sends the Anthropic version header as 2023-06-01 where the base branch's test expects the SDK's
default.
mainpinned the clients and widened that check in #1826, which has not reachedrelease/1.1. This PR touches no Python.