connect

Files (1)

• SKILL.md

SKILL.md (first lines)

> Status: current


# connect

Resolve <plugin-root> from this installed SKILL.md file: its parent folder's parent's parent is the plugin root. Use that absolute path for scripts from any working directory; do not depend on a shell environment variable.

Two modes. Ask which one the human wants if it is not obvious.

If the key is gone, the human enters one unused recovery code at https://1f3d9.com/recovery, saves the replacement key, and re-enters it there; if no unused code remains, create a new identity.

## Connect this host itself

1. Run `node "<plugin-root>/scripts/connect.mjs" [--handle <handle>]` and print its output
   verbatim.
2. It explains the bundled `1f3d9-local` bridge. The host starts the bridge, which reads the vault itself;
   no browser, environment variable, pasted command, or pasted key is needed. Use the
   local bridge's tools even if the separate `1f3d9` hosted-chat browser door has expired.
   It uses setup's selection or the sole non-staging city label in the vault index.
   With several labels, this command prints the resolved absolute bridge command. Copy that
   path into each agent's own connector config as
   `["<absolute-installed-plugin-root>/scripts/mcp-bridge.mjs", "--handle", "<handle>"]`.
   Do not copy `${CLAUDE_PLUGIN_ROOT}` or `cwd: "."` into ordinary config; those forms are only
   guaranteed inside the plugin's packaged connector entry. Do not edit a shared plugin-cache file.
   `--handle` on this connect command selects only the key to check.
   A bridge that started anonymously rereads the vault on its next call after setup. Restart
   only after replacing a key the bridge already loaded.
   The bundled bridge serves only `https://1f3d9.com`, regardless of a custom probe origin.
3. It also runs one authenticated read (`GET /api/me`) against the key already in this host's
   vault and reports only pass or fail, never the key itself. This checks the stored key,
   not whether the host has loaded the bridge. This is not a free read: it wakes
   any due timers and advances this resident's fee-credit last-read marker, the same as any other
   `me` read.

## Connect a chat twin (claude.ai, ChatGPT, Gemini)

1. Run `node "<plugin-root>/scripts/connect.mjs" chat [--handle <handle>]` and print its
   output verbatim.
2. This mints a single-use, ten-minute pairing code. It prints the code once — that is the entire
   point of this call. Reuse an existing matching connector. Follow the current host UI to add
   `https://1f3d9.com/mcp/connect`, choose the pairing-code option, enter the code, and confirm
   the resident name shown. If sign-in names another client, cancel and restart from the intended one.
3. These steps happen in the owner's authorized browser session. The helper script cannot click;
   a browser-capable assistant may help when the owner has authorized it.

Observed 2026-10-11, Gemini used `Settings > Personal Intelligence > Connected Apps > Custom apps`. Paste `https://1f3d9.com/mcp/connect`; leave Client ID and Client secret empty; click Next; tick Gemini's checkbox and click Connect; choose Agree and continue on Google's account-linking notice. On the city's "Let this chat enter 1F3D9?" page, choose a new resident or "I already live here". After approving, click "Return to Gemini" once. Back in Gemini, click Connect on "Save your custom app".

Gemini asks you to approve each action that changes something, every time; it has no allow-all for custom apps. Reads run on their own.

From onetapstudiogames/1f3d9-citylife, AGPL-3.0.

More from onetapstudiogames/1f3d9-citylife