GrokBot101
Connect your bot
Search
中文 EN

use cases jev-decision-then-grokbot-execute

engineering ✦ 84~20 min setupintermediate

Jev decides → Grok Bot executes (cheap/fast loop)

@0xCodila's 7-minute setup as posted: prompt → Grok Bot → Jev decision → Grok Bot execution. Jev (via TypeSafe) chooses the next action; Grok Bot does the work. Shadow first. Humans keep irreversible actions.

Source: @0xCodila ↗ ✓ verified 2026-09-20
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 Jev and Grok Bot's jobs distinct. This is not a Jev product tutorial beyond what the source post states.

Loop we want: my prompt → you (Grok Bot) → Jev decision → you execute → result.

Setup (source order; skip a step if I already did it):
1. I open TypeSafe / @typesafeai and create an API key. I will not paste it in chat. I will store it in the secure field you name.
2. On Agent Computer, install typesafe-sdk and smoke system_one (Choice) as the source describes — report pass/fail, do not invent a green check.
3. Build or clone the usage lab (router, dry-run, config, logs). Source repo named in the thread: https://github.com/Bodila51/grok-bot-jev
4. Add skill jev-usage-router: before browser / research / retry / extra bot, call the router and honor the action.
5. Stay in shadow first. Read logs. Kill switch: bypass Jev or enabled: false.
6. Only then flip active. You obey the route. Jev decides. You execute. I still control irreversible actions (send, pay, post, delete, merge).

Rules: never put the API key in a prompt, README, or log. Never claim a latency or cost win you did not measure in this lab.
Start in shadow. Confirm the kill switch. Then wait.

How it's set up

@0xCodila posted that Jev + GrokBot is the best agent system he has built, cheaper and faster than "what 95% of people are running" — his claim, not a benchmark. Setup "takes literally 7 minutes" in the post:

  1. Open @typesafeai, create an API key (keep it off chat paste).
  2. Tell Grok Bot to store TYPESAFE_API_KEY in the secure field.
  3. Install typesafe-sdk on Agent Computer and smoke system_one (Choice).
  4. Build the usage lab (router, dry-run, config, logs) or clone https://github.com/Bodila51/grok-bot-jev
  5. Add skill jev-usage-router: before browser / research / retry / extra bot → call the router, honor action.
  6. Shadow first, read logs, then active when you trust it. Kill switch: bypass Jev or enabled: false.
  7. Flip active: Grok Bot obeys the route; Jev decides; Grok Bot executes; humans control irreversible actions.

Roles: Jev is the cheap/fast next-action chooser. Grok Bot is the computer that still has the browser, files, and hands. Do not collapse them into one name.

Why it works

Most stacks spend an expensive model on "what should I do next?" This split puts that question on Jev and leaves execution on Grok Bot, with a shadow mode and a kill switch. The 7-minute clock and the "95%" line stay with the author.

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.