Repository navigation
KinetAios: a desktop workbench that hosts Gemini CLI as a parallel channel (stream-json UI, resume, shared memory) #30151
phinn
started this conversation in
Show and tell
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hi Gemini CLI team & community — I maintain KinetAios, an open-source (GPL-3.0) desktop workbench that hosts CLI coding agents in parallel channels, and Gemini CLI now ships as a built-in plugin engine.
What it is
KinetAios gives terminal agents a durable home: multi-channel sessions with streaming output, tool-call timelines, cost/token tracking, and a shared local long-term memory (SQLite FTS5) that persists across conversations and engines. Everything stays on your machine.
How gemini fits in
The new
gemini-cliplugin engine wrapsgemini --output-format stream-jsonthrough a declarative adapter, with a dedicatedjsonl-geminiprotocol parser built from the official event schema (packages/core/src/output/types.ts):init/message(delta streaming) /tool_use/tool_result/resultevents — same treatment as native Claude Code and Codex engines-r <session_id>(session id captured from theinitevent, restored on each turn)--approval-modeexposed as a user setting (default / auto_edit / yolo / plan)Why bother
gemini -pin a terminal gives you one scrollback buffer per run. KinetAios gives those headless sessions a persistent UI: readable tool timelines, per-turn token stats (folded fromresult.stats), session resume after app restarts, and 30+ built-in tools alongside. Your gemini auth and settings stay untouched.macOS (dmg) and Windows (exe): https://github.com/phinn/KinetAios/releases/latest
Repo: https://github.com/phinn/KinetAios
The
jsonl-geminiprotocol preset is generic — any CLI that emits the same event schema plugs in with a one-file manifest. Feedback welcome, especially from anyone running gemini with MCP servers or custom approval setups.All reactions