Use Grok Bot with Customaise.

Give Grok Bot named tools for the websites you use. Customaise runs them in Chrome on the Bot’s cloud computer, using the accounts you sign in to there.

Collect a catalogue with Grok Bot.

An illustrated video about Grok Bot creating reusable browser tools with Customaise: collect a fictional shop’s catalogue across two pages, then ask for a human-approved export. Install the extension and run the CLI on the Bot’s own computer. Web scraping is one example; the same approach works for dashboards, research and daily admin.

Watch the Grok Bot video on YouTube. Remote approvals from your phone require Power User and an agent-operated browser.

Install it on the Bot’s computer.

Install Customaise in Chrome on Grok Bot’s cloud computer. Run the CLI in that computer’s terminal. Your laptop’s tabs and sign-ins are separate. You need Grok Bot access, Node.js/npm, Customaise sign-in and Agent Bridge enabled.

Connect Grok Bot to Customaise.

  1. Open the Bot’s computer

    Start with a working Grok Bot account and open Agent Computer from a conversation. All installation steps below happen on that cloud computer. Installing Customaise on your laptop alone does not connect the Bot’s Chrome.

  2. Install Customaise in that Chrome

    Open the Chrome Web Store on the Bot’s computer and install Customaise. In chrome://extensions, open its Details and turn on Allow user scripts.

  3. Sign in and turn on Agent Bridge

    Open Customaise and sign in with Google. Take over the computer yourself for passwords, two-factor authentication or a site’s human verification. In Customaise → Settings → MCP & Terminal, enable Agent Bridge. Sign in to any source website in this same Chrome profile.

  4. Connect the terminal

    Ask the Bot to run the commands below in its own terminal. Node.js and npm must be available. doctor should report a connected extension and a signed-in account; resolve either issue before continuing. init writes a project primer for the Bot to read.

  5. Review a script, then enable it

    Choose an AgentScript from the Marketplace or ask the Bot to build one for your task. Review its source, matching websites and tool permissions. Shared scripts arrive disabled: enable the reviewed script in Customaise, then reload its matching website. A UserScript adds controls for you; an AgentScript exposes tools for the Bot.

  6. Discover, run and check

    List tabs to find the current tab ID, then discover the tools on that tab. Read the returned schema before calling a tool. Start with a read-only action, check the result against the page and save useful output under /workspace. Rediscover tab IDs after a restart.

mkdir -p /workspace/customaise
cd /workspace/customaise
npx -y -p @customaise/mcp customaise doctor
npx -y -p @customaise/mcp customaise init
npx -y -p @customaise/mcp customaise tabs

Setup message for your Bot

Set up Customaise in Chrome on your own Grok Bot computer, using /workspace/customaise for project files. Install the CLI on that same computer; this does not connect to Chrome on my personal computer.

1. Install the current Customaise Chrome Web Store release. Check Allow user scripts in its extension Details. Ask me to take over for Google sign-in and any protected browser permissions, then enable Agent Bridge in Customaise Settings → MCP & Terminal. Stop and report the exact issue if the store, a site or a policy blocks access.
2. Check Node.js 20 or newer and npm, installing a supported Node.js LTS if needed. Install the current published CLI with `npm install -g @customaise/mcp@latest` and confirm `customaise --version`. If the global directory is not writable, use `npx -y -p @customaise/mcp@latest customaise` for the remaining commands. Do not change system permissions or expose the localhost bridge over the network.
3. Create /workspace/customaise if needed and work there. Run `customaise doctor`. Continue only when the extension is connected, signed in and allowed to run scripts. Run `customaise init`, preserving existing instructions, then read the generated primer and `customaise resource agentscript-conventions`. List tabs and scripts, using their real IDs.
4. Help me choose and review an AgentScript for one read-only task. After I enable it, reload its matching page, discover its tool schemas, run one tool and show me the source-linked result. Do not guess tool names or arguments. Wait for requested approvals; do not approve your own actions or retry a denied or unanswered call.

For a script that uses paid Script Decisions, first read `customaise resource script-decisions`. Explain the Power User, saved-key, device and per-script setup; I control those in Customaise. Do not ask for keys in chat or try to set protected permissions through the bridge.

Find and run your first tool.

Discover tabs, then run customaise tools --tab with the returned tab ID. Read the tool schema before calling it. Check the result against the page. For remote approval with Power User, enable Remote Approvals under Account → Control Your Data, then mark the Bot’s browser as agent-operated from Account → Your Devices on a device you control, and verify a Prompt-gated call waits for you.

Build a watchlist from your subscriptions.

One example, not the only use case: the YouTube Deep Research AgentScript provides subscription-feed and transcript tools. Ask Grok for a source-linked shortlist, with unavailable captions and partial coverage reported honestly.

Use the YouTube Deep Research AgentScript in your Chrome to prepare a watchlist from my subscriptions. This is a one-time test.

Ask for my interests, lookback window and viewing budget first. Discover the current YouTube tab and tool schemas. Use yt_get_subscription_feed for subscriptions, not recommendations. Shortlist at most five uploads, then use yt_get_transcript where captions are available.

Return Watch / Skim / Could not assess, with source links, verified timestamp links and a reason for each choice. State how many uploads and transcripts you actually reviewed and whether coverage was incomplete. Do not invent missing captions or infer a video’s content from its title alone.

Save the report and a processing ledger under /workspace/customaise/youtube-briefing. Leave YouTube likes, subscriptions, comments and other account settings unchanged. Do not schedule anything until I have checked this first result.

Make it repeatable before you schedule it.

Save reports and a processing ledger under /workspace/customaise/youtube-briefing. Keep discovered, analysed and delivered items distinct. Check duplicate handling, unavailable captions and browser restarts. Grok Bot owns the schedule and reasoning; Customaise supplies the browser tools. A working first run is not proof of a reliable multi-day routine.

Troubleshooting

For a disconnected extension, check the same computer, sign-in and Agent Bridge. For missing tools, enable a matching AgentScript and reload its page. Take over for sign-in and human verification. Wait for requested approval and do not retry denied calls to get past them. Check doctor for usage limits.

Grok Bot setup questions

Can Grok Bot use Customaise for web scraping and browser automation?

Yes. An AgentScript can expose tools to collect a catalogue, read a dashboard, research a site or update a record. Grok Bot calls those tools through the Customaise CLI on its own computer. Each site needs a suitable script, access in that Chrome profile and your permission. The catalogue workflow in the video and this guide’s YouTube briefing are examples, not the only use cases.

Does this connect Grok Bot to Chrome on my laptop?

No. This setup installs Customaise and its CLI on the Bot’s cloud computer. The extension uses that computer’s Chrome profile and the accounts you sign in to there. Your laptop’s tabs and website sessions stay separate.

Do I need an xAI API key or an MCP configuration?

Not for this setup. Grok Bot uses its terminal to run the Customaise CLI. The CLI and MCP share the same local bridge, but this guide does not require a native Grok Bot MCP client or an xAI API key. You do need Grok Bot access, Customaise sign-in and Agent Bridge enabled.

Where do I approve the Bot’s actions?

Calls follow your Customaise permission mode and each tool’s policy. Remote Approvals is a Power User feature: enable it in Account → Control Your Data, then mark the Bot’s browser as agent-operated under Your Devices from another device you control. Verify that a Prompt-gated call waits for you there. On Free, take over the Bot’s computer to approve locally. Do not switch to Full Access simply to clear a waiting approval.

Can I schedule the workflow?

Grok Bot owns the schedule; Customaise provides the browser tools. Check a one-time result first, then repeat the task to check duplicate handling and incomplete data. Only then ask Grok Bot for a routine with an explicit timezone, inputs, output destination and failure behavior. A signed-out site, disconnected bridge or exhausted allowance must be reported.

Can an AgentScript use Jev or Decisions API for the Bot?

Yes, through the Power User Script Decisions. Save a separate provider key on the Customaise account page, enable Allow Script Decisions for the Bot’s device, and choose the provider in that script’s Quick Actions. The script needs @grant CM_decisions and valid @decisions metadata. Matching requests run automatically; WebMCP tool approvals still apply separately. Provider charges and budgets are separate from Grok Bot usage and Customaise tokens. The Bot can read customaise resource script-decisions for authoring guidance.

Which usage limits apply?

Grok Bot usage and Customaise allowances are separate. The CLI shares Customaise’s bridge allowance with MCP; doctor reports your current connection and quota. Customaise’s own AI features may also use tokens. See Pricing for the current plans rather than assuming a scheduled Bot has unlimited access.

Is the YouTube example a ready-made daily Bot?

It is a workflow you can build with the existing YouTube Deep Research AgentScript. The script provides the tools; your Bot provides the selection criteria and report. Setup work is not proof of a reliable multi-day routine. Check the first result and repeat runs before relying on a schedule.

References: Grok Bot overview, Computer and apps, Skills and routines.