Your apps, in the Kite bar.

Send JSON from any script on your PC. Kite draws it at the top of your screen, in its own look, and tells you what was clicked.

Your desktop
Built in

Three things Kite puts there, then yours.

One queue for all of it. One thing shows at a time; the rest wait beside it as chips, one click to bring one forward.

Sign-in codes code

Read from mail arriving now and dropped in over whatever you're doing, ready to copy. When a code could be two things, the part you pick is remembered for that sender.

Steps in frontCopySign-in linksKept a day

Meetings meeting

Two minutes before it starts, from your calendar or the invites in your mail. It counts down by itself and Join opens the call.

Steps in frontCountdownJoin

Mail that matters mail

Only when an automation says notify now, and only when Kite isn't in front. Reply opens right there in the Kite bar, files and Undo send included.

Quick replyArchive with UndoOpen
The API

Send JSON, get a bar.

Make a token in Kite → Settings → Kite bar, then call it from anything that speaks HTTP. You never ship UI.

Kite bar API

          
House rules

Your words, Kite's look.

Kite draws every activity from its fields, so a bar from a script feels like one from Kite and nothing can hijack your screen.

What Kite handles For you

The motion and the queuegrows out of the edge, rests as a pill, takes turns
The pointer and the keyboardclick-through except over the shape, never steals focus
Updates in placesame key, same bar: progress, status, countdown
Quiet when you want itone switch makes everything arrive as the pill

What it never does Ever

Run or load what you sendno HTML, no scripts, no pictures from the internet
Answer the internet127.0.0.1 only, and web pages are refused
Cover a reply you're writingarrivals wait until you've sent or closed it
Keep a token you took backpause or remove an integration and it stops at once
Reference

Small API, no surprises.

Point your AI assistant at 127.0.0.1:3100/api/bar: it answers with all of this and the exact JSON Schema.

Values

Text, a code with its own Copy button, a progress bar with a label, or a countdown that ticks by itself.

text · code · progress · countdown

Actions

Up to three buttons, the last one the main one. Open a page, copy some text, or tell your script.

open_url · copy · callback

Priority

Passive arrives as one quiet line, normal drops open for a moment, high goes ahead of whatever is waiting.

passive · normal · high

Events

One server-sent stream per integration: which button was pressed, what was closed, what ran out.

ready · action · dismissed · expired

Limits

60 calls a minute and 20 live activities each. For something busy, update one key instead of sending new ones.

429 says what to do

Errors

A bad request lists every mistake and where it is, so you fix them all in one go.

actions.0.url: Use an https:// address
Questions

Before you ship it.

Do I need Kite running?
Yes. The Kite bar is part of the Kite desktop app, and the API lives on the same computer at 127.0.0.1:3100. Activities live in Kite's memory: they end when they expire, when you close them, or when Kite restarts.
What can I build with it?
Anything that finishes, changes or needs a click: builds and deploys, test runs, timers, a song, a price alert, a long training run. node scripts/bar-demo.mjs <token> runs a pretend deploy and is the template for your own.
Which languages work?
Any that can make an HTTP request: curl, PowerShell, Node with plain fetch, Python's standard library. No SDK, no packages.
Can a web page use it?
No. Requests carrying an Origin header are refused, so a site you visit can't put anything on your screen. Only programs on your computer with a token can.
Does anything I send leave my computer?
No. Kite draws it from the fields and keeps it in memory. Links open in your browser only when you click them.
API v1

Put it where you'll see it.

Free with Kite for Windows. Tell me what you put in yours.