JIKU · OPTIONAL COMPANION · Three-Driver · Sealed memfd · SQLite FTS5

Standalone Desktop Orchestration Companion

Pairs with Koma over sealed memfd IPC and Epoch fencing, uniting zero-output-token visual routing, planner execution, three-tier episodic memory, and MCP tools.

Koma runs 100% standalone without Jiku. Install Jiku only when you want desktop agent orchestration.

Orchestration Highlights

01

Three-Driver Split Pipeline

Decouples Planner, Executor, and Vision-Router drivers so complex desktop workflows run cleanly across isolated background workspaces.

02

Sealed memfd & Epoch Fencing

Consumes zero-copy compositor frames and validates every action against Koma's monotonic Epoch lease, preventing stale-frame misclicks.

03

L0–L2 SQLite FTS5 & MCP

Local three-tier working, episodic, and semantic memory with FTS5 retrieval, skill approval gates, and standard MCP tool exposure.

Workspace Architecture & Visuals

Multi-Workspace Matrix
Multi-Workspace MatrixConcurrent visual inspection across virtual Koma outputs.
Kumiko Orchestration Loop
Kumiko Orchestration LoopStructured planner checkpoints, memory recall, and MCP dispatch.

Arch Linux / AUR

Install `jiku-bin` (R2-backed prebuilt) or `jiku` (`PKGBUILD.jiku.in`) alongside Koma.

x86_64 · aarch64

Prebuilt via AUR

paru -S jiku-bin

Build from source PKGBUILD

paru -S jiku