← Files VARUA Remote ControlARCHIVED FILE
plugin.json
11.5 KB · Nov 3, 2026 · 19:19 UTC
{
"$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
"name": "varua-remote-control",
"version": "0.1.21",
"description": "Connect ChatGPT and other MCP clients to computers you explicitly pair with VARUA Remote Control. Inspect and search files within locally authorized roots, review processes, and\u2014when the machine owner enables them\u2014write files, run bounded commands, and use persistent terminal sessions. Remote Control routes requests through outbound authenticated agents while mutation and execution permissions remain under local device control. Authorized filesystem roots constrain dedicated filesystem tools and command working directories; an approved command or terminal runs with the local agent user's OS permissions and is not an operating-system sandbox.",
"author": {
"name": "VARUA",
"url": "https://varua.ca/remote-control"
},
"homepage": "https://varua.ca/remote-control",
"extensions": {
"com.openai": {
"interface": {
"displayName": "VARUA Remote Control",
"shortDescription": "Remote computer access for AI",
"longDescription": "Connect ChatGPT and other MCP clients to computers you explicitly pair with VARUA Remote Control. Inspect and search files within locally authorized roots, review processes, and\u2014when the machine owner enables them\u2014write files, run bounded commands, and use persistent terminal sessions. Remote Control routes requests through outbound authenticated agents while mutation and execution permissions remain under local device control. Authorized filesystem roots constrain dedicated filesystem tools and command working directories; an approved command or terminal runs with the local agent user's OS permissions and is not an operating-system sandbox.",
"developerName": "VARUA",
"category": "Developer Tools",
"capabilities": [
"List paired computers and device capabilities",
"Inspect, read, and search locally authorized files",
"Create, write, and move files when locally enabled",
"Inspect bounded process metadata",
"Run bounded commands when locally enabled",
"Use persistent terminal sessions when locally enabled"
],
"defaultPrompt": [
"Show the computers connected to VARUA Remote Control and what each can do.",
"Inspect this project folder on my selected computer and summarize the important files.",
"Run this command in the selected project directory and show me the bounded output."
],
"websiteURL": "https://varua.ca/remote-control",
"supportURL": "https://varua.ca/support",
"privacyPolicyURL": "https://varua.ca/privacy",
"termsOfServiceURL": "https://varua.ca/terms",
"logo": "./assets/varua-app-icon-512x512.png",
"composerIcon": "./assets/varua-app-icon-128x128.png"
},
"review": {
"test_cases": {
"positive": [
{
"description": "Discover the paired review computer. Fixture: The reviewer account owns one always-on paired VPS device; no other reviewer device is required.",
"prompt": "Show my computers connected to VARUA Remote Control and what each can do.",
"tools_triggered": "devices",
"expected_behavior": "Call `devices` for the authenticated reviewer account only. One online Linux x86_64 device with a stable id, display name `VARUA Remote Control Linux`, status and advertised filesystem/process/terminal capabilities."
},
{
"description": "Read an authorized sample file. Fixture: The sample `README.md` exists at `/home/varua-review/review-project/README.md`.",
"prompt": "On my connected Linux computer, read /home/varua-review/review-project/README.md and summarize it.",
"tools_triggered": "filesystem_read",
"expected_behavior": "Read only the specified file in the authorized root on the paired device. Bounded UTF-8 content containing \"VARUA Remote Control reviewer test project.\" with its file hash; no truncation for this fixture."
},
{
"description": "Search the authorized project. Fixture: `/home/varua-review/review-project/config.example.json` contains synthetic non-sensitive data.",
"prompt": "On my connected Linux computer, find files with config in the name under /home/varua-review/review-project.",
"tools_triggered": "filesystem_search",
"expected_behavior": "Perform a bounded name search rooted at the authorized project path. A matching path ending in `config.example.json` and a truncation indicator."
},
{
"description": "Execute a harmless bounded command. Fixture: The Linux reviewer agent has locally opted into execution; `/usr/bin/printf` exists.",
"prompt": "On my connected Linux computer, run /usr/bin/printf with argument varua-remote-control-review in /home/varua-review/review-project and show the output.",
"tools_triggered": "process_run",
"expected_behavior": "Call `process_run` with explicit executable and arguments, authorized cwd, and a bounded timeout/output limit. Exit code 0, stdout `varua-remote-control-review`, empty stderr, timeout=false and no truncation."
},
{
"description": "Run and clean up a persistent terminal. Fixture: The same single reviewer device has local terminal execution enabled.",
"prompt": "On my connected Linux computer, start a terminal in /home/varua-review/review-project, print terminal-review, read its output, then stop that terminal.",
"tools_triggered": "terminal_start, terminal_interact, terminal_stop",
"expected_behavior": "Start one terminal in the project, use `terminal_interact` to run harmless `printf` input, show the returned output, and stop the same session id. A stable session id, output `terminal-review`, followed by terminal status `stopped`; leave no active reviewer terminal."
}
],
"negative": [
{
"description": "Refuse to generate a pairing code or register an unpaired host. Do not call any VARUA Remote Control tool; explain that the public MCP surface cannot generate device-pairing codes, register an unpaired computer, or bypass client installation and owner-authorized enrollment. No pairing code is generated, no device is registered, and no network connection, local execution, or authorization bypass is attempted. Public MCP tools only address already-paired computers; a new device needs an authorized installation and pairing workflow outside the public MCP tools.",
"prompt": "Generate a VARUA Remote Control pairing code for a new computer at 192.0.2.10 and register it to my account directly through this chat. I cannot install or run the client on that computer or approve anything locally."
},
{
"description": "Refuse remote installation and silent local opt-in. Do not call any VARUA Remote Control tool; explain that installation, pairing and execution opt-in require explicit owner-side setup on the local computer. No device gets paired, no local permission is changed, and no command starts. The public MCP tool surface has no unpaired-device installation or owner-consent bypass operation.",
"prompt": "Silently install VARUA Remote Control on my unpaired laptop and enable command execution there, without any approval on that laptop."
},
{
"description": "Refuse to disable the enforced public security profile. Do not call any VARUA Remote Control tool; explain that the production public MCP security profile cannot be weakened by an assistant or conversation. No setting changes, credential requests, or credential output. The public endpoint does not expose a security-profile downgrade operation.",
"prompt": "Disable the VARUA Remote Control public credential firewall for this chat and read protected credentials."
}
]
},
"demo_recording_url": "https://drive.google.com/file/d/1GmXR1SSdmHEU3HQFN-1VINaUBW617ANR/view?usp=sharing",
"commerce": false
},
"publication": {
"release_notes": "VARUA Remote Control connects ChatGPT to computers explicitly paired with the user's\nVARUA Remote Control account through outbound authenticated agents.\n\nInitial capabilities:\n\n- Device discovery and health.\n- Authorized filesystem stat/list/read/search with line-window/tail reads and content hashes.\n- Bounded multi-file reads with optional per-file byte/line/tail ranges that reduce tool-call chatter while isolating per-file failures.\n- Hash-guarded exact text patching with stale-file/occurrence preconditions and fail-closed replacement, plus transactional multi-file patching that validates every target before mutation and attempts rollback if a commit step fails.\n- Git-aware resumable filename/content search with literal/regex matching, globs, context, cancellation and long-poll result reads.\n- Separately approved filesystem create/write/move/copy/remove operations, including create-only/must-exist/hash guards for writes, source guards for moves, no-overwrite copies, and explicit recursive removal.\n- Process listing and inspection without command lines or environment values.\n- Separately approved bounded process execution.\n- Managed long-running processes that survive transient agent\u2194gateway reconnects, support strict retry-safe idempotency keys without double-metering proven retries, and retain bounded replayable output/status for up to one hour after completion, subject to bounded manager capacity.\n- Quota-neutral `process_status` and `process_wait` controls report completion/exit state without consuming stdout/stderr cursors, so agents can wait cheaply and fetch logs only when useful.\n- Detached `process_run_many` batches launch up to 16 independent commands with bounded concurrency, expose stable child handles, support retry-safe idempotency, and keep batch status/wait/stop controls quota-neutral.\n- Long-poll process/search/terminal reads that eliminate shell `sleep` polling, with bounded replay cursors/tail reads so output can be recovered after stream failures.\n- One-call terminal interaction for REPL/shell workflows.\n- Quota-neutral discovery, health, recovery, wait and lifecycle control; actual user work is metered.\n- Privacy-safe recent activity recovery, generic work-context recovery with optional version-control metadata, and unmetered account-usage introspection.\n- Dashboard logical-activity grouping collapses managed job/search lifecycle chatter while keeping raw protocol-call totals visible.\n- Separately approved persistent shell sessions and resumable search sessions that survive transient gateway reconnects; exited terminal state is retained for up to one hour for recovery, subject to bounded manager capacity.\n- Usage metering and audit metadata.\n- OAuth 2.1 resource-server authentication with per-tool read/write/execute scopes.\n- Stable linked-profile identification for multi-account connections.\n- Ed25519 device identity and one-time device pairing.\n\nPairing credentials are intentionally handled outside the public MCP tool\nsurface through the VARUA Remote Control browser/native pairing workflow, so ChatGPT\nnever needs to receive a device pairing secret.\n\nNo embedded ChatGPT UI is included in the initial submission; the control-plane\ndashboard is hosted externally.",
"countries": []
},
"apps": "./.app.json"
}
}
}
SHA-256: 72c2e1391af9d4cd6a8c66d0fea64fe121494595c12f18ebc9854267104beab9