logicaflow Tools for your workflow

LOGICARELAY · VERSION 0.2.1

Your browser session.
Your AI workflow.

Connect LogicaRelay to your AI client, choose a website and put its session to work. This guide walks through sharing, syncing and controlling access.

1. Install from your browser's store

After installing, pin LogicaRelay to your browser toolbar.

2. Connect your AI client

LogicaRelay uses a relay running on your computer. Once it is running, open Settings & AI in the extension and choose Link for your supported client. Restart that client's MCP connection if prompted.

For GitHub Copilot or a client that needs a configuration file, use Manual relay and MCP configuration below. You'll use your own AI subscription or model access.

3. Share a website

  1. Sign into the website in your browser as usual.
  2. Open LogicaRelay and check the Active browser tab.
  3. Choose Share Session and approve access to that site.
  4. Check that the site appears under Connected websites.

Share only accounts and websites you're allowed to use. Browser profile transfer, when included in your plan, needs separate consent for each site under Advanced.

4. Give your AI a task

Ask your assistant to use LogicaRelay and name the shared website:

Use my shared session for example.com with LogicaRelay. Read the dashboard and summarize today's alerts.

On Free, you can ask your assistant to export the shared session for a local headless browser workflow (such as Playwright). The exported storageState file is saved to private .exports storage with restricted permissions and remains available until you Disconnect the site or pause with the Kill Switch. Standard includes built-in page-reading and browser-action tools. Your AI client controls what it sends to its model provider.

5. Sync or pause access

Use Sync beside a connected website to refresh its session, or Sync All to AI for all selected sites. If a site asks you to sign in again, complete the login in your browser and sync before retrying.

In Settings & AI, the Kill Switch pauses new relay operations. Choose Resume Access when you're ready to continue. Pausing does not revoke a website login or recall previously exported files.

Manual relay and MCP configuration

1. Install and start the local relay

Extract the downloaded local-relay archive (logicarelay-local-0.2.1.zip) to a permanent folder. With Node.js 26 or newer installed, open your terminal in that folder and install runtime dependencies:

npm ci --omit=dev

Start the local relay daemon:

node start-relay.cjs

The relay starts on loopback (http://127.0.0.1:38173). The relay can use installed Google Chrome on macOS. If no supported browser is detected, install Playwright Chromium:

npx playwright install chromium

2. Load the Chrome extension

Extract the separate Chrome extension ZIP. Open chrome://extensions, enable Developer mode and choose Load unpacked. Select the extracted folder containing manifest.json. The relay archive is a different package and cannot be loaded as an extension.

3. Connect your MCP client

For JSON-based MCP clients, use your actual absolute paths in place of these examples:

{
  "mcpServers": {
    "LogicaRelay": {
      "command": "/absolute/path/to/node",
      "args": ["/absolute/path/to/relay/mcp/server.cjs"]
    }
  }
        }

Your client's MCP connection starts the relay. To run it without the client, keep this command open in the extracted relay folder:

node start-relay.cjs

Codex: use the extension's Link button or run the command below in the relay folder, then restart the client. Codex uses TOML; do not paste the JSON example into its configuration.

node mcp/server.cjs --install-codex

GitHub Copilot in VS Code: run the command below in the relay folder, then restart the MCP server in VS Code. The server appears as LogicaRelay.

node mcp/server.cjs --install-vscode

Client support varies by app and workspace. ChatGPT web/mobile cannot start this local stdio server. Update the relay and extension together, and stop the old relay before switching versions.

4. Share a selected site

  1. Sign into a website normally in Chrome.
  2. Open the extension, connect it to the local relay and choose Share Session with AI.
  3. Grant access to that website. The relay receives and encrypts its session on your computer.
  4. On Free, ask your client to call list_sessions, then export_playwright_storage_state for the exact shared domain. The plaintext storageState file is saved to private .exports storage with restricted permissions and deleted on Disconnect or Kill Switch pause.
  5. Use the returned file with compatible headless browsers (such as Playwright). Start with a small read-only task.

5. Use a Free export with Playwright

Use the exported path in a local script. Replace the URL with the site you selected and are authorized to access:

const { chromium } = require('playwright');
const browser = await chromium.launch();
try {
  const context = await browser.newContext({
    storageState: '/absolute/path/from-the-export.json'
  });
  const page = await context.newPage();
  await page.goto('https://your-authorized-site.example');
  console.log(await page.title());
} finally {
  await browser.close();
}

Wrap this example in an async function in a CommonJS script. Loading a session file does not prove the site accepted the login. If you encounter a sign-in or verification page, complete it yourself in Chrome, sync again and retry.

Standard license

Paid capabilities use a Lemon Squeezy license key entered in the extension's plan panel. Standard adds built-in browser tools, cookie-change sync, keepalive, unlimited sites and optional browser profile transfer. This advanced choice has a separate per-site consent page. See pricing for current availability; the Free demo does not show a paid activation or a payment transaction.

Control and cleanup

Pause relay access with the Kill Switch. This does not revoke website logins or recall exported files. Disconnecting a site stops tracking but can leave earlier relay files and exports. Delete those local files or use the relay's purge control when you no longer need them; copies held by your scripts or backups remain under your control.

Need help?

session_status and session_sync_help are available on Free for diagnostics. Contact support@logicaflow.dev with your browser, operating system and a description of the issue. Do not send cookies, passwords, license keys or session exports.