Repository navigation
specola v0.2.1-beta
Specola is a proxy application with separate Core and desktop UI processes. This beta provides a Qt Quick desktop interface for configuration management, proxy control, connection inspection, routing rules, and logs.
Proxy and traffic control
- HTTP and SOCKS5 local proxy listeners.
- Support for protocols including Shadowsocks, Trojan, VMess, VLESS, Hysteria2, and SSH.
- Rule, Global, and Direct routing modes, with system proxy controls.
- Configurable DNS, traffic sniffing, and rule-based routing.
- TUN enhanced routing and Linux eBPF transparent proxy support, subject to platform capabilities, configuration, and permissions.
Desktop interface
- Overview: Core status, live upload/download rates, and traffic statistics.
- Connections: Filter and inspect connections, close selected connections, or close all active connections.
- Proxies and rules: Browse proxy and rule lists and inspect their details.
- Logs: Filter by severity, pause updates, inspect startup output, and open the log directory.
- System tray: Open the interface, switch routing modes, and control system proxy and enhanced routing.
Configuration management
- Import local TOML profiles, rename them, activate them, and reload configurations.
- Core manages profile files and their lifecycle.
- Importing a profile does not activate it. Select Use this Profile to start using it.
- Removing an inactive profile moves its file into the
.removeddirectory.
Interface and runtime behavior
- Light and dark themes, optional restoration of the last page at startup, and configurable automatic refresh intervals.
- Choose whether closing the window hides it or releases the interface while keeping the system tray available.
- Release desktop builds can launch and manage a local Core, or connect to an existing Core.
- Core and UI communicate over MessagePack-RPC, separating proxy operation from interface management.
Getting started and limitations
- This is a beta prerelease.
- Import a TOML profile and activate it manually after launching the application.
- TUN / eBPF require the appropriate system permissions.
- Release packages do not include GeoIP / GeoSite datasets by default. Supply these files separately when using rules that require them.