MaKa provider for Paseo

Unmaintained since 2026-09-24. MaKa is still changing too quickly to track release by release. The last release is maka-v0.1.0-beta.4, tested with signed MaKa Desktop/CLI 0.2.0-dev.39.20260916 on Paseo 0.9. Newer MaKa nightlies are not reviewed or supported. The code stays here so the provider can be revived later.

An experimental server-only plugin that adds MaKa to Paseo 0.9's provider picker through the official maka --acp interface. It supports streamed conversations, tool cards when MaKa emits them, standard tool approvals, real file and shell work, follow-up prompts, cancellation, and MaKa's configuration selectors.

Install

Requirements: Paseo 0.9.0-beta.1 with plugins enabled, Node.js 22.19 or newer, and a configured MaKa CLI on the machine running the Paseo daemon. The tested signed MaKa release is 0.2.0-dev.39.20260916. Keep Desktop and CLI on the same MaKa release because they share a workspace database. The published .41, .42, and .43 nightlies were checked only in isolated profiles; they are not a reason to migrate a normal dev39 profile.

Install the matching CLI release:

npm install --global --ignore-scripts maka-agent@0.2.0-dev.39.20260916
maka

Use MaKa's own UI to configure a working provider connection, credentials, and a default model, then exit it. A working MaKa default is required before Paseo can discover the model catalog. The plugin neither imports credentials nor changes your MaKa profile.

Install the pinned plugin prerelease:

paseo plugin add geoqiao/paseo-stuff:plugins/maka --ref maka-v0.1.0-beta.4 --host <your-host>

For local development, run from this directory:

npm ci --ignore-scripts --legacy-peer-deps --no-audit --no-fund
npm run check
paseo plugin install "$PWD" --host 127.0.0.1:6767

Replace the host with your daemon's address if different. Source changes require a reload before they are visible to Paseo, and reloading ends existing MaKa sessions.

Select MaKa → MaKa configured default when creating an agent. The model label is a local selector for the model already chosen in MaKa; it does not switch the upstream model. Thinking levels depend on that model. MaKa also exposes collaboration, permission, and orchestration configuration through ACP; Paseo presents the selectors supported by its public ACP shim.

The provider launches the executable with the working directory and environment supplied by Paseo. If maka is unavailable on the daemon's PATH, set MAKA_PASEO_COMMAND in the daemon's environment to the absolute executable path. This variable accepts an executable path only; the plugin supplies --acp itself.

Current limits

The tested official MaKa ACP implementation has these boundaries:

• Tool visibility: When MaKa publishes standard ACP tool-call and tool-call-update notifications, Paseo renders the call, bounded output/progress, and final result through its public ACP shim. The published .41, .42, and .43 ACP line includes this mapper. Real .42 and .43 tool execution was not observed in isolated candidate profiles, and MaKa still publishes no ACP usage updates.
• MCP: MaKa rejects MCP servers. The plugin omits Paseo's MCP configuration and emits an explicit session notice, without exposing its values. Paseo's agent-management MCP is also unavailable inside MaKa conversations.
• Permissions and questions: Standard ACP tool permission requests are forwarded through Paseo's permission flow when MaKa emits them; the plugin never automatically approves tools. The public Paseo 0.9 ACP shim does not expose elicitation/create, so MaKa questions/forms and other elicitation interactions remain unsupported and fail explicitly. Configure effective behavior through MaKa's own UI where possible.
• History: follow-ups work while the session is connected. MaKa's ACP interface has native session listing and close, but no load/resume operation. The plugin therefore withholds session listing from Paseo so it cannot offer imports that would fail when opened. Imported history and restoration after plugin reload or daemon restart are unavailable. Requests carrying persistence are rejected. Shutdown closes the owned ACP session and allows MaKa to cancel its associated Runtime Host work before process termination.
• Prompt configuration: MaKa does not apply Paseo's _paseo metadata, including custom system prompts, provider options, or tool policy. Configure effective behavior in MaKa.
• Other input: image prompts, provider commands, and prompt steering are unsupported.

The plugin rejects unsupported requests and documents the remaining upstream gaps. It uses public SDKs and does not reconstruct missing features from private Runtime Host state.

These are limits of the tested MaKa ACP adapter, not the ACP protocol itself. Closing the ACP connection does not delete MaKa's durable history; the adapter lacks a way to reopen it. See the upstream maintenance procedure for how new MaKa releases are reviewed and supported capabilities are added.

Troubleshooting and verification

Check maka --version, ensure the same OS user can run MaKa with a working default, then inspect:

paseo plugin ls --host 127.0.0.1:6767
paseo provider models maka --host 127.0.0.1:6767
paseo plugin logs maka --host 127.0.0.1:6767

A configured free provider is not necessarily available for inference. Validate an ordinary prompt in MaKa if Paseo can discover selectors but turns time out.

If Desktop reports OperationalStateMigrationBlockedError or a schema newer than its supported version, update Desktop to match the CLI. Changing schema version numbers or restoring only part of the database is not a compatible downgrade.

npm run check runs TypeScript, lint, and tests against the public Paseo 0.9 ACP shim and synthetic ACP peers. Real CLI, installed-host, and UI evidence is in docs/verification.md, including the versions and platform limits.