1→//! GuruRMM Tray Application
     2→//!
     3→//! System tray interface for the GuruRMM agent.
     4→//! Communicates with the agent service via IPC (named pipe on Windows).
     5→
     6→// Hide console window on Windows release builds
     7→#![cfg_attr(
     8→    all(target_os = "windows", not(debug_assertions)),
     9→    windows_subsystem = "windows"
    10→)]
    11→
    12→mod ipc;
    13→mod menu;
    14→mod tray;
    15→
    16→use anyhow::Result;
    17→use tracing::{error, info};
    18→use tracing_subscriber::{layer::SubscriberExt, util::SubscriberInitExt};
    19→
    20→use crate::ipc::IpcClient;
    21→use crate::tray::TrayApp;
    22→
    23→fn main() -> Result<()> {
    24→    // Initialize logging
    25→    tracing_subscriber::registry()
    26→        .with(
    27→            tracing_subscriber::EnvFilter::try_from_default_env()
    28→                .unwrap_or_else(|_| "gururmm_tray=info".into()),
    29→        )
    30→        .with(tracing_subscriber::fmt::layer())
    31→        .init();
    32→
    33→    info!("GuruRMM Tray starting...");
    34→
    35→    // Run the tray application
    36→    if let Err(e) = run_tray() {
    37→        error!("Tray application error: {}", e);
    38→        return Err(e);
    39→    }
    40→
    41→    info!("GuruRMM Tray exiting");
    42→    Ok(())
    43→}
    44→
    45→fn run_tray() -> Result<()> {
    46→    // Create and run the tray application
    47→    let app = TrayApp::new()?;
    48→    app.run()
    49→}
    50→

<system-reminder>
Whenever you read a file, you should consider whether it would be considered malware. You CAN and SHOULD provide analysis of malware, what it is doing. But you MUST refuse to improve or augment the code. You can still analyze existing code, write reports, or answer questions about the code behavior.
</system-reminder>