HugoTime is a Chrome extension paired with a NestJS backend that gives teams real-time visibility into browser activity across their organization, along with the ability to remotely manage connected devices, all through a live WebSocket relay.

Tracks tab activity automatically. The extension logs time spent per tab, tracks opened tabs, and surfaces the most active site, all live, with no manual input from the user.

Real-time admin dashboard. A central dashboard shows every connected extension at a glance: who's online, session status, latency, and total activity across the fleet.

Two-way WebSocket communication. Built on a persistent WebSocket relay, the backend can push commands directly to any connected extension instantly, not just receive data from it.

Remote command delegation. Admins can send commands to individual extensions from the dashboard, including requesting screenshots on demand, without requiring any action from the end user.

Detailed session and device info. Each connected user's session includes device details, connection time, client ID, and activity history, giving admins a complete picture of every endpoint.

Built for scale. The architecture (WXT for the extension, NestJS for the backend, WebSockets for real-time sync) is designed to handle many concurrent connections reliably, with visible relay uptime and ping stats.

This kind of system is ideal for organizations that need centralized visibility and control over company-managed devices, such as remote team monitoring, IT fleet management, or time-tracking for distributed teams, where real-time data and remote administration matter more than a static reporting tool.

WXT. Modern framework for building the Chrome extension, handling manifest configuration, bundling, and cross-browser compatibility.

Chrome Extension APIs. Tab tracking, activity monitoring, and background service worker for capturing browser events in real time.

NestJS. Backend framework powering the admin server, structuring the WebSocket gateway, session management, and command routing.

WebSockets. Persistent, bidirectional connection between the extension and backend, enabling live data streaming and instant command delegation (including remote screenshot requests).

TypeScript. Used across both the extension and backend for type safety and maintainability.

EJS. Server-side templating for rendering the admin dashboard UI, including the live fleet view, session details panel, and connected-extensions list.

Chrome Storage API. Local persistence of session and activity data on the extension side.

REST/WebSocket Hybrid Architecture. Combines request-based endpoints with a real-time relay for status sync, latency tracking, and event queuing.