What Kairos does by itself

The week plan

How Kairos forecasts the week and orders every account's capacity — the forecast, first expired first out, promotion of weeks that would go unused, always borrow, renewals, events that make the plan again, and the 2.0.69 words for when each week is spent.

Every check, Kairos plans the week ahead: how much your sessions will use, hour by hour, and which account serves each hour, so that as little capacity as possible expires unused while the work keeps going. Week ahead draws the plan; Rotation follows it.

The forecast

Kairos learns how much your sessions use at each hour of the day, from your own past days: the same hour on earlier days, the nearest days counting most, weekdays and weekends apart once each has two days of history. It gives a likely amount and a low and a high one, for the next seven days.

The plan counts in sessions: one session is one account's 5-hour window, up to the 5-hour ceiling. A week of a typical plan holds a handful of them. Kairos learns what a session of each account is worth from how its readings rise as your sessions spend; an account not measured yet borrows the typical one.

First expired, first out

Hour by hour, the forecast is served from the capacity that would be lost soonest:

1. Promoted capacity: a week, or expiring API credit, that would otherwise expire unused (see below).
2. Accounts without a weekly limit: an open window soonest reset first. A window not yet started can wait: waiting loses nothing.
3. Weeks, the one that resets (or renews, or ends) soonest first.
4. API keys, billed per token, your last resort: expiring credit first.

Kairos also counts what a switch costs (the sessions' prompt caches, written again), and leaves a remnant to expire rather than stop your sessions on a window that would not last.

Promotion

When the plan would leave part of a week unspent at its reset, Kairos tries spending that week first. It keeps the change when it serves more of the forecast, or as much with less expiring, by more than the switch costs. A promoted week starts as late as it can and still do as well, with one 5-hour window to spare: a week with 58% left needs its last day or so, not the first days of the week.

Always borrow

The plan never holds capacity back for later; it only orders it. Hours the accounts cannot serve are dry spells, and the plan says when the first one comes. Prepaid API money carries over, so only weeks and expiring credit count as "expiring unused".

Ends, renewals and bills

• A use-up-by time ends an account's capacity there; what is left then is lost, so the plan spends it first. See Use up by.
• A subscription's monthly renewal ends its week too: on that day the plan renews, and its limits start again, or lapses, and nothing is left. Either way what the week has not spent by then is lost, so the renewal is that week's deadline when it comes first.
• New in 2.0.70, the renewal day comes from the account's billing page ("Your subscription will auto renew on Dec 6") once Kairos has read it in Billing, in any currency. Until then, and after a subscription that began again since, it is a month on from when the subscription began.
• A bill not paid puts the account first while it has room. See Billing.

When each week is spent

New in 2.0.69, the plan says when it spends each account: the first and last hour the forecast draws on it before what it holds expires. You see it as:

• planned Fri 09:00 (or planned now) on each account's row. See Accounts.
• Next in the plan: in the plan sentence, the weeks rotation passes over now, each with when it is planned and when it resets or renews:

An account the forecast does not spend before its reset shows no "planned" time. "The forecast leaves about N sessions of it unspent at its reset" (or "renewal") appears from half a session up.

Making the plan again

The plan is made again whenever something changes, not only on a timer. These events make the next check plan again, whatever the plan's age: a window reset, an account reaching a ceiling, a switch (by Kairos or by hand), an account added, removed or signed in, a session stopped on a limit, an API key budget recorded, a setting changed, or a request for a new plan.

Every event is recorded, and listed with whether a check has handled it (plan when it re-planned, seen otherwise) or not yet (pending).

The web dashboard lists the recent events under the week plan. See Web dashboard.

Settings

Turn weekly-first off and rotation stops following the plan's order; Week ahead then says so. See Configuration.