What is remocli AGENTS.md?

Repository instructions for maintaining RemoCLI, a Windows and WSL control system for remote command-line sessions. They describe its gateway, per-WSL agent, network connections, web or Android client, deployment modes, and troubleshooting entry points.

Use them when maintaining RemoCLI, identifying its active USB, LAN, tunnel, or public mode, checking the gateway or agent, generating deployment configuration, or following troubleshooting documentation.

They provide a fixed order for diagnosing connection and login problems, starting with the gateway and agent before investigating the client. This helps identify which layer is actually failing.

How whulxc/remocli configures Codex and OpenCode

Reuse

Borrowing it

Nothing to install: this file belongs to whulxc/remocli. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/whulxc/remocli/main/AGENTS.md

Clone the repo

git clone --depth 1 https://github.com/whulxc/remocli

Made for: Codex, OpenCode.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/whulxc/remocli/agents-md/github.svg)](https://agentmods.dev/instructions/whulxc/remocli/agents-md)

Your own site

<a href="https://agentmods.dev/instructions/whulxc/remocli/agents-md"><img src="https://agentmods.dev/badge/instructions/whulxc/remocli/agents-md/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/whulxc/remocli/agents-md"><img src="https://agentmods.dev/badge/instructions/whulxc/remocli/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 997 This file is loaded in full into every session.

When invoked 997 The same file — it is already loaded in full.

Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00997	$0.00997
Opus 5.5	$0.00399	$0.00399
Sonnet 5.5	$0.00199	$0.00199
Haiku 4.5	$0.00100	$0.00100

Measured 2mo ago against content hash f30693d4f86d, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

remocli AGENTS.md scanned grade A with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

- `curl -sS http://127.0.0.1:8080/health`

AGENTS.md · 134 lines

How it starts

The opening of the file, as written. The whole thing — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.

RemoCLI Maintenance Guide

This repository is maintained as a Windows + WSL control plane for remote CLI sessions. Use this file as the default engineering context for new maintenance sessions.

What matters first

Treat the stack as four layers:
- gateway
- per-WSL agent
- transport (USB, LAN, Quick tunnel preview, Formal public deployment)
- Android/Web client state
For connection or login problems, always check layers in that order.
Do not start from app-side guessing when gateway or agent health is unknown.

Primary entrypoints

Gateway server: src/gateway/server.js
Agent server: src/agent/server.js
Frontend app: src/frontend/app.js
Android shell: android/app/src/main/java/com/remoteconnect/mobile/MainActivity.kt
Deployment config generation: scripts/generate-deployment-config.mjs
Public deployment notes: docs/public-deployment-modes.md
Troubleshooting: docs/troubleshooting.md

Default troubleshooting flow

1. Identify the active mode

USB direct
LAN direct
Quick tunnel preview
Formal public deployment

Do not treat the Cloudflare Access team domain as the application hostname.

2. Check the local stack

Gateway:
- curl -sS http://127.0.0.1:8080/health
Agent:
- node scripts/check-deployment.mjs <deployment-manifest>
Logs:
- tail -n 80 data/runtime/gateway.log
- tail -n 80 data/runtime/agent-*.log

3. Check the transport

USB:
- adb devices
- adb reverse --list
LAN:
- test the Windows LAN URL from the host first
Formal public:
- curl -I https://<public-hostname>
- if 1033, check named tunnel state and logs

4. Only then check client state

Web page stale state: refresh once
Android stale state: reopen app once
Only use UI tree / logcat when:
- the user says “still broken”, or
- server-side state is healthy but phone behavior disagrees

Low-token maintenance defaults

Do not restate the entire README in every maintenance session.
Read AGENTS.md first, then only open files relevant to the active problem.
Prefer short status reports:
- root cause
- exact fix
- validation
- whether web refresh / app reopen / gateway restart / agent restart is needed
For repeat issues, reuse the same path:
- mode -> gateway -> agent -> transport -> client

Read the full file on GitHub · 134 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

2mo ago First seen · 134 lines · 997 tokens per session scan A f30693d4f86d

Subscribe to this mod's changes

remocli AGENTS.md is an instructions file published in the GitHub repository whulxc/remocli (5 stars, last pushed 7mo ago), licensed MIT. It adds 997 tokens to every session, about $0.0040 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

android cloudflare-tunnel codex-cli remote-console tmux webview

remocli AGENTS.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
remocli AGENTS.mdwhulxc/remocli	Instructions file	5	7mo ago	MIT	A	997	Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	yesterday	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	yesterday	MIT	A	4,680	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	5,516	GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	3,093	GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness	Instructions file	274k	2d ago	MIT	A	4,313	Codex, OpenCode

remocli: Instructions file for Codex