Feature request: compact ↓ inbound / ↑ outbound traffic indicators in Remote terminal

Author: cxhttt233Created Sep 18, 2026Updated Sep 18, 2026

Feature request

It would be useful for the Remote terminal to have a compact fixed status line showing inbound and outbound Desktop Commander tool traffic.

Example:

✻ Reading   ↓ 12.4 KB   ↑ 3.8 KB   42 calls

From the device's point of view:

  • = inbound tool-call payloads / arguments (download to the device)
  • = outbound tool results (upload from the device)
  • calls = cumulative Desktop Commander tool calls for the current process/session

Why this is useful

For long-running or concurrent Remote work, it is hard to tell at a glance whether the device is receiving a request, still working, returning a large result, idle, or handling repeated calls. A one-line indicator gives useful feedback without flooding the terminal.

Working prototype

I implemented and tested this here: https://github.com/cxhttt233/desktop-commander-claude-style

The prototype keeps one fixed terminal line, updates inbound bytes and call count as soon as a tool call starts, updates outbound bytes from the real result, keeps the positions stable, and handles concurrent calls without counters moving backwards.

One important detail: these values should be described as serialized Desktop Commander tool payload bytes, not model tokens and not exact physical network bytes. A minimal ↓ input bytes ↑ output bytes calls version would already be useful.

Source: wonderwhy-er/DesktopCommanderMCP