@yu_robotics/remote-cli weekly downloads statistics

@yu_robotics/remote-cli

Remote control Claude Code, AGY CLI, Codex CLI, OpenCode CLI, Kimi Code CLI, ZCode, or Pi from anywhere using your mobile phone through Feishu (Lark) messaging.

Features

• Remote Control: Control your local development environment from anywhere via mobile • Access Controls: Working-directory allowlist and user-device binding • Mobile-Optimized: Simplified commands and rich text formatting for Feishu • Readable Code Changes: Edit operations show collapsible, line-aware diff previews inside the existing progress card • Multi-Backend Support: Supports Claude Code, AGY CLI (Antigravity), Codex CLI (OpenAI), OpenCode CLI, Kimi Code CLI, ZCode, and Pi • Image Input and Output: Forward Feishu images to supported backends and return Codex native image output. All backends can return local images through file paths or Markdown image links; files must be inside an allowed directory and no larger than 2 MiB. AGY does not accept image input. • Multi-session (Threads): Create independent chat threads to parallelize tasks • Remote Machine Management: Control remote servers or Docker via SSH • Persistent Process: Long-running AI process with bidirectional streaming • Automatic Updates: Install the newer Router's exact version when idle. Manual clients keep running and use the update on their next start; supervised non-interactive clients exit for an immediate restart. • Task Recovery: With a compatible Router, running tasks resume output on a usable surviving card or a new card with an output-gap notice. Recovery retries use bounded backoff; disconnected output is not buffered or replayed, even after recovery is paused.

Router 1.6.117 and newer explicitly label standalone background-task notifications Background task. The status, originating thread name (or thread ID when no name is provided), and abbreviated task ID remain visible, while View details is collapsed by default and contains the rich Markdown result and optional output path. Failed tasks also show a short, literal failure summary outside the panel. This changes only the Router presentation: the CLI protocol, foreground replies, delegated-worker cards, and reply-to-thread routing remain unchanged.

Public Activity

From Router 1.6.158, completion pagination keeps the final body item (or complete worker group) with the completion note, optional model metadata and thread controls when they fit together. This avoids preventable footer-only continuations, including replies without model metadata. Indivisible oversized groups still split according to node, size and table limits; thread-button refreshes preserve the final body. This does not change streaming completion timing or the wire protocol.

From CLI 1.6.153, Codex shell calls no longer lose their label when native command actions are absent or unknown. Native reads, searches, and directory listings remain preferred. Other calls use fixed operation labels such as Run npm command or Run Git command for simple allowlisted programs, and Run shell command for compound or unrecognized commands. These are deterministic operation labels, not model-authored purpose summaries: installed Codex 0.160.0 command items have no per-call description field. Arguments, full paths, output, and execution-wide reasoning are never copied into these fallback labels. Late native action metadata can enrich a pending row before its first result; repeated results retain one row. Existing description fields, heading limits, and card-node counts are unchanged; upgrade the CLI, with no new Router capability required.

Router 1.6.145 combines each foreground tool call and its matching result into one collapsed row, retaining input, output, and diff previews. Independent calls, workers, and approvals remain separate. This uses the existing CLI protocol; the client does not need a new capability. See Code Change Previews.

Router 1.6.146 gives Bash and other foreground tools one compact heading with a gray success dot, pending hourglass, or gray failure cross, plus the tool name and an optional public description or file basename. Full tool IDs and explicit status labels remain inside the expanded details. Raw commands are not fallback headings; the existing CLI protocol is unchanged.

CLI and Router 1.6.147 preserve ACP call/update titles and explicit AGY/Pi parameter descriptions or titles as optional tool-use metadata. Meaningful call labels take precedence over file basenames, without copying execution-wide activity into tool headings or generating missing summaries. Terminal-only titles never synthesize calls; results update status/output and preserve the existing label. Labels remain literal and bounded inside the existing heading and add no card nodes. Upgrade both peers to show newly forwarded labels; older peers retain their existing tool data and presentation.

From Router 1.6.148, the status symbol is always a dot (•): green for success, blue while awaiting a result, and red for failure. This replaces the pending hourglass and failure cross without changing per-call labels, expanded status text, asynchronous in-place updates, or card-node counts. The color change alone does not require a CLI protocol update.

CLI and Router 1.6.144 add optional activityProgress snapshots. Public text, explicit Codex commentary and public summaries, plan steps, and safe tool labels remain separate from answers and raw thinking. The latest main card shows a mutable tail row; each worker shows its activity below its identity. Input and terminal states take precedence. Snapshots are bounded to 240 Unicode code points, coalesced at 2.5 seconds, and do not extend liveness deadlines or bypass worker result barriers. Worker activity also requires delegationProgress. Older peers keep their existing behavior; no percentage, model call, or prompt is added. See Public Activity for provider coverage limits.

Maintenance Notices…

Description from the npm listing.