@mcpbridgeapp/cli 0.0.0-stage → 0.1.1

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Syed Zeeshan Ali
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -1,3 +1,346 @@
-# Temporary Holding Version
+<div align="center">
 
-This version is a temporary placeholder for this package. An operational version to replace this has been submitted for review and is awaiting a staged release.
+# mcpbridgeapp
+
+**Let any AI app hand work to the AI tools on your own computer.**
+
+[![npm](https://img.shields.io/npm/v/@mcpbridgeapp/cli?color=4f6bed)](https://www.npmjs.com/package/@mcpbridgeapp/cli)
+[![CI](https://github.com/szeeshan896/mcpbridgeapp/actions/workflows/ci.yml/badge.svg)](https://github.com/szeeshan896/mcpbridgeapp/actions/workflows/ci.yml)
+[![License: MIT](https://img.shields.io/badge/license-MIT-green)](LICENSE)
+
+[Quick start](#quick-start) · [How it works](#how-it-works) · [Control panel](#the-control-panel) · [Agents](#agents-you-can-use) · [Safety](#safety) · [Reference](#reference)
+
+</div>
+
+<img src="https://raw.githubusercontent.com/szeeshan896/mcpbridgeapp/main/docs/images/how-it-works.png" alt="AI apps such as claude.ai, ChatGPT and Claude Code send a task to the mcpbridge.app relay, which forwards it to your computer, where mcpbridgeapp runs Claude Code, Codex, Grok, Antigravity, DeepSeek, NVIDIA or Ollama and sends the answer back" width="100%">
+
+You are chatting with Claude on your phone. Your laptop at home has Codex, Claude Code and
+Grok signed in, each on a plan you already pay for. With mcpbridgeapp you can say:
+
+> Ask codex through mcpbridgeapp to review `payment.ts` in my shop project.
+
+Claude passes the task to your laptop. Codex runs there, reads the real files, and its
+review comes back into the same chat. **One message, work done.**
+
+- **Use the plans you already pay for.** mcpbridgeapp runs the AI command-line tools that are
+  signed in on your computer. No new subscription and no API key needed for them.
+- **No keys on any server.** Logins and API keys stay on your computer. The relay only
+  passes messages along, so a breach there leaks no AI credentials.
+- **Works from anywhere.** claude.ai on the web, the desktop app and your phone, ChatGPT,
+  Claude Code, Cursor, or any app that speaks [MCP](https://modelcontextprotocol.io).
+- **A second opinion on tap.** Have one AI check another's work, or pick the model best at
+  the task: a free NVIDIA coding model, DeepSeek, a local Ollama model that never touches
+  the internet.
+- **No terminal needed.** A control panel in your browser adds agents, keys and the
+  connection, and tests each agent with one click.
+
+## Quick start
+
+You need **[Node.js 22 or newer](https://nodejs.org)** on the computer where your AI
+tools are installed. Check with `node --version`.
+
+### A. From claude.ai, your phone, ChatGPT and other apps
+
+1. **Create an account** at **[mcpbridge.app](https://mcpbridge.app)**. On the dashboard,
+   generate an **agent token**.
+2. **Start the control panel** on your computer:
+
+   ```bash
+   npx -y @mcpbridgeapp/cli ui
+   ```
+
+   It opens in your browser. Paste the agent token under **Relay connection**, then press
+   **Save & connect**. The panel turns **Online**. Keep that window open (you can minimise
+   it); while it runs, your agents are reachable.
+3. **Add the connector in claude.ai.** Open **Customize → Connectors → Add custom
+   connector**, name it `mcpbridgeapp`, and use `https://mcpbridge.app/mcp` as the URL. Press
+   **Connect**, sign in, and press **Allow**. Nothing to paste. The same connector then
+   works in the Claude desktop app and on your phone.
+4. **Ask.** In any chat, switch the mcpbridgeapp connector on (**+ → Connectors**) and say
+   *"list my mcpbridgeapp agents"*, then *"ask codex to …"*.
+
+The dashboard shows the exact setup lines for Claude Code, Claude Desktop and Cursor, with
+your own address filled in.
+
+### B. Only Claude Code, on the same computer
+
+You don't need an account or the relay. Claude Code starts mcpbridgeapp itself:
+
+```bash
+# macOS / Linux
+claude mcp add -s user mcpbridgeapp -- npx -y @mcpbridgeapp/cli
+
+# Windows (PowerShell or cmd)
+claude mcp add -s user mcpbridgeapp -- cmd /c npx -y @mcpbridgeapp/cli
+```
+
+Then, in Claude Code: *"ask gemini through mcpbridgeapp to review the caching layer in this
+module"*. `-s user` makes it available in every folder, not just the current one.
+
+### Install it for good (optional)
+
+`npx` fetches the latest version each time. To install once instead:
+
+```bash
+npm install -g @mcpbridgeapp/cli
+mcpbridgeapp ui              # the control panel
+mcpbridgeapp --agents        # which agents are ready on this computer
+```
+
+## How it works
+
+<img src="https://raw.githubusercontent.com/szeeshan896/mcpbridgeapp/main/docs/images/flow.png" alt="Sequence: claude.ai calls ask_agent on the relay; the relay forwards it to mcpbridgeapp on your computer; mcpbridgeapp runs codex in your folder; the answer is checked and returned the same way" width="100%">
+
+1. Your AI app calls mcpbridgeapp's `ask_agent` tool. It names an agent (say `codex`), writes a
+   self-contained task, and can pass a folder on your computer.
+2. The relay at mcpbridge.app forwards the call over a WebSocket that **your computer**
+   opened. Nothing on your computer listens for connections, so no ports to open and no
+   firewall rules.
+3. mcpbridgeapp looks the agent up in **your** configuration and runs it, e.g.
+   `codex exec "<task>"` in that folder. The task is passed as a single argument with no
+   shell involved, so text in a prompt can never become a command.
+4. The agent works the way it always does, signed in as you.
+5. mcpbridgeapp **checks the answer** before calling it a success. An agent that exits normally
+   but only says *"I couldn't read the files"*, or stops after *"I'll start by reading
+   payment.ts"*, comes back as a failure that says why. A usage limit or an expired
+   sign-in is remembered, so the next call is told straight away instead of waiting.
+6. The answer travels back the same way into your chat.
+
+Close the laptop and the dashboard shows **offline**. That is the point, not a
+limitation: the work happens where your logins are, which is why the server needs none.
+
+## The control panel
+
+```bash
+npx -y @mcpbridgeapp/cli ui        # or: mcpbridgeapp ui
+```
+
+<img src="https://raw.githubusercontent.com/szeeshan896/mcpbridgeapp/main/docs/images/control-panel.png" alt="The mcpbridgeapp control panel: relay connection Online as my-laptop, and a list of agents (antigravity, claude, codex, deepseek, gemini, grok, an NVIDIA model, ollama), each ready, with Test, Edit and Customise buttons" width="100%">
+
+A page on your own computer (`http://127.0.0.1:8809`) that does everything this README does
+with commands:
+
+- **Connect to the relay.** Paste the agent token once. The page keeps the computer online
+  while it is open, reconnects by itself the next time you open it, and sends a newly added
+  agent to the relay straight away.
+- **Add an agent from a preset.** NVIDIA (free tier), DeepSeek, Grok, OpenRouter, Groq,
+  Mistral, Ollama, or any OpenAI-compatible service or command-line tool. Paste the key,
+  press **List models**, pick one and save. To keep several models from one provider, tick
+  them under **Add several models at once**. Each becomes its own agent, named after its
+  model (`nvidia-qwen3-coder-480b`).
+- **Test** any agent with a one-word prompt and see the answer or the exact error.
+- **Allow edits or commands** per agent (see [Safety](#safety)).
+
+**On Windows**, if you cloned the repository, double-click `start-ui.cmd`. Put a shortcut to
+it on your desktop to start mcpbridgeapp with one click.
+
+Keys and the agent token are saved in `~/.config/mcpbridge/secrets.json` on your computer.
+They are never written to `config.json` and never sent to the relay. The page answers only on
+127.0.0.1, and only to the browser that opened the link it printed.
+
+## The dashboard
+
+<img src="https://raw.githubusercontent.com/szeeshan896/mcpbridgeapp/main/docs/images/dashboard.png" alt="The mcpbridge.app dashboard: your machine is Online as my-laptop, with each agent listed as available and what it may do" width="100%">
+
+[mcpbridge.app](https://mcpbridge.app) shows whether your computer is online and which agents
+it offers. It is also where you manage tokens, turn on 2-step verification, and see and
+disconnect the apps you have allowed.
+
+## Agents you can use
+
+| Agent | What it is | Needs |
+|---|---|---|
+| `claude` | Claude Code | `claude` installed and signed in |
+| `codex` | OpenAI Codex CLI | `codex` installed and signed in |
+| `grok` | Grok Build CLI | `grok` installed and signed in |
+| `antigravity` | Google's Antigravity CLI (`agy`), Gemini models | `agy` installed and signed in |
+| `gemini` | Gemini CLI | `gemini` installed and signed in |
+| `ollama` | a model running locally in [Ollama](https://ollama.com) | Ollama and one pulled model. No account, works offline |
+| anything else | DeepSeek, NVIDIA, xAI API, OpenRouter, Groq, Mistral, LM Studio, … | an API key, added in the control panel |
+
+The first six are built in: install the tool, sign in once in a terminal, and it shows up.
+Anything not installed is listed as unavailable, never silently broken. Check from a
+terminal:
+
+```bash
+npx -y @mcpbridgeapp/cli --agents
+```
+
+```
+✓ claude     claude found on PATH
+✓ codex      codex found on PATH
+✗ gemini     gemini is not on PATH — install it or fix the command
+✓ ollama     Ollama at http://127.0.0.1:11434, using qwen3:latest
+```
+
+Using these tools removes the key, not the quota: each one still spends its own plan's
+limits.
+
+## Tools your AI app gets
+
+| Tool | What it does |
+|---|---|
+| `list_agents` | which agents exist, whether each is ready, what each may do, and whether your computer is online |
+| `ask_agent` | give one agent a task, wait, get the answer |
+| `start_task` | the same, but returns an id at once, for work longer than the app will wait |
+| `get_task` | check on a started task: queued, running (with the output so far), or finished |
+
+The agent you delegate to starts fresh. It cannot see your chat, so the calling AI writes a
+complete task and passes `workingDirectory` when it is about code.
+
+Every answer says honestly how it went:
+
+- **`succeeded`** is true only if the agent actually did the work, not just because its
+  program exited normally.
+- **`status`** in `list_agents` is `ready`, `unavailable`, `quota-exhausted`,
+  `sign-in-failed` or `directory-not-trusted`, with the last error and, when the agent
+  named one, when to retry. A limit is remembered for an hour, a failed sign-in for six,
+  and any success clears it.
+- **`writesFiles`** and **`runsCommands`** say what the agent is allowed to do, so the
+  calling AI hands file-changing work only to an agent that can do it.
+- **`diagnostics`** is short and to the point. `notes` carries what you should know about a
+  success, such as tokens spent or an answer cut short.
+- On a **timeout**, whatever the agent had written so far comes back, marked incomplete.
+- **Tasks queue.** Two delegations run at once by default. The rest wait their turn, and
+  `get_task` says where they are in the queue.
+
+## Safety
+
+mcpbridgeapp runs programs on your computer for apps on the internet, so it is careful by
+default.
+
+**Agents are read-only until you allow more.** Every agent starts unable to change files
+or run commands. In the control panel, press **Edit** (or **Customise** for a built-in)
+and tick what it may do. mcpbridgeapp turns that into the tool's own flags:
+
+| CLI | Change files | Run commands |
+|---|---|---|
+| claude | `--permission-mode acceptEdits` | `--allowedTools Bash` |
+| codex | `--sandbox workspace-write` (one switch for both; still no network) | same |
+| grok | `--always-approve` (all or nothing) | same |
+| gemini | `--approval-mode auto_edit` | `--approval-mode yolo` |
+| agy (Antigravity) | `--mode accept-edits` | `--dangerously-skip-permissions` (allows edits too) |
+
+Allow only what you are happy for every app connected to your account to do on your
+computer. Some tools can't even read files without approval when no one is there to give
+it: Grok Build, for one, reads with shell commands. Such an agent needs **Change files**
+ticked before it can review code.
+
+**Commands come only from your configuration.** A tool call can name an agent, never a
+command. The prompt reaches the program as one argument with no shell, so `;`, `&&` and
+backticks in a prompt arrive as plain text. A test checks exactly that.
+
+**The relay holds no AI credentials.** It stores accounts, password hashes and token
+hashes, never an API key or a CLI login. Tokens are shown once. claude.ai and Claude Code
+sign in through OAuth with PKCE, and every app you allow is listed on the dashboard, where
+you can disconnect it. 2-step verification with an authenticator app is available.
+
+**Local servers stay local.** The control panel and the optional HTTP mode listen on
+127.0.0.1 only, and refuse requests from other websites.
+
+## Reference
+
+### Commands
+
+```
+mcpbridgeapp                     MCP server over stdio (what Claude Code starts)
+mcpbridgeapp ui [--port N]       the control panel in your browser
+mcpbridgeapp connect             stay connected to the relay (uses the saved token,
+  [--relay URL --token T]        or pass them here)
+mcpbridgeapp --agents            which agents are ready here
+mcpbridgeapp --ask <agent> "…"   delegate once from the terminal, to test an agent
+mcpbridgeapp --http [port]       one shared HTTP server on 127.0.0.1 (default 8808)
+mcpbridgeapp --example-config    print a starter config
+```
+
+### Configuration
+
+Everything the control panel does is saved in `~/.config/mcpbridge/config.json` (set
+`MCPBRIDGE_CONFIG` to use another file). You can also write it by hand. An entry replaces the
+built-in agent of the same name.
+
+```json
+{
+  "maxConcurrent": 2,
+  "agents": {
+    "codex": {
+      "command": ["codex", "exec", "--skip-git-repo-check", "{prompt}"],
+      "allow": { "edits": true, "commands": true },
+      "timeoutMs": 600000
+    },
+    "deepseek": {
+      "type": "openai",
+      "baseUrl": "https://api.deepseek.com/v1",
+      "model": "<a model id: List models in the control panel shows them>",
+      "apiKeyEnv": "DEEPSEEK_API_KEY"
+    },
+    "local": { "type": "ollama", "model": "qwen3:latest" }
+  }
+}
+```
+
+| Field | Meaning |
+|---|---|
+| `command` | the program and its arguments. `{prompt}` is replaced by the task, as one argument |
+| `promptVia` | `"argv"` (default) or `"stdin"`. Use stdin for long prompts: Windows limits an argument to about 32 KB |
+| `allow` | `{ "edits": true, "commands": true, "trustDirectory": true }`, the same switches as the control panel |
+| `capabilities` | for a CLI mcpbridgeapp doesn't know: declare `{ "writesFiles": true, "runsCommands": true }` yourself |
+| `env` | extra environment variables for that agent |
+| `timeoutMs` | how long one call may run (default 5 minutes) |
+| `type: "openai"` | any service with `POST /v1/chat/completions`: `baseUrl`, `model`, `apiKeyEnv` |
+| `type: "ollama"` | a local Ollama model: `model`, optional `baseUrl` |
+| `maxConcurrent` | how many delegations run at once (default 2) |
+
+`apiKeyEnv` is the **name** of an environment variable, not the key, so a config file can be
+shared without leaking anything. Keys saved in the control panel go to `secrets.json` and are
+loaded into that variable. A variable you export yourself still wins.
+
+### Troubleshooting
+
+| You see | What to do |
+|---|---|
+| Panel or dashboard says **offline** | Start `mcpbridgeapp ui` (or `mcpbridgeapp connect`) and keep its window open |
+| `sign-in-failed`, *"session expired"* | Run that tool once in a terminal and sign in again |
+| `quota-exhausted` | The tool's plan hit its limit. Wait for `retryAt`, or use another agent |
+| Agent times out, or says it *needs permission* | It stopped at an approval prompt. Allow edits or commands for it, or ask only for a reading |
+| Gemini CLI: `IneligibleTierError` | Google withdrew Gemini CLI for personal accounts. Use the built-in `antigravity` agent, same models, same login |
+| `directory-not-trusted` | Tick *Trust the working directory* for that agent, if you trust the folders your apps send it |
+| Codex: *not a git repository* | Point it at a git repository, or add `--skip-git-repo-check` to its command |
+| Claude Code doesn't see the tools | Add it with `-s user`, then restart Claude Code. Check with `claude mcp list` |
+
+**Windows:** npm-installed CLIs are `.cmd` files, which Node can't run without a shell, and a
+prompt must never go through a shell. mcpbridgeapp reads the `.cmd` file and runs the real
+program it points to, so `claude`, `codex` and the rest work as they are.
+
+### Run your own relay
+
+mcpbridge.app is one instance of the relay in [`relay/`](relay/README.md). You can host your
+own: it is one Docker image with a SQLite database, and deploys to Railway, Fly.io or any
+VPS. Accounts use email or phone, a password or Google, with optional 2-step verification.
+
+## Development
+
+```bash
+git clone https://github.com/szeeshan896/mcpbridgeapp.git
+cd mcpbridgeapp
+npm install       # also builds dist/
+npm test          # typecheck and tests
+npm start         # the stdio server, from source
+cd relay && npm install && npm test
+```
+
+```
+src/agents/    running each kind of agent: cli.ts, openai.ts, ollama.ts; judging an
+               answer (outcome.ts); remembered failures (health.ts); permission flags
+               (permissions.ts); Windows .cmd shims (shim.ts)
+src/ui/        the control panel
+src/connect.ts the outbound connection to a relay; src/protocol.ts its messages
+src/tools.ts   the four tools, shared by the local server and the relay path
+src/tasks.ts   background tasks and their queue
+relay/         the hosted relay: accounts, OAuth, tokens, 2FA, dashboard, forwarding
+test/fixtures/ a stand-in agent CLI, so the suite runs on Windows, macOS and Linux
+```
+
+## License
+
+[MIT](LICENSE) © Syed Zeeshan Ali

package/dist/agents/broken.d.ts

@@ -0,0 +1,24 @@
+import { type Agent, type AgentResult } from './types.js';
+/**
+ * Stands in for an agent whose configuration could not be used.
+ *
+ * <p>Without this, one bad entry in the config file threw during startup and took the
+ * whole bridge with it — every other agent included — and over stdio the client saw only
+ * a process that died, with the reason going nowhere a person would look.
+ */
+export declare class BrokenAgent implements Agent {
+    readonly name: string;
+    readonly reason: string;
+    readonly readsFiles = false;
+    readonly writesFiles = false;
+    readonly runsCommands = false;
+    readonly timeoutMs = 0;
+    readonly requires = "a valid configuration";
+    constructor(name: string, reason: string);
+    get description(): string;
+    probe(): Promise<{
+        available: boolean;
+        detail: string;
+    }>;
+    run(): Promise<AgentResult>;
+}

package/dist/agents/broken.js

@@ -0,0 +1,31 @@
+import { failed } from './types.js';
+/**
+ * Stands in for an agent whose configuration could not be used.
+ *
+ * <p>Without this, one bad entry in the config file threw during startup and took the
+ * whole bridge with it — every other agent included — and over stdio the client saw only
+ * a process that died, with the reason going nowhere a person would look.
+ */
+export class BrokenAgent {
+    name;
+    reason;
+    readsFiles = false;
+    writesFiles = false;
+    runsCommands = false;
+    timeoutMs = 0;
+    requires = 'a valid configuration';
+    constructor(name, reason) {
+        this.name = name;
+        this.reason = reason;
+    }
+    get description() {
+        return `misconfigured: ${this.reason}`;
+    }
+    async probe() {
+        return { available: false, detail: `misconfigured: ${this.reason}` };
+    }
+    async run() {
+        return failed(this.name, `agent "${this.name}" is misconfigured: ${this.reason}`);
+    }
+}
+//# sourceMappingURL=broken.js.map

package/dist/agents/broken.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"broken.js","sourceRoot":"","sources":["../../src/agents/broken.ts"],"names":[],"mappings":"AAAA,OAAO,EAAgC,MAAM,EAAE,MAAM,YAAY,CAAC;AAElE;;;;;;GAMG;AACH,MAAM,OAAO,WAAW;IAQX;IACA;IARF,UAAU,GAAG,KAAK,CAAC;IACnB,WAAW,GAAG,KAAK,CAAC;IACpB,YAAY,GAAG,KAAK,CAAC;IACrB,SAAS,GAAG,CAAC,CAAC;IACd,QAAQ,GAAG,uBAAuB,CAAC;IAE5C,YACW,IAAY,EACZ,MAAc;QADd,SAAI,GAAJ,IAAI,CAAQ;QACZ,WAAM,GAAN,MAAM,CAAQ;IACtB,CAAC;IAEJ,IAAI,WAAW;QACb,OAAO,kBAAkB,IAAI,CAAC,MAAM,EAAE,CAAC;IACzC,CAAC;IAED,KAAK,CAAC,KAAK;QACT,OAAO,EAAE,SAAS,EAAE,KAAK,EAAE,MAAM,EAAE,kBAAkB,IAAI,CAAC,MAAM,EAAE,EAAE,CAAC;IACvE,CAAC;IAED,KAAK,CAAC,GAAG;QACP,OAAO,MAAM,CAAC,IAAI,CAAC,IAAI,EAAE,UAAU,IAAI,CAAC,IAAI,uBAAuB,IAAI,CAAC,MAAM,EAAE,CAAC,CAAC;IACpF,CAAC;CACF"}

package/dist/agents/cli.d.ts

@@ -0,0 +1,47 @@
+import type { CliAgentConfig } from '../config.js';
+import { type Permissions } from './permissions.js';
+import { type Agent, type AgentResult, type RunOptions } from './types.js';
+export declare const PROMPT_PLACEHOLDER = "{prompt}";
+/**
+ * An agent that is a command-line tool. The command comes from configuration and the
+ * prompt only ever fills {prompt} or goes down stdin — never through a shell, so nothing
+ * in a prompt can be read as a shell metacharacter.
+ */
+export declare class CliAgent implements Agent {
+    readonly name: string;
+    private readonly config;
+    private readonly maxOutputChars;
+    readonly requires: string;
+    readonly readsFiles = true;
+    readonly permissions: Permissions;
+    constructor(name: string, config: CliAgentConfig, maxOutputChars: number);
+    get writesFiles(): boolean;
+    get runsCommands(): boolean;
+    get timeoutMs(): number;
+    private get promptVia();
+    get description(): string;
+    probe(): Promise<{
+        available: boolean;
+        detail: string;
+    }>;
+    run(prompt: string, options: RunOptions): Promise<AgentResult>;
+    private spawnAgent;
+    private startupAdvice;
+}
+/**
+ * Turns a spawn failure into something the caller can act on. The size limit varies by
+ * platform — roughly 128KB per argument on Linux, about 1MB on macOS, and as little as
+ * 32KB on Windows — so the advice names the setting that removes it rather than a number.
+ */
+export declare function startupAdvice(agent: string, command: string, error: Error & {
+    code?: string;
+}, prompt: string): string;
+/**
+ * A .cmd or .bat can only be run through a shell, and running the prompt through a shell
+ * is exactly what this program must never do: quoting rules for batch files are their own
+ * minefield (see CVE-2024-27980). So such an agent is refused with the fix, rather than
+ * made to work unsafely or left to fail as a bare ENOENT.
+ */
+export declare function needsAShell(resolvedPath: string): boolean;
+export declare function resolveOnPath(executable: string): Promise<string | null>;
+export declare function onPath(executable: string): Promise<boolean>;