Kairos
Kairos
Kairos keeps the chain — focus sessions, file touches, agent claims — on this device. Local. Askable. Honest about what it actually saw.
The status quo
Something broke. You guess. You restart.
You lived Tuesday. Nothing kept the thread.
They edit files while you are away.
They say they finished. Nobody checked.
What Kairos is
Focus sessions. File touches. Agent claims. One timeline. Every entry is what the machine observed — not a summary, not a screen recording, not a cloud sync.
Try Ask (demonstration — not your machine)
Ask what did I work on after lunch?
Matched 3 journal moments in that window
You were mainly in Editor (52m), then edited brief.md, then an agent logged a draft claim.
Inside the product
These are not decorations around a journal. Each one changes how you answer a question you already ask yourself — after the day, after a hang, after an agent run.
Ask
Ask answers in plain language with evidence you can open in Today. Search finds sessions and files when you already know the word. Answers carry a reason — matched moments, compared windows — and refuse to invent a story the journal did not earn.
When you use it, questions like “what was I switching between?” or “what did the agent claim?” get answers with receipts, not vibes.
Today
Today turns foreground app activity into a private timeline — List for the diary, Swimlane for parallel lanes so overlaps and context switches become visible at a glance. Time Machine lets you scrub to a clock time and reconstruct what was active around that moment.
When you use it, “where did Tuesday go?” stops being a shrug and becomes a place you can open.
Focus & rhythm
Focus Flow separates deep stretches from fragmented ones, counts switches, and names your longest block. Energy Curve shows when focus tends to peak across recent days. Week view zooms out so one noisy afternoon doesn’t rewrite the story of the week.
When you use it, “I worked for hours” gets a structure — deep vs broken, morning vs afternoon — without inventing productivity theater.
What Changed
What Changed surfaces meaningful CPU and memory movements — which process rose or dropped, by how much — when the machine feels different and you need a named culprit instead of a vibe.
When you use it, “something feels heavy” becomes a short list of what actually moved, not a restart ritual.
Dependency Map
Dependency Map reveals process and activity chains — what spawned what, what sits near what — so the graph under the day is not only stored, but readable. It is the substrate made legible, not a pretty diagram for its own sake.
When you use it, you stop reconstructing “what depended on what” from memory under pressure and start consulting the map.
Agents
Agents can log what they say they did into Kairos — next to the focus and file activity the machine already saw. Quiet entries, not a scoreboard. Ask what happened while you were gone and open the thread in Today.
When you use it, “the agent said it finished” becomes something you can find in the journal — not a trust exercise.
Health
Health keeps vitals observed live, recent hangs and crashes, repeated problems, and pressure signals — then lets you ask about an incident instead of guessing. It never invents hours of CPU history it did not store.
When you use it, a freeze or hang stops ending only in a reboot — you still have the nearby thread.
Privacy
Exclude apps, tune sensitivity, run a personal-data check on what is stored, export what you need, wipe everything when you want. No account to start. No screen recording. No cloud of your day.
When you use it, the journal stays yours — inspectable, bounded, and erasable — which is how trust is earned.
Built for the agent era
Every previous layer of the personal computer assumed actions had human authors. AI agents break that assumption.
Kairos gives agents a place to log claims next to what the machine observed. Ask “what did the agent do while I was gone?” and open the same timeline you already use for your own day — quiet entries, not a Corroborated/Disputed scoreboard.
Same journal as your focus and files — local, askable, quiet.
After Kairos
Closest analogy isn’t a debugger. It’s a filesystem for causality. Read the vision →
Kairos still has the nearby thread — what you were in, what hung, what spiked. Vitals are observed live. It never invents hours of CPU history it did not store.
Trust through constraint
Your data stays with you, on your device. No cloud. No server. Not on the internet. Nowhere else.
Get started
Then a small monthly contribution if it earns a place in your day. Wipeable anytime.
Prefer to check the bits yourself? Verify a download — Ed25519-signed releases, public key and steps on one page.
After the trial
Nothing is owed during the trial. If Kairos stays, continue below.
$2/month
billed monthly