Skip to content

Let a person pick Kite Bot: their Bots first, each as a kite - #1837

Open
jerelvelarde wants to merge 2 commits into
CopilotKit:release/1.1from
jerelvelarde:jerel/kitebot-skin-1.1
Open

jerelvelarde wants to merge 2 commits into
CopilotKit:release/1.1from
jerelvelarde:jerel/kitebot-skin-1.1

Conversation

@jerelvelarde

@jerelvelarde jerelvelarde commented Nov 18, 2026 •

Copy link
Copy Markdown
Contributor

Kite Bot: switching skins in Settings, the Sky, the Bots-first sidebar, and a reload that keeps the choice

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 Frame and botLook: "kite", and uses one new
optional 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 a
conversation's right-click menu (ConversationMenu) are now exported from app-sidebar, so the two
frames cannot drift apart.

The sidebar leads with Bots. Its sections are:

  • Needs you: each Bot waiting on the person, with a count and a link to where it waits.
  • Pinned.
  • Bots: every Bot. The one on screen opens out to its conversations, five and then "Show N more".
  • Groups: conversations with several Bots.

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.ts from the three reads the app already
makes (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:

  • At 48px and up, at the top of a conversation, the eyes are always open.
  • From 22px, they open when you point at the Bot or tab to it, and stay open for the Bot you are with.
  • A waiting Bot shows taller eyes.

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 changes: they run through the router's view transition, typed page. The page fades out
    over 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.
  • Theme and skin changes: they cross-fade the whole app.
  • Hover, press and focus: these ease their colours over 120ms, at no specificity, so a component
    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

  • Saving the choice needs the back end to accept kitebot. This PR adds it to SKIN_IDS and the
    API'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.
  • The recording uses two stand-ins. The local stack has no model service, so conversation history
    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.
  • No faces under 22px, so Pinned and Groups rows stay faceless.
  • A group shows two kites even when it has three or more Bots.
  • Sections do not collapse, and "Show N more" resets when you leave that Bot.
  • Not tried in OpenBot Desktop, only in the browser.

Verification

All of this ran on this branch, on release/1.1 at v1.1.0.

  • typecheck, lint and format:check are clean.
  • bun test shared api: 467 pass, 9 skip, 0 fail.
  • The whole app suite: 4256 pass, 322 skip, 0 fail. An earlier run had one failure that did not
    repeat, 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, Needs
    you, 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 each
    section'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 for
    reduced motion.
  • avatar-skin.test.tsx (extended): kites where Bots are kites, a group of two kites, and only Kite
    Bot opting in to them.

Checked by hand in headless Chrome against the local stack:

  • the transition timings;
  • the Sky waking under the pointer;
  • Needs you;
  • light and dark;
  • a phone width, where the sidebar becomes OpenBot's sheet and the Sky shows four tiles.
Sidebar at 2x: the open Bot, one under the pointer, one waiting Dark

Merge notes

This is based on release/1.1 at v1.1.0, the version it is meant to ship on. The same change
applies to main without conflicts. It moves these shared contracts:

  • Skin gains an optional home.
  • BotLook gains "kite".
  • SKIN_IDS and the skin enum gain kitebot. oasdiff counts a new response enum value as breaking,
    so api/accepted-breaking-changes.md gains a line for each of the two preferences operations. A
    build from before Kite Bot reads the id as openbot, as it reads any skin it does not know.
  • app-sidebar exports AppSidebarFooter and ConversationMenu.
  • The router sets defaultViewTransition, which reaches every page.

The python harness regressions job fails on release/1.1 itself, not on this change. The base
branch 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. main pinned the clients and widened that check in #1826, which has not reached
release/1.1. This PR touches no Python.

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.
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

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant