Plays4. PlaysWhat you can do nowTo doDoneDismissedDeadlinesSince you lookedChecking Plays…Plays could not be checked. This does not mean there is nothing to do.Plays are held while the actionability and safety checks are measured.Personal Plays are held until the measured rollout checks pass.Deadline reminders are held until the measured rollout checks pass.Sign in to see Plays for your saved tools.Personal Plays and Deadlines are included with Practitioner, Researcher and Business.Sign inSee plansRetrySave a tool in Your stack to see Plays for it.We have not checked every saved tool yet. There is no all-clear to report.No new action was found in the checked release sources. Checked as ofNo published Plays for this tool in the last 90 days. This is not an all-clear for the version you run.No Plays in this view.No dated Plays for your saved tools.Why it mattersDo thisBefore you startEstimated effortEffort has not been measured.Read the sourceSource evidenceAct before it breaksNot for meRemind me next weekHidden from To do until next week.That change was not saved. Try again.Keep my Play answers in my accountOptional: save Done, Not for me and reminders privately in your account. Your tools are matched in this browser. No answers are sent until you opt in.Erase my Play answersYour Play answers and private calendar link have been erased.Create a private calendar linkReplace calendar linkRevoke calendar linkAnyone with this link can read generic deadline events. It contains no tool names, versions or answers. Revoke it any time.Private calendar feedWithin 30 daysWithin 7 daysPast the published dateMore than 30 days awayAct byNo earlier visit saved for this tool.breakingtotal Plays since your last reviewReview this toolMark this tool reviewedReview dates stay in this browser. Opening this list does not mark a tool reviewed.Category moves this monthThere is not enough documented history to call a category move this month.Category history is unavailable. No monthly comparison can be made.Category moves are held until the measured rollout checks pass.The documented monthly history shows no category move.What we got wrongThere are too few reviewed Plays to report a correction rate.Play corrections have not been measured for this month.Plays reviewedcorrectedPublished in the last 90 days. Breaking changes come first.Saved tools are matched in this browser; your versions are not sent.Your Plays{count} PlaysWhat you can do with the tools you runRelease sources for {checked} of {total} saved tools checked; no new plays match this edition.Add your toolsRead the details on the webIn {count} daysWe corrected {wrong} of {count} reviewed Plays.
Summary
Maka is an open-source agent workspace that records every model message, tool call, and permission decision as an append-only log for task execution and recovery. It is licensed under the Apache License, Version 2.0, and functions as a desktop application. It is designed for practitioners who build and test automated workflows, and its documentation positions it alongside other agent harnessesagent harnessesThe software around an AI agent that manages its tools, execution loop, state and limits. It determines how the model's proposed actions are run and checked.. The project has seen steady activity with recent repository updates.
Apache Maka (Incubating) is a high-performance agent workspace that keeps a complete record of everything it did.
Chinese (Simplified)
Documentation: Chinese (Simplified)
Features
12 capabilities
Built from maka's releases, docs, README and our own runs.
“Seen” marks the month we first spotted a release the vendor didn't date.
Group names and tags are our labels.
maka covers 1 of the 6 ai evaluation and governance capabilities we track.
What maka offers you
Command-line interface2
Administrative audit log1
CI/CD pipeline integration1
Disaster recovery1
Show
No capabilities match.
+All capabilities12 capabilities▸
+Agent workspace audit logshippedRecords every model message, tool call, and permission decision as an append-only log to support task execution tracking and recovery.4 releases · 1 other source · first seen Jul 2026▸
Shared capability: LLM application tracing
Also counts toward: Administrative audit log
release
Adds MAKA_CONTEXT_ACTIVE_TOOL_RESULT_MIN_STEP_NUMBER environment variable to control the step number at which active pruning begins.
0.1.2 · Jul 2026
· source
· release history
Introduces internal AgentRun ledger and file-backed AgentRunStore for durable trace writes, expanding runtime kernel architecture beyond implicit session management.
0.1.2 · Jul 2026
· source
· release history
Adds MAKA_CONTEXT_ACTIVE_TOOL_RESULT_MAX_ESTIMATED_TOKENS configuration knob to tune the token threshold for archiving large tool results (default 2048).
0.1.2 · Jul 2026
· source
· release history
Adds MAKA_CONTEXT_ACTIVE_TOOL_RESULT_PRUNE=off environment variable to opt out of the new default active tool-result pruning behavior in both desktop and headless modes.
0.1.2 · Jul 2026
· source
· release history
docs
Agent workspace that records every model message, tool call, and permission decision as an append-only log for task execution and recovery.
+Session diagnostics collectionshippedGuides users through collecting diagnostic information from a Desktop session to help troubleshoot conversation problems.1 release · 2 other sources · first seen Aug 2026▸
release
Adds opencode-free as a zero-credential default provider
0.1.3 · Aug 2026
· source
· release history
docs
- [Collect evidence for a Desktop conversation problem](./session-diagnostics.md) ([中文](./session-diagnostics.zh-CN.md))
seen Oct 2026
· source
example
Execute Computer Use tasks using the new dedicated executor binary.$ maka-cu --target <task_description>
0.1.4 · Aug 2026
· source
+Branch conversation managementshippedEnables branching side conversations to explore alternatives while preserving main thread context.1 release · 1 other source · first seen Aug 2026▸
release
Adds Codex-style side conversations to branch off a thread and return with the answer
0.1.8 · Aug 2026
· source
· release history
example
Branch a side conversation to explore an alternative approach without losing the main thread context.$ In the chat panel, use the side-thread option to start a new branch from the current context.
0.1.8 · Aug 2026
· source
+Custom pet appearance systemshippedSupports importing, managing, and persisting custom visual assets for the agent's interface.1 release · 1 other source · first seen Aug 2026▸
release
Enables custom pets with pack import, library management, persistence, and animation
0.1.8 · Aug 2026
· source
· release history
example
Import a custom pet pack to personalize your assistant's appearance.$ Go to Settings > Pets, then use the 'Import Pack' button to load your saved pet data.
0.1.8 · Aug 2026
· source
+CLI task executionshippedAllows direct session and command execution from the terminal or CI pipelines.1 release · 1 other source · first seen Aug 2026▸
Also counts toward: CI/CD pipeline integration, Command-line interface
release
Adds maka run subcommand to execute runs from the CLI.
0.1.7 · Aug 2026
· source
· release history
example
Execute a Maka session directly from the terminal or CI pipeline.$ maka run
0.1.7 · Aug 2026
· source
+Web search integrationshippedsuggestedProvides a unified web search capability with provider-native routing and citation metadata.2 releases · first seen Aug 2026▸
Suggested capability: Retrieval-augmented generation. This is our guess, not confirmed.
Also counts toward: Command-line interface
release
Adds a runtime WebFetch tool for agent capabilities.
0.1.7 · Aug 2026
· source
· release history
Added provider-native web search: one WebSearch routing layer that selects the current model provider or explicit Tavily execution, with OpenAI and Anthropic implementations, durable replay, citation metadata, and privacy-mode coverage across Desktop, CLI, Runtime Host, and opt-in Headless Harbor
0.1.5 · Aug 2026
· source
· release history
+Version-controlled task executionshippedManages Git workspaces and file changes with verified runtime integrity for reproducible agent tasks.2 releases · first seen Aug 2026▸
release
Bundled a hermetic Git runtime and gated managed workspace reads behind owner-bound Runtime Host execution
0.1.6 · Aug 2026
· source
· release history
Adds managed Git workspaces for version-controlled task execution
0.1.3 · Aug 2026
· source
· release history
+Managed workspace persistenceshippedMaintains agent state and conversation history using local SQLite memory and verified backups.2 releases · first seen Aug 2026▸
Also counts toward: Disaster recovery
release
Adds verified operational backups for data integrity
0.1.3 · Aug 2026
· source
· release history
Adds SQLite-backed local memory for persistent agent state
0.1.3 · Aug 2026
· source
· release history
+Bounded long-term memoryshippedExtracts and stores persistent agent memory for continuity across sessions.1 release · first seen Aug 2026▸
release
Adds bounded long-term memory extraction for agent sessions.
0.1.7 · Aug 2026
· source
· release history
+Extended agent concurrencyshippedSupports multiple concurrent subagent executions to increase task throughput.1 release · first seen Aug 2026▸
release
Extended agent swarm concurrency to support 32 concurrent ways via the tool's internal limits.
0.1.4 · Aug 2026
· source
· release history
+Cost trackingshippedsuggestedProvides metering of model calls to allow cost estimation for agent operations.1 release · first seen Aug 2026▸
Suggested capability: LLM application tracing. This is our guess, not confirmed.
release
Adds canonical model-call metering for cost tracking
0.1.3 · Aug 2026
· source
· release history
+Goal event wait coordinationdocumentedProvides a mechanism for consumers to wait on goal events, enabling synchronisation across agent tasks or subagents.1 other source▸
docs
- [Goal event wait consumers](./goal-event-wait-consumers.md) ([中文](./goal-event-wait-consumers.zh-CN.md))
seen Oct 2026
· source
Lines in monospace are the tool's own words: help text
parsed from its source, or an endpoint from its API document. Under
release, a line is our summary of a dated release. Under
docs, it is quoted from the tool's own documentation or
website. Each links back to the source it came from.
Command line
View
Source
No command matches.
load a captured run
composed command
No matchesTry a different search, or clear a filter to see more.
option surface across analysed releases
options at that releaseadded, per releaseremoved, per release
option
found in
since
description
No matchesTry a different search, or clear a filter to see more.
option changes per release — drag across the rail to set a range
→
Values are placeholders taken from each option’s declared default.
Nothing is executed here — the output shown is a recording of a run
that already happened.
Score card
Shipping velocityreleases a month, last 12 months
Documentation qualityrelease-notes rubric, 0–100
Breaking-change disciplinehow rarely a release breaks users, and notice given
Maintenance riskquiet time against its own cadence, maintainers
Innovation & surfacenew capabilities, API and MCP surface
Community health
Contributor trenddistinct committers, this year against last
Maintainer concentrationbus factor now against a year ago
Issue backlog trendissues closed per issue opened, 12 months
Responsivenessmedian time to a maintainer’s first reply
Nine scores for maka, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.
Each score is 0–100 on a published rubric, derived from data this site already shows.
A dimension we cannot measure says so — it is never scored 0 and never enters a rank.
How this is scored
Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
Documentation quality — the release-notes rubric published on the analytics page, unchanged.
Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.
Release-note detail over time
See how much detail maka puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.
Issue, contributor and maintainer activity in apache/maka, 2023-12 – 2026-11,
as of 2026-11-03. Twelve-month figures first; the trend lines run
the whole window.
Contributors155+155 vs prior 12 months
Maintainers10+10 joined · −0 left, last 12 months
Bus factor2committers behind half the commits
Community-filed74%of issues opened, last 12 months
Median time to close1.2 daysfirst maintainer reply 20 hours
Open backlog278of 1,592 issues ever filed
Issues opened / month119 · 33communitymaintainers
Open backlog278
Contributors / month0
Commits / month0
Starsnot measured
Issue themes, last 12 months
bugs 26%
features 28%
questions 0%
docs 1%
other 45%
Counts from the project's public repository and git history; no individuals
are identified. Maintainers are the committers covering 80% of the last year's
commits. how we measure this
Libraries its release ships
What its latest release locks, checked against known advisories.
None of its release's images build from a lockfile we can read.
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can
follow every release here.