Linux / x64
clashtui-linux-amd64-v0.3.1.gz
1.6 MB · v0.3.1 (opens in a new tab or window)
Open upstream asset (opens in a new tab or window)SHA256 / source record
sha256:4d4cf18563794ed9e0220bb843f5ca0ee3d81b008dd4d9cd2dff65082fa4735b
Clients
ClashTUI
Architecture labels are derived from asset names. Minimum OS, installation formats and runtime dependencies still require release documentation.
- Installation test
- Not performed
- Project type
- Clients
Upstream release assets
Platform and architecture are based on upstream information. Review release notes, minimum OS and dependencies before installing.
No matching downloads
There are no reviewed files or store listings for the current selection.
Linux / arm64
clashtui-linux-arm64-v0.3.1.gz
1.5 MB · v0.3.1 (opens in a new tab or window)
Open upstream asset (opens in a new tab or window)SHA256 / source record
sha256:d9e9f7b66698a67e40177b19ba6f23a71b7a787d2ba32f43212ffa878b5f6788
Windows / x64
clashtui-windows-amd64-v0.3.1.zip
1.4 MB · v0.3.1 (opens in a new tab or window)
Open upstream asset (opens in a new tab or window)SHA256 / source record
sha256:1e107cfb8c3823e8931acfcc5171e1c288b2fd912b4e4915ab30f570bbd29ef2
Windows / arm64
clashtui-windows-arm64-v0.3.1.zip
1.3 MB · v0.3.1 (opens in a new tab or window)
Open upstream asset (opens in a new tab or window)SHA256 / source record
sha256:41efb6b4f07b306c3a8754214a9386598f41cb17d7026ca39f82c22ee5ea22b2
macOS / x64
clashtui-darwin-amd64-v0.3.1.gz
1.4 MB · v0.3.1 (opens in a new tab or window)
Open upstream asset (opens in a new tab or window)SHA256 / source record
sha256:c409e90ecc85b98eef1371ffcf8893f4792e0e6d09b1a94b5e5e96db16d7320c
macOS / arm64
clashtui-darwin-arm64-v0.3.1.gz
1.4 MB · v0.3.1 (opens in a new tab or window)
Open upstream asset (opens in a new tab or window)SHA256 / source record
sha256:28616a1e18ebf12ea06064048b8771d95389a158ed85f6060ae3ba2ea66681f3
Project and release sources
https://github.com/JohanChane/clashtui (opens in a new tab or window)
Source attribution, checksums and security review are distinct. Unknown details are not marked verified.
From documentation to setup
- Confirm the project and device requirements.
- Use upstream documentation to choose a file or deployment method.
- Understand configuration format, then review runtime logs.
What else should I check?
Is my device guaranteed to work?
No. Device installation tests have not been performed here. Review the project’s OS, privilege and runtime requirements.
Are legacy projects and later forks the same?
No. Project identity and release sources are recorded separately; another maintainer’s software is not presented as an official update of the original project.