Skip to content

Feature request: allow adding/editing proxy nodes from the web UI #2106

Description

@EraAsh

Feature Request

Please consider adding a web UI feature to manually add/edit proxy nodes, similar to Clash desktop clients.

Current situation

MetaCubeXD is great for viewing proxy groups, testing latency, selecting nodes, and managing existing providers. However, when a user wants to add a new vmess / socks5 / http / trojan / ss node, they still need to edit the Mihomo YAML config or use an external subscription manager such as Sub-Store.

For self-hosted or homelab users, this makes the setup less convenient:

  • open dashboard to check nodes
  • leave dashboard to edit config / provider source
  • reload Mihomo config
  • go back to dashboard

Expected behavior

Add a page/dialog in the web UI to create and manage custom nodes, for example:

  • Add node manually by protocol form:
    • vmess
    • socks5
    • http / https
    • trojan
    • ss
  • Import a single share link, e.g. vmess://, trojan://, ss://
  • Save nodes into a local/custom provider or generate a managed provider section
  • Trigger Mihomo config reload after saving
  • Optional: allow grouping these custom nodes into an existing proxy group

Why this is useful

This would make MetaCubeXD usable as a full proxy management dashboard instead of only a viewer/controller for existing config.

A common user flow would be:

  1. Open MetaCubeXD
  2. Paste a vmess:// or SOCKS node
  3. Save
  4. The new node appears in proxy groups and can be selected/tested immediately

This is especially useful for users who run Mihomo on a home server/NAS and do not want to manually edit YAML every time they add a node.

Notes

I understand that Mihomo core owns the actual config format and reload API, so this could be implemented as a dashboard-side helper that writes/updates a managed provider/config section and then calls the existing reload API.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions