feat(wallet-cli): Add wallet CLI with daemon support

[rekmarks]

Introduces an oclif CLI for @metamask/wallet. It is more or less a port of the Ocap Kernel equivalent.

Usage

First, cd packages/wallet-cli.

Then, to start the daemon:

yarn mm daemon start \
  --infura-project-id <YOUR_PROJECT_ID> \
  --password testpass \
  --srp 'test test test test test test test test test test test ball'

Try calling an available controller action:

yarn mm daemon call AccountsController:listAccounts

Actions params must be specified as a stringified JSON array:

yarn mm daemon call \
    KeyringController:signPersonalMessage \
    '[{"data": "0x48656c6c6f2c20776f726c6421", "from": "0xc6d5a3c98ec9073b54fa0969957bd582e8d874bf"}]'

When done, stop the daemon and clean up:

yarn mm daemon purge --force

Summary

• Create wallet-cli package scaffolded with oclif (mm binary)
• Implement daemon infrastructure for running a @metamask/wallet instance as a detached background process, communicating over JSON-RPC via Unix domain sockets
• Add daemon commands: start, stop, status, purge, call
• call command dispatches arbitrary messenger actions to the running daemon (e.g. mm daemon call AccountsController:listAccounts)
• Unit tests for all daemon modules (108 tests, 100% coverage on daemon code)

---

Note

High Risk
Introduces a new local daemon that can dispatch arbitrary wallet messenger actions over a socket and requires handling secrets (SRP/password) and process lifecycle correctly, which is security- and reliability-sensitive despite being new code.

Overview
Introduces a new @metamask/wallet-cli package (Oclif mm binary) that can start @metamask/wallet as a detached background daemon and communicate with it over newline-delimited JSON-RPC on a Unix domain socket.

Adds daemon management and interaction commands (start, stop, status, purge, call), including a call pathway that forwards arbitrary messenger actions to the running wallet instance, plus supporting socket server/client/spawn/cleanup utilities with extensive unit tests.

Monorepo wiring is updated to include the new workspace in README.md, CODEOWNERS/teams.json, root tsconfig references, ESLint overrides, and Yarn workspace validation; @metamask/wallet now exports importSecretRecoveryPhrase for CLI consumption.

^{Reviewed by Cursor Bugbot for commit 8e1bd9d. Bugbot is set up for automated code reviews on this repo. Configure here.}

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​metamask/​auto-changelog@​3.4.4
	@​inquirer/​confirm@​6.0.7 ⏵ 6.0.11	+1			-2
	@​oclif/​core@​4.10.5

View full report

[rekmarks]

@SocketSecurity ignore npm/jake@10.9.4

Transitive via @oclif/core. Usage not suspicious.

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 8e1bd9d. Configure here.}

[cursor]

Handler lookup vulnerable to prototype method invocation

Low Severity

The handlers[method] lookup on a plain object doesn't guard against Object.prototype properties. If a client sends a request with method set to "constructor", "toString", "hasOwnProperty", etc., the lookup returns a truthy built-in function instead of undefined, bypassing the "Method not found" check. The server then invokes that prototype function as if it were an RPC handler, returning an unexpected result instead of a -32601 error.

Using Object.hasOwn(handlers, method) (or creating handlers with Object.create(null)) before accessing the handler would ensure only explicitly registered methods are dispatched.

 

^{Reviewed by Cursor Bugbot for commit 8e1bd9d. Configure here.}