All 75 Dependencies
Every package Apache Maka depends on, ranked by repo health score.
Apache Maka (Incubating) is a desktop, TUI, and CLI agent workspace built around a single idea: the log is the runtime. Every model message, tool call, permission decision, and termination fact is written as an append-only RuntimeEvent, and everything else in the product — the chat UI, the next prompt sent to the model, crash recovery, session resumption — is a projection of that log rather than a second copy of the truth. That makes a Maka session auditable and recoverable in a way ad-hoc agent scripts are not: you can inspect exactly what happened in a run after the fact, and a crashed session can be reconstructed from its event history.
The project ships three thin clients over one execution authority, the Runtime Host: an Electron desktop app, a terminal UI, and a non-interactive CLI (`maka run`). All three go through the same SessionManager and AgentRun machinery, so a task started in one surface behaves identically in another, and a State Root has exactly one Runtime Host as its write authority. On top of single-agent runs, Maka has an Agent Graph control plane for multi-agent orchestration — `maka run --graph` schedules dependent child sessions, each operating in an isolated Git worktree, and reconciles their output back through the same event log.
A separate `@maka/eval` package turns the same Runtime Host into a benchmarking substrate: experiments expand into cells (task × repetition × subject), each cell runs as one or more immutable attempts, and results are scored with a declared verifier rather than an operator's preferred outcome. The project publishes its own harness benchmarked against competitors on the same model with the same verifier, with per-task results checked into `docs/eval/`.
Maka is Apache-2.0 licensed and openly building toward its first ASF release; nightly desktop builds are available for macOS, Windows, and Linux today. It does not bundle a model account — you bring your own API key, local model, or supported provider connection, and all session, settings, and run data stay local to your machine (SQLite plus a local plaintext credential file, never sent to a Maka-operated server).
