Codex Netwatch

LOCAL VISIBILITY. CLEARER ANSWERS.

See where your Codex
network traffic goes.

A local Windows dashboard for traffic history, process attribution, and connection troubleshooting.

Windows 10/11 x64 · Mihomo / Clash-compatible controller required

Latest releasev0.2.6 ↗
Local-first No app telemetry MIT licensedCODEX NETWATCH / WINDOWS

01 / THE OVERVIEW

Your network activity,
in one clear view.

Follow observed uploads and downloads, spot changes over time, and narrow the view to the period you need.

Codex Netwatch dashboard showing observed traffic, a history chart and process rankings
CODEX NETWATCH OVERVIEWOpen full-resolution image

02 / FOLLOW THE EVIDENCE

From “how much?”
to “what happened?”

01

Traffic over time

See observed upload and download totals, live rates and history. Filter a time range or export a CSV for a closer look.

02

Processes with context

Identify Codex and its child processes using process evidence. Compare with other proxy applications when you need context.

03

Connections that explain

Inspect destinations and connection activity. Find upload or download bursts, sustained uploads and collection gaps.

04

A separate activity trail

Use session activity and local-log token counts as troubleshooting clues, alongside network observations.

LOOK A LITTLE CLOSER

Give unusual traffic
a starting point.

Move from a spike in the chart to connection destinations and process evidence. Keep session activity in context without treating it as a precise traffic allocation.

Configuration & troubleshooting
DEMO VIEW · SYNTHETIC DATA
Synthetic demo of the investigation view with traffic events and connection evidence

03 / GET STARTED

Three steps to a clearer picture.

  1. Download & extract

    Get the Windows x64 portable ZIP and SHA256SUMS.txt from the same release. Verify the checksum, then extract the entire archive into a writable folder.

  2. Start your tools

    Run a compatible proxy and Codex, then open Codex-Netwatch.exe. The portable package includes Node.js.

  3. Check, then make a request

    Follow Connection help, send a new Codex request and wait for two samples. Existing connections establish a baseline first; only new traffic is counted.

Before you download

Windows 10/11 x64, .NET Framework 4.8 and Microsoft Edge WebView2 Runtime are required. The Windows EXE is currently unsigned. Verify the downloaded ZIP against the release checksum file.

What the numbers mean

Bytes come from controller connection snapshots. Direct traffic that bypasses the controller is invisible. Short connections and final bytes before closing may be missed. These totals are not network-adapter traffic or a VPN bill. Long-running 24/72-hour validation has not been completed.

04 / GOOD TO KNOW

A few things, made clear.

Will it work with my proxy or VPN?

Network collection needs a running Mihomo / Clash-compatible local controller. Not every VPN or proxy client exposes a compatible controller. Use the controller port, not the HTTP / SOCKS proxy port; check the configuration guide for details.

Why is the traffic showing zero?

Check Connection help for controller reachability, the secret and response compatibility. Make sure Codex traffic passes through that controller and has process evidence. Then generate a new request and wait for two samples. Connecting or reconnecting first establishes a baseline; offline traffic is not backfilled.

Does closing the window stop collection?

Closing the desktop window keeps collection running in the tray. Double-click the tray icon to reopen it. Use Exit in the tray menu to stop it fully. Start at login is optional and off by default.

Does it upload my chats?

The app has no telemetry and stores observations locally. Its local database includes destinations, process identities, session metadata, tokens and activity times; it does not persist chat bodies, tool content, command lines or credentials. Keep your database, configuration and raw CSV private. This website is a static introduction and does not connect to your local monitor.

Can it measure exact GB for each conversation?

No. Shared processes and connections cannot be split precisely into per-session GB. Session activity is a separate investigation clue, not proof of byte attribution.

Are tokens my subscription balance or bill?

No. Token counts come from local logs. They cannot be converted to GB, remaining subscription allowance, a bill or official billed usage.

OPEN SOURCE / READY WHEN YOU ARE

Make your traffic
a little less mysterious.

A portable dashboard. A local view. The evidence to investigate.

v0.2.6 Windows x64 MIT