KinetAios: open-source desktop workbench that hosts ccr as a plugin engine (stream-json UI, resume, parallel routed channels)

[phinn]

Hi Claude Code Router community — I maintain KinetAios, an open-source (GPL-3.0) desktop workbench that manages Claude Code-style CLI agents, and ccr now ships as a built-in plugin engine.

What it is

KinetAios gives every CLI agent a proper home: multi-channel sessions with streaming output, tool-call timelines, cost tracking, and a shared local long-term memory (SQLite FTS5) that persists across conversations. Everything is local-first — nothing leaves your machine.

How ccr fits in

The new claude-code-router plugin engine registers ccr (ccr code -p --output-format stream-json) as a first-class engine via our declarative CLI engine adapter:

• Full stream-json parsing — tokens, tool calls, and costs render in real time, same as native Claude Code
• Session resume via --resume <session_id> — pick conversations back up across app restarts
• Multiple parallel channels can run different routed models (DeepSeek / Kimi / GLM / Qwen...) side-by-side, each with its own context
• The routing config stays in your existing ~/.claude-code-router/config.json — KinetAios doesn't touch it

Why bother

If you route Claude Code through ccr to save tokens, you've probably juggled terminal windows and lost session state. KinetAios gives those routed sessions a durable UI, cross-channel memory, and 30+ built-in tools (shell, files, web fetch) — without changing how you use ccr.

macOS (dmg) and Windows (exe) binaries: https://github.com/phinn/KinetAios/releases/latest

Repo & docs: https://github.com/phinn/KinetAios

Feedback welcome — especially from ccr power users running unusual provider setups. If something doesn't parse right through the adapter, I want to know.