Mihomo命令行

Use the bundled script for repeatable Mihomo operations instead of re-discovering paths and API auth each time.

Quick start

Run:

CODEBLOCK0

The script auto-detects common Mihomo installs by checking:

• - INLINECODE0
• INLINECODE1
• INLINECODE2

It extracts:

• - INLINECODE3
• INLINECODE4

Common commands

CODEBLOCK1

When switching a group

1. 1. List groups first:

CODEBLOCK2

1. 2. Switch the selector/group to a target proxy:

CODEBLOCK3

Use exact group and proxy names.

For latency / node quality questions

Default to:

CODEBLOCK4

This shows the latest recorded delay from Mihomo's history.

If the user wants a live test for one node, run:

CODEBLOCK5

Treat 0ms with caution: it may indicate missing/failed measurement rather than a truly perfect route.

For deeper API work

Read references/api.md when you need raw endpoint details, request shapes, or want to call an endpoint not wrapped by the helper script.

Practical notes

• - Prefer read-only commands first (status, proxies, groups, connections) before mutating state.
• Before switch or restart, be sure that changing the active route is actually what the user wants.
• If API requests return Unauthorized, re-check secret from the detected config.
• If the script cannot find config automatically, inspect running processes for mihomo, clash, verge, or clashmac, then locate the active config path from process args.
• On macOS with ClashMac, the real core may run as mihomo under ~/Library/Application Support/clashmac/core/ while the GUI runs as ClashMac.app.

Useful fallback detection

When auto-detect fails, use:

CODEBLOCK6

Then inspect the config path from the process command line.