# Maka CLI

Coordinate Maka CLI as a worker to submit tasks, inspect progress, update saved models...

- Repository: https://github.com/apache/maka (5932 stars)
- Category: Engineering
- License: Apache-2.0
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add apache/maka --skill maka-cli -g -a claude-code -y`
Codex: `npx skills add apache/maka --skill maka-cli -g -a codex -y`
Cursor: `npx skills add apache/maka --skill maka-cli -g -a cursor -y`
Gemini CLI: `npx skills add apache/maka --skill maka-cli -g -a gemini-cli -y`

## Description

Coordinate Maka CLI as a worker to submit tasks, inspect progress, update saved models, and handle Session questions or approvals.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

<!--
  Licensed to the Apache Software Foundation (ASF) under one
  or more contributor license agreements.  See the NOTICE file
  distributed with this work for additional information
  regarding copyright ownership.  The ASF licenses this file
  to you under the Apache License, Version 2.0 (the
  "License"); you may not use this file except in compliance
  with the License.  You may obtain a copy of the License at

      http://www.apache.org/licenses/LICENSE-2.0

  Unless required by applicable law or agreed to in writing,
  software distributed under the License is distributed on an
  "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
  KIND, either express or implied.  See the License for the
  specific language governing permissions and limitations
  under the License.
-->

# Maka CLI

Delegate work to Maka; the parent owns the assignment and final judgment.

## Submit, then wait

Check `maka run --help` for the installed interface. This skill does not upgrade Maka. Preserve the user's Host, model, cwd, and permissions; otherwise use existing defaults. Repeat the same `--host <profile-id>` on subsequent calls. Model, connection, and thinking options can also persistently update an existing Session.

Prefer this flow when coordinating work across calls:

```sh
maka run "Inspect the project and report findings" --no-wait
# Save the returned sessionId with its Host and assignment as $session.
maka run --session "$session" --wait --json
```

`--no-wait` already returns JSON. It is the recommended parent-agent workflow, not the CLI's global default: ordinary `maka run "…" --json` still waits and suits a single call. Detached work requires a persistent installation and cannot own CLI MCP servers or use Graph Mode.

Wait when ready for the next interaction or result; avoid repeated status polling. A Session-only wait selects its current Turn, or the latest result if idle. It does not drain the whole queue.

The rest: https://github.com/apache/maka/blob/HEAD/skills/maka-cli/SKILL.md