Morning brief
Review the day’s schedule and selected sources, then produce a concise brief. Start manually; enable a routine only after reviewing the exact read tools it may use.
Daily work, without a blank check
Start read-first.
Earn automation.
The first routines should create useful drafts and briefings while staying in an explicit, reviewed scope. These are practical starting points, not opaque agents.
Curated starting points
Three workflows for building trust through use.
Begin with local notes, calendar files, weather, web reading, or optional search. Google Calendar is an opt-in connector and begins read-only with a disposable test account.
Meeting prep
Gather a focused context packet before a meeting: upcoming event details, relevant notes, and a draft agenda. Any note creation stays a proposal until approved.
Research brief
Turn a research question into a bounded source review, then keep a Markdown draft in your local workspace. Inspect the trace and source outputs before sharing.
ROUTINES STAY SCOPED
Before enabling a routine
A schedule is not permission.
Kerna asks you to inspect a routine’s allowed tools first. It refuses to enable routines without a reviewed allowlist, and approval-required actions remain blocked in the daemon.
Learn the controls✓
Routine preflight
Before it runs
- Tool allowlist
- reviewed
- Policy
- read-only
- Schedule
- paused
- Budget
- bounded
✓ enable only after explicit review
More connectors are not implied
One governed connector is better than ten invisible ones.
Hosted mail, collaboration, and broad unattended writes are intentionally outside the first cohort. See exactly what is ready before you connect it.
See available installs