trafficbot

Audit fixes — 2026-10-30

Implemented

Verification

Check Result
Backend build and ESLint Pass
Full backend suite 254 pass, 45 skipped; exits normally
Frontend build and tests Pass; 18 tests
Control API integration 8 pass; exits normally
Shared Redis proxy capacity 6 pass, including competing allocator instances
Real local browser integration Pass: session success, stop, manual retry, stop again, live events, safe shutdown
Compiled controller integration Same lifecycle passes with compiled macOS sidecar; no automatic work on startup
Rust check Pass on macOS ARM64
macOS app/updater archive build Pass, local unsigned release build
Native UI Automatic owned-controller connection, live zero-work dashboard, close preference and idle quit verified

Tests used a disposable Redis container on loopback port 26389 and controlled local HTTP fixtures. Other project containers were left alone. Screenshot: /tmp/trafficbot-fixes-proof/native-dashboard.png.

Verification limits and remaining product scope

Windows/Linux installers and macOS x64 need execution on their native hosts; release signing, notarization and installation from the public updater feed were not performed. A local unsigned archive is not a signed distributable release. The public updater feed did not provide a valid release during native UI verification; the installed app was preserved.

Frontend lint has no error diagnostics but still reports advisory React/style warnings. Vite reports a roughly 748 kB main chunk; route splitting remains a performance improvement.

Multi-target campaigns, campaign-wide concurrency and selected proxy pools are now implemented; see campaign execution. The remaining product scope includes complete live navigation/page-visit telemetry, centralized remote-worker log ingestion, arbitrary remote-controller configuration and full accessibility verification. Existing log search only finds events available to the controller and is not a complete remote-worker log archive.

Historical note: subsequent work added worker execution timelines and curated remote-worker events. See the current session visibility guide for those capabilities and retention limits.

Development

Use npm run dev:desktop to launch the native app; it builds and starts the dedicated controller. Start Redis and execution workers separately. Use npm run build:desktop to stage the platform-specific sidecar and create native bundles. Build macOS x64 on an x64 host so the sidecar and Tauri binary match.

Settings are stored in $TRAFFICBOT_CONTROL_DIR/.env or ~/.trafficbot/.env. Default desktop data, logs and preferences are outside the installed application resources. Restart affected external workers separately after configuration changes.