← Plugin catalog
Developer Tools

Bridge

亚轩 孙 v1.2.9

Connect your computer to AI

Create a free account to save this plugin.

From the developer

Cost & access

This plugin accesses an existing Bridge account and its existing service entitlement. The separate Bridge website operates metered prepaid service billing. The plugin does not sell digital credits or services, show purchase plans, initiate checkout, provide payment links, collect card details, or promote upgrades. Usage and entitlement information do not prove payment.

Declared limitations

  • Bridge provides no general-purpose cloud computer for arbitrary user code. Explain that execution requires an authorised connected Host or configured repository runner. Do not call execution or provisioning tools, invent a cloud job, or silently substitute the already connected Windows computer when the user explicitly excludes it.
  • Use the synthetic demo file already transferred in this conversation. New Bridge relay files are temporary, normally 24 hours from READY; this is not a permanent backup service. Explain the unsupported guarantee without uploading, exporting, executing commands or fabricating a permanent link. Use existing verified retention evidence where available, distinguish storage expiry from download access expiry, and do not claim that a local copy or a different external storage service is permanent storage provided by Bridge.
  • Purchasing Bridge digital credits is outside the plugin. Explain the limit without Bridge tool invocation, checkout creation, payment link, card-data collection, or simulated credit. Existing-account access is distinct from buying credits.

Not specified in the available declarations: capabilities.

Onboarding example

Show my connected Bridge computers.

View onboarding source →

Sources & dates

Developer declarations; not independently tested. Listing last checked Nov 7, 2026. Package observed Nov 7, 2026.

View package source →

Description

From the marketplace listing

Connect your own Windows or Linux computer through your Bridge account. Find authorized computers, run bounded local commands, inspect actual task results, and transfer temporary files in both directions. Install the official Bridge Host and authorize the same account for your computer and this plugin. Optionally connect GitHub repositories separately in Bridge settings, install the GitHub App for the intended repositories, and explicitly save your selection. GitHub sign-in alone does not grant repository access. Inspecting an authorized repository does not require a project configuration file. Repository execution and publication also require configured workflows, runners and permission checks. GitHub access can be added later or revoked without changing Host pairing or your Bridge account.

Language: English · Automatically detected from descriptions.

Changes

No changes recorded yet. Follow this plugin to keep track of future changes.

First seen Nov 7, 2026. Last seen Nov 7, 2026.

Files & skills

File archives

Plugin package6 files · 1.02 MBBrowse files →
Skill instructions
bridge-connect22.5 KB

View saved version →

---
name: bridge-connect
description: Connect a Bridge Host, run authorised local tasks, inspect evidence or transfer temporary files; use the optional GitHub branch for repository authorisation, project setup, engineering tasks or revocation.
---

# Bridge commercial connection

Use the packaged commercial MCP server at `https://console.yunrou.work/mcp`.
For GitHub authorisation, repository discovery, project onboarding, engineering
execution or revocation, first read [repository setup](references/repositories.md).
This plugin accesses existing accounts; it does not sell credits or initiate
payments. Never provide checkout links, collect card details, or use a Host
command to circumvent that limit. Explain unavailable capabilities honestly.

For a request solely to buy credits or obtain checkout, make Bridge itself act
as an image-generation model, or bypass another owner's permission, explain
that boundary directly without calling any Bridge tool. This includes
`bridge.account_usage` and Host or repository discovery: do not inspect balances
or probe resources merely to explain an unsupported request. Do not offer a
top-up route, upgrade promotion or checkout URL in that response. A separate,
explicit authorised request to inspect usage, or to run a legitimate
image-generation tool on the user's allowed Host, remains supported under the
usual ownership and execution checks.

Bridge does not provide its own general-purpose cloud computer for user code.
If the user explicitly excludes connected Hosts and repository runners, explain
that boundary without starting a task, provisioning a machine, or silently using
an already connected computer. New relay files are temporary, not permanent
backup. A request to retain one forever cannot be fulfilled by another import,
export or regenerated link; explain the actual retention and access deadlines
without claiming a permanent save or changing the file.

## Keep the selected account connection

Before each tool call, inspect that tool's CURRENT eligible linked-account
identifiers when the platform requires an account selector. Preserve the
connection the user chose. Reuse an identifier only when the current tool lists
it as eligible for that same connection. Never substitute a Host ID, GitHub
installation ID, email, nickname, stale identifier or another account. Do not
hard-code connection identifiers. Platform account selectors are separate from
Bridge server arguments; supply one only as declared by the current tool interface.

If the platform returns `link_id must identify an eligible linked account`,
check the current tool metadata and the user's selected connection. This is a
linked-account selection or availability error, not evidence of missing GitHub
grants, repository configuration or Host pairing. Do not change those resources
to fix it, or claim a particular wrong identifier was sent unless the failed
input is actually visible. If the intended connection is now eligible, retry the
failed read once using its current identifier. Otherwise ask the user to select
or reconnect that intended connection; do not switch accounts or keep retrying.
For a possible write, recover its original run before considering any resubmission.

`MCP_CATALOG_TIMEOUT` is a separate repository preset-catalog timeout, not a
linked-account error or proof that repository access was revoked. For basic
repository inspection, call `bridge.get_repository_configuration` directly;
do not add an unnecessary `bridge.repository_tools_status` probe. Inspect that
catalog only when extra preset availability is relevant. Preserve any successful
configuration result, report the timeout separately, and retry that read at most
once if still needed. Never repeat a command or change GitHub permissions merely
to recover a catalog read.

During a demonstration, perform only the requested demo actions and necessary
evidence reads. Do not create unrequested Notion p

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 1 — file references are metadata, not package contents.

Release notes

1.2.9: Require Node.js file-demo readback and explicit PowerShell console UTF-8 when Windows-specific commands are necessary. Distinguish intact file bytes from lossy stdout and retain original receipts during diagnosis. Repository metadata uses a bounded 12-second construction budget, separate from Host execution waiting; ownership, permission checks, cancellation and rate limits remain. The owner-approved recording and its five positive / three negative cases are retained. Host 0.5.1 and App/account identities are unchanged.

Declared in the saved package. Remote tools may change independently.

Package details

Publisher declarations from the archived package. These are separate from our research and the live service's terms.

Declared availability
No country restrictions declaredDeclared regions; live availability may differ.
Getting started skill
./skills/bridge-connect/SKILL.md
Commerce declaration
Does not support commerceThis does not establish whether access is free or paid.
Review scenarios
5 positive · 3 negativeScenario counts, not test results.

Package observed Nov 7, 2026.

Technical details
First seen
Nov 7, 2026 · 06:00 UTC
Last seen
Nov 7, 2026 · 12:00 UTC
Collection status
Collected

plugin_asdk_app_6ad784379bac8191ab45010cef83102e

Download plugin data (JSON)

Plugin details: freshly prepared. Prepared . Refreshed when plugin data changes or after 6 hours. Your account and Follow status are live.