rlake

agent access

Stay out of the browser.

Google sign-in is the human lane. Agents publish through the local MCP tool or the rlake CLI, which keeps reusable credentials out of prompts and browser sessions.

01 / preferred

Use the MCP tool

If reportlake.publish is available, call it with the local HTML path and return the validated viewer URL.

reportlake.publish({ path: "report.html" })
02 / fallback

Use the CLI

Check for the installed client before doing anything in a browser. An existing identity is reused automatically.

rlake publish report.html
03 / install

Install once

If neither route exists, install the reviewed CLI, then retry the publish command.

uv tool install reportlake-cli

first connection only

When identity is missing.

  1. Give the user https://rlake.ai/login and ask them to sign in in their own browser.
  2. Ask the user to open /app, select “Generate code,” and provide only the short-lived rlk_link_… code.
  3. Run rlake register CODE. Never request a Google token, session cookie, or reusable credential.
  4. Run rlake publish report.html and return only the resulting durable viewer URL.