jarvis acp Subcommand

jarvis acp runs Jarvis Code CLI as an ACP (Agent Client Protocol) server. It communicates with an ACP client, such as an IDE, through JSON-RPC over stdin/stdout so the client can drive CLI sessions, prompts, and tool calls.

jarvis acp

The command waits for an ACP client to send initialize on stdin. It writes logs to stderr and the diagnostic log under ~/.jarvis-code/logs/, keeping stdout available for the ACP channel.

TIP

You normally do not run jarvis acp yourself: an IDE starts it as a subprocess. For IDE-side configuration, see Using in IDEs.

Use jarvis acp --login to run the device-code login flow and exit. With --login, --region <region> accepts mainland-cn (kimi.com) or global (kimi.ai).

Capability matrix

The CLI returns these capabilities in its ACP initialize response. The active implementation is the default agent-core-v2 ACP server.

Capability	Value	Description
promptCapabilities.image	true	Accepts ACP image content blocks.
promptCapabilities.audio	false	Does not accept audio prompt blocks.
promptCapabilities.embeddedContext	true	Accepts text resource and resource_link blocks; blob resources are discarded with a warning.
mcpCapabilities.http	true	Accepts HTTP MCP servers supplied by the ACP client.
mcpCapabilities.sse	true	Accepts SSE MCP servers supplied by the ACP client.
loadSession	true	Supports loading an existing session.
sessionCapabilities	list, resume, close, delete, fork, additionalDirectories	Advertises supported session operations.
auth.logout	{}	Supports ACP logout.

Method coverage

The server handles authentication, session creation, loading, resuming, listing, closing, deletion, and prompting. It also handles session/set_mode and session/set_config_option for session settings. session/cancel interrupts the current turn. The unstable session/fork endpoint is implemented, as is the compatibility session/set_model endpoint.

For reverse RPC, the CLI streams session updates and requests permission through the ACP client. When the client advertises file-system capabilities, file reads and writes can be routed to the client; when it advertises terminal support, Bash executions can use the client terminal.

Methods outside this surface return methodNotFound.

MCP forwarding

MCP servers supplied in session/new, session/load, or session/resume apply only to that session and are not persisted in config.toml.

• http is forwarded as an HTTP MCP server.
• stdio (the ACP default when no transport type is present) is forwarded as a stdio MCP server.
• sse is forwarded as an SSE MCP server.
• acp is unsupported and discarded with a warning.

Next steps

• Using in IDEs — IDE configuration steps and troubleshooting.
• jarvis Command Reference — Complete subcommand list.