KIOKU v0.7.0: completing multi-agent — Gemini and Codex CLI now get automatic session logging

try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 3883168) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } megaphone Posted on Apr 28 KIOKU v0.7.0: completing multi-agent — Gemini and Codex CLI now get automatic session logging #claudecode #ai #mcp #opensource KIOKU (4 Part Series) 1 I brought KIOKU to Claude Desktop — one .mcpb drag, no Node setup 2 KIOKU v0.5.0 + v0.5.1 — unified ingest router + hot cache, shipped same day 3 KIOKU v0.6.0: multi-agent support — same vault across Claude / Codex / OpenCode / Gemini CLI 4 KIOKU v0.7.0: completing multi-agent — Gemini and Codex CLI now get automatic session logging Context I've been building KIOKU — a memory / second-brain OSS for Claude Code, Claude Desktop, and (since v0.6) Codex CLI / OpenCode / Gemini CLI. The v0.6 post introduced "multi-agent support" — but I want to be honest about what that meant in v0.6, and what's actually different in v0.7. In v0.6, I shipped setup-multi-agent.sh to symlink KIOKU's skill directory into each agent's skills location. So /wiki-ingest and friends became callable from Codex and Gemini. But the automatic session logging pipeline — the hooks that capture every conversation and quietly grow session-logs/ in the background — was still Claude Code-only. You could call KIOKU's tools from Gemini, but the second-brain didn't grow on its own there. v0.7.0 (shipped 2026-04-28) closes that gap. The headline: In v0.6 the skills were shared. In v0.7 the memory is shared too. What that took, and what else came along: 🔀 Multi-agent automatic session logging — Gemini CLI and Codex CLI now write to session-logs/ automatically, via a refactor that turns session-logger.mjs from a 591-line monolith into a core + three adapters 📚 Multi-agent MCP install docs — three agents' worth of config snippets, verification commands, and explicit "unverified in delegation environment" banners 🎬 Visualizer α (kioku_generate_viz MCP tool) — first user-callable surface for "see your wiki along a time axis," the alternative to Obsidian's Graph View ✅ verify-multi-agent-e2e.sh — interactive 6-step sanity checker for post-install reassurance Plus a security-implementation pass that takes the formal policy from v0.6 and threads it through the multi-agent boundary. https://github.com/megaphone-tokyo/kioku 1. Hook port: from monolith to core + adapters This is the centerpiece of the release. What was missing in v0.6 setup-multi-agent.sh (v0.6) symlinked skills, not hooks. The hook layer — hooks/session-logger.mjs, 591 lines, monolithic — was written against Claude Code's specific event schema (UserPromptSubmit / Stop / PostToolUse / SessionEnd with their particular stdin/stdout shapes). Other agents have hook systems too, but with different schemas, so the same script wouldn't run there. The honest framing: in v0.6, "multi-agent" was a half-finished narrative. Skills moved; the automatic memory layer didn't. The refactor session-logger.mjs got split into a core + three adapters: hooks/ ├── session-logger.mjs (core: agent-agnostic, processes NormalizedEvent) ├── adapters/ │ ├── claude.mjs (normalizes Claude Code's hook schema) │ ├── gemini.mjs (normalizes Gemini CLI's hook schema) │ └── codex.mjs (normalizes Codex CLI's hook schema) └── _common.mjs (safeMain — exit-0 contract, shared…

This excerpt is published under fair use for community discussion. Read the full article at DEV Community.