The day forgot itself
Something broke. You guess. You restart.
You lived Tuesday. Nothing kept the thread.
Kairos
The day ends. The journal stays.
Every day on your machine leaves a chain of causes. Then the chain vanishes.
Kairos keeps the chain — focus sessions, file touches, agent claims — on this device. Local. Askable. Honest about what it actually saw.
- Stays on your machine
- No screen recording
- Wipeable anytime
The status quo
Your computer has amnesia. Your agents answer to no one.
Agents write without a ledger
They edit files while you are away.
They say they finished. Nobody checked.
Inside the product
What Kairos actually gives you
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.
01
Ask
Ask the journal. Open the receipts in Today.
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.
02
Today
See where the day actually went
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.
03
Focus & rhythm
Understand the shape of your attention
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.
04
What Changed
Name the shifts that felt wrong
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.
05
Dependency Map
Make the causal chain visible
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.
06
Agents
Keep agent claims in the same journal
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.
07
Health
When the machine feels wrong, keep the nearby thread
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.
08
Privacy
Stay in control of what the journal holds
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
Your agents write. Ask keeps them honest.
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.
14:02
Agent · refactored server.cpp
14:31
Agent · updated the docs
15:10
Agent · drafted a fix for the failing tests
Same journal as your focus and files — local, askable, quiet.
After Kairos
Who you become
- 01“What was I doing Tuesday?” is a question Ask can answer.
- 02Agent claims land in the journal — Ask cites them, not vibes.
- 03When the machine feels wrong, the nearby thread is still there.
Closest analogy isn’t a debugger. It’s a filesystem for causality. Read the vision →
When the machine feels wrong, the chain is usually already gone
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
What Kairos refuses
- Cloud your day
- Read your words
- Interrupt for attention
- Demand an account to start
- Overclaim certainty
- Sell the ledger
Your data stays with you, on your device. No cloud. No server. Not on the internet. Nowhere else.
Get started
One command. No account. 21 days free.
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
Continue when you’re ready
Nothing is owed during the trial. If Kairos stays, continue below.
$2/month
billed monthly
How checkout works
- Install Kairos and open Settings → Subscription.
- Copy your Kairos ID, then continue below.
- After checkout, paste the license key into Kairos (Settings, or the paywall if your trial has ended).
Already paid? Recover license.