- Periodic reviews and health alerts
- Check the goal against recent actions and validation evidence in Claude, Codex, OpenCode, Antigravity, and Cursor. An independent monitor tracks hook use, review delivery, and explicit feedback; a durable inbox and native macOS alerts need no Postfix. Configure supervision and notifications.
- Reminders that wake agents
- A reminder can carry a shell command, instructions for Claude, or a headless wakeup that resumes a named Claude, Codex, Antigravity, Cursor, OpenCode, or Muse session in its working directory. Notifications go where you point them: an HTTP endpoint, a file, or a descriptor. Due items fire when
kin cron, kin remind check, or an installed schedule runs. - Session tags
- Named handles for a piece of work: start, segment, pause, resume, and end with a summary. One active tag per project. Completed ones archive after 60 days without distorting graph health.
- Dream
- A bounded consolidation pass that merges strong duplicates and stages weaker links for review, capped so a busy week never turns into a clique.
- Coordination channels
- Short-lived conversations that several agents, and you, can join: read cursors, standing messages, and advisory locks on shared nodes so everyone sees who holds what.
- Conversation modes
- Research-backed priming artifacts that put a session into a processing mode. Five built in. Make your own from a session and export it without personal data.
- Git-tracked project context
- A
.kin/ directory that ships with the repo: config that inherits from the platform and org above it, a shared merge-friendly graph, and a gitignored local/ for what is yours. - Code maps
- A portable map of the repository that rides in
.kin/ and gives a new session the shape of the code before it opens a file. - Ingest
- Backfill from GitHub, git history, files, saved Codex sessions, and code through ctags, cscope, or tree-sitter.
- Memory of conversations
- Imported conversations are kept in full, with speaker and role, and digested into dated facts and summaries that
kin ask can answer from. - Repository-bound memory
kindex-lite --repo serves one repository's graph and nothing else, for an agent that should not see your personal graph. Run a repository-bound endpoint.- Your graph on other machines
kindex-remote serves graph tools over streamable HTTP behind Cloudflare Access, on infrastructure you run. Nothing that runs a command, reads a host path, or ingests from the host is reachable.- Grounded ask
kin ask answers across connected nodes and cites them, under the same calibrated floor, so it declines rather than invents.