StackMap
Subscribe
Explore / maka
apache

maka

Apache-incubating agent workspace where the append-only run log IS the runtime: desktop, TUI, CLI and Eval are thin clients of one host, and every harness benchmark ships with per-task records.

4,775 453 TypeScript Apache-2.0updated today
View on GitHubDispute this mapping →
Curator's take

Pick Maka if you want a coding-agent harness that treats measurement as the product: every model message, tool call, permission and termination is a RuntimeEvent; the UI, the next prompt and crash recovery are projections of that log; and the project publishes per-task results against other harnesses on the same model with the official verifier. Sessions stay local, you bring the model (API, local, or a gateway). NOT a release yet — no ASF release exists, nightlies are unsigned previews — and NOT the lightest: the discipline is the point. If you want a 100-line agent to read, that's elsewhere on the map.

Mapped by ShipWithAI editors · links verified

Continue your stack

What teams reach for next — and why each earns a place beside maka. Ranked by curator confidence.

alternativealternativealternativealternativegooseshepherddeepseek-harnessmini-swe-agentmaka
pairs wellalternativebuilt withpick a node for the why · open it from the panel
Weekly digest
README.md1 min read

Maka Apache Maka (Incubating)

Apache Maka (Incubating) is a high-performance agent workspace that keeps a complete record of everything it did.

Website · Documentation · Download · 中文文档

GitHub stars License: Apache 2.0 Platforms: macOS, Windows preview, Linux preview

One turn of RuntimeEvents: the model speaks, runs a command, asks permission, you approve, it gets the result, edits a file, the turn ends.

What Maka is

An agent harness exists to finish tasks. We hold it to one measure: how many it completes and at what cost. We publish every run: same model, same official verifier, full per-task record.

  • Measured, not claimed. Maka is benchmarked against other harnesses on the same model with the official verifier, and the per-task results ship with every report in docs/eval/.
  • The log is the runtime. Every model message, tool call, permission decision and termination is an append-only RuntimeEvent. The UI, the next prompt and crash recovery are projections of that log, never the only copy. Old tool output can leave the next prompt without leaving the log.
  • Your machine, your model. Sessions, settings and run records stay local. You bring the model: a cloud API, a local model or a compatible gateway.
  • One Runtime Host. Desktop, the TUI and CLI, and Eval are thin clients of one execution authority; Eval owns only the experiment and its scores.

The website walks through one turn of the log and links the published runs. ARCHITECTURE.md has the system map.

Get Maka

Apache Releases: Maka has not made an Apache release yet. When one exists, the signed source archive will be the official release; packages distributed elsewhere are convenience artifacts. See the downloads page and .github/ASF_SOURCE_RELEASE.md for candidate criteria, signing procedures, and verification steps.

Desktop Nightly: Built daily from main for developers and testers, for macOS on Apple Silicon and Intel, Windows x64 and Linux x64 and arm64; the Windows and Linux builds are unsigned previews. It is not an ASF release and is not intended for production use. Th