Request on feature of Clash API and safety defaults #468
Labels
enhancement
New feature or request
low periority
To be deployed during the time
to deploy
Considerable for implementation
Is your feature request related to a problem? Please describe.
In previous versions, there was a clash api option in experimental section, but now it is gone.
Describe the solution you'd like
I hope clash API can be added back, as it is quite convenient to perform remote flow controling.
Describe alternatives you've considered
No
Additional context
The listen address by default for clash API better be 127.0.0.1, and hopefully the panel and the subscription service can also listen to 127.0.0.1.
The text was updated successfully, but these errors were encountered: