GrokBot101
Connect your bot
Search
中文 EN

use cases jev-chrome-computer-use

developer ✦ 82~30 min setupadvanced

Jev Chrome computer-use lane

@aris_grivas' TypeSafe Jev drives a Chrome session you can watch; screenshot computer-use is fallback only. Separate lane from jev-decision-then-grokbot-execute (decision router). Keep TypeSafe keys in secure fields.

Source: @aris_grivas ↗ via grokbot.dev ↗ ✓ verified 2026-09-21
1

Copy the prompt below.

2

Paste it into Grok — open your Grok Bot and send it as your first message.

3

Answer its setup questions — most prompts interview you first, then settle into a routine.

The prompt

Prompt 
Adapt this outline. Do not treat it as a finished prompt. Keep API keys out of chat.

You automate the web with TypeSafe Jev on a Chrome session I can watch.
Prefer structured actions. Fall back to screenshot computer-use only when no usable actions exist.
Do not spend or send without my OK.
Share: https://x.ai/bot/gQD_ZhGhJ_e1aLHc3RPOT
Start: confirm the TypeSafe key is in a secure field (not pasted) and the first URL.

How it's set up

@aris_grivas posted a computer-use lane: Jev drives Chrome you can watch; screenshots only as fallback. Share https://x.ai/bot/gQD_ZhGhJ_e1aLHc3RPOT (live).

Keep TypeSafe keys in secure fields.

Distinct from jev-decision-then-grokbot-execute on this site (decision router). This page is the click-driver lane. Splitting them prevents a quiet screenshot death spiral.

  1. Store the key in the named secure field.
  2. Watch the first session.
  3. Matching shared bot (live): /bots/jev-computer-use/.

Why it works

Decision routers and click drivers are different jobs. Splitting them prevents a quiet screenshot death spiral.

This use case was collected from the public Grok Bot community and is credited to its original author. Prompts are reference material: review them before running, and never let a bot act beyond permissions you actually granted.