Set Up Grok Bot Approval Controls

Build a Grok Bot control set, test a delete gate, and draft a company message.

Introduction

30 Second Summary

A new founder can save time with an AI helper. Trust depends on knowing exactly what that helper can access before it acts.

In this project, you will build the Day 1 control set around one Grok Bot named Scout. You will prove its delete gate works before sending one Scout-drafted company message yourself.

What You'll Build

Picture an approval card stopping Scout's deletion while your connection register stays intact for you to verify.

By the end of this project, you'll have:

  • A bounded Scout that drafts from your facts while protected actions stop for your review.
  • A shared access register that shows every company tool the Bot's computer can reach while keeping bank access permanently out of scope.
  • A tested founder-control workflow where you deny a deletion, record observed usage, and send Scout's draft yourself.
  • Secret Mission: A founder-led audit that checks Scout's rules, Auto Review, Plugins, both evidence files, and Sent against the original ask.

Are there any prerequisites?

You need a Windows laptop with paid Grok Bot access through your existing Cursor plan. Your formed one-person company also needs an existing company mail account with one real message to send today. No terminal experience is required.

Before We Start

Before any setup begins, commit to a narrow Day 1 boundary: one Bot named Scout receives no company connections or sensitive details (tax IDs, bank details, passwords, or one-time codes). You personally send the real message from your existing company mail.

Set Up Grok Bot Controls

Before Scout receives work, the shared Bot computer must be ready. Your spending boundary must block paid spillover. Auto Review must inspect actions before they run. The plugin list must stay empty.

This step installs Grok Bot on your Windows laptop. You will sign in through Cursor authentication. You will then verify each control before creating Scout.

In this step, get ready to:
  • Install Grok Bot on your Windows laptop.
  • Sign in with your existing Cursor account and finish the shared computer setup.
  • Prevent paid spillover and confirm that Auto Review is on.
Install Grok Bot on Windows

Windows installers differ by processor architecture. Your System type tells you whether to choose x64 or Arm64.

  • Open the official Grok Bot download page in your browser.
  • Press the Windows key to open search.
  • Type Settings and press Enter.
  • Select System.
  • Select About.
  • Read the value beside System type.

Why does system type matter?

The x64 installer supports most Windows processors. The Arm64 installer supports Windows devices built on ARM processors.

Matching the installer to the value shown under System type prevents an incompatible installation.

Windows may ask for permission before the installer starts. This request allows the installer to add Grok Bot to your laptop.

  • Return to the Grok Bot download page.
  • Choose the Windows x64 or Arm64 installer that matches your system type.
  • Run the downloaded installer.
  • Approve the Windows permission request if one appears.
  • Press the Windows key after installation finishes.
  • Type Grok Bot and press Enter to open it.

You have cleared the first setup hurdle. Grok Bot is installed on your Windows laptop. You should see Get started on the first-use screen.

Installer or app not opening?

Confirm that the installer architecture matches the value under System type. Download the matching installer again if the values differ.

Close Grok Bot completely before trying the installer again.

Ask for help with troubleshooting your Grok Bot installation. You can also describe the problem in the Cursor Community Forum.

Sign in and finish computer setup

Grok Bot uses browser-based Cursor authentication. After sign-in, it prepares the shared cloud computer used by every Bot on your account.

The first setup can take several minutes while the computer starts or updates. A quiet loading screen during that time is expected.

  • Select Get started.
  • Finish Cursor authentication in the browser using your existing paid account.
  • Return to Grok Bot after authentication completes.
  • Answer any first-use questions without selecting a company tool.
  • Skip every option to install a plugin or authenticate a company service.
  • Wait while Starting your computer or Updating your computer is shown.
  • Stop when the main Grok Bot workspace loads.
  • Leave Scout creation for the next step.

The shared Bot computer is ready when the setup screen disappears. No company service should be connected or signed in.

Why keep the computer disconnected?

Every Bot on your account shares the same files. They also share browser sessions and installed connections.

An empty connection list lets you test the controls before any Bot can reach company systems.

🙋‍♀️ Computer setup not finishing?

Confirm that you authenticated with the existing paid Cursor account that includes Grok Bot access. Close Grok Bot completely before reopening it if the setup screen remains stuck.

Ask for help with a Grok Bot computer setup problem. You can also report the setup state in the Cursor Community Forum.

Lock spending, review, and connection settings

On-demand usage is extra paid usage after included weekly usage runs out. Keeping it off prevents Grok Bot from spilling beyond your existing plan.

This setting touches billing, so pause before changing it. Your goal is simple. Grok Bot must stop when included weekly usage runs out.

  • Open Settings in Grok Bot.
  • Find On-demand monthly limit.

✔️ On-demand monthly limit is available

The spending control is available inside Grok Bot.

  • Turn off On-demand monthly limit.
  • Confirm that the setting remains off.

ⓧ Grok Bot opens the web dashboard

Some accounts manage the spending boundary through the Cursor web dashboard.

  • Open Spending in the web dashboard.
  • Set Monthly Limit so paid spillover cannot occur.
  • Return to Grok Bot after saving the limit.

What does this spending control do?

Paid Grok Bot access includes weekly usage. On-demand usage adds billed usage after that weekly amount runs out.

With on-demand usage off, Grok Bot stops when the included weekly usage runs out.

Auto Review evaluates proposed actions before they run. A later step adds the founder-written rules that stop protected actions.

  • Return to Settings in Grok Bot.
  • Select General.
  • Open Auto-review.
  • Confirm that Auto Review is on.

Connected plugins are available across the shared Bot computer. The safe Day 1 state is an empty company connection list.

  • Return to Settings.
  • Open Plugins.
  • Open Yours if that installed-plugin area appears.
  • Confirm that no company plugin is connected.
  • Confirm that no company service has been authenticated.

Found a company connection?

Do not continue while a company plugin or authenticated company service is present. Remove the connection through its displayed controls before using Scout.

Ask for help with reviewing an unexpected Grok Bot plugin connection.

Before the final check, do you expect every screen to show the Day 1 boundary with no added access?

  • Return to the main Grok Bot workspace and confirm that computer setup has finished.
  • Open Settings.
  • Confirm that On-demand monthly limit is off or that Monthly Limit prevents paid spillover.
  • Open Auto-review under General.
  • Confirm that Auto Review is on.
  • Open Plugins.
  • Confirm that no company plugin or authenticated company service is connected.

Your controls now match the Day 1 boundary. Grok Bot is installed and signed in. The shared computer is ready. Paid spillover is blocked. Auto Review is on. No company connection has been added.

✔️ All controls match

Your Windows installation and shared Bot computer are ready. Keep every company connection empty until a later project explicitly approves one.

ⓧ I'd like to double check the controls

  • Grok Bot is installed on your Windows laptop and signed in with your existing Cursor account.
  • Shared Bot computer setup is complete. No company service or company account is connected or signed in.
  • On-demand monthly usage is off or the dashboard Monthly Limit prevents paid spillover beyond the existing plan.
  • Auto Review is enabled under General in Settings.
  • The Plugins page in Settings shows no connected company plugin.
  • Scout does not exist yet.

Your guarded workspace is ready. Next, you will create Scout and give it the standing rules that define its one Day 1 job.

Build Scout and the Control Set

Your Grok Bot setup is ready. The shared computer has no company connection, so Scout starts from a clean boundary.

A Bot is a durable AI teammate with a name, one job, its own conversation, and working context. Scout needs that job bounded before it receives company work.

Four standing rules define Scout's behavior. A separate Auto Review layer stops protected actions before they run.

The connection register records only the plugin state you read yourself.

In this step, get ready to:
  • Create Scout as one bounded worker.
  • Add eleven separate Require Approval rules to Auto Review.
  • Build the connection register from the plugin state you observed.
Create Scout with four standing rules

Scout's profile holds rules that remain true across its conversations. Today, its only job is to record founder-supplied connection facts and draft founder-specified messages.

  • Click New in Grok Bot.
  • Select Create new agent.

You should see the profile for a new Bot. This is the worker you will turn into Scout.

  • Open Bot actions.
  • Select Edit Profile.

The profile editor gives Scout a durable identity and description.

  • Enter Scout in the Name field.
  • Enter Day 1 operations recorder for Pineapple Advisory in the Title field.

The profile fields now identify Scout as Pineapple Advisory's Day 1 operations recorder.

  • Keep Scout's scope to one job: record founder-supplied connection facts and draft founder-specified messages.
  • Leave Scout without a research job or second job.
  • Paste these four standing rules into the Description field:
1. Use only the sources and facts I give you. Invent nothing.
2. Write only under `/workspace/pineapple/`.
3. Never open an account, sign anything, pay, send, publish, or sign in anywhere.
4. When an ask names a review point, stop and wait for me.

How do these rules bound Scout?

  • The first rule keeps Scout tied to founder-supplied facts.
  • The second rule limits Scout's files to /workspace/pineapple/.
  • The third rule blocks Scout from taking external company actions.
  • The fourth rule makes Scout pause at every named review point.
  • Apply the profile changes with the editor's save control.
  • Return to Scout's profile.

You should see Scout with the title Day 1 operations recorder for Pineapple Advisory. Its description should contain four numbered rules.

Profile does not match?

Check that the name and title are in their matching profile fields. Confirm that the description contains each rule on its own numbered line.

Make sure the profile changes were applied before leaving the editor.

Help me check Scout's profile settings.

Add eleven approval gates

Standing rules tell Scout how to behave. Require Approval rules always stop matching actions for your decision.

Each protected action needs its own rule. Separate rules make the boundary easier to inspect before you trust it.

  • Return to Settings from earlier.
  • Select General.

You should see Grok Bot's general settings.

  • Select Auto-review.
  • Add each line below as a separate Require Approval rule:
1. Require approval before sending any message.
2. Require approval before publishing anything.
3. Require approval before purchasing or paying for anything.
4. Require approval before deleting any file inside `/workspace/pineapple/`.
5. Require approval before overwriting anything outside `/workspace/pineapple/`.
6. Require approval before changing permissions or access.
7. Require approval before filing any form.
8. Require approval before accepting any terms or signing anything.
9. Require approval before opening any account or signing in anywhere.
10. Require approval before moving, copying, pasting, uploading, publishing, or sending client data outside that client's folder under `/workspace/pineapple/clients/`.
11. Require approval before entering, storing, copying, pasting, revealing, or using any bank login.

Why eleven separate rules?

Each rule covers one category of protected action. Auto Review can match a proposed action against the relevant boundary before that action runs.

The deletion rule protects the register you create today. The other rules establish the complete Day 1 control set.

  • Count the separate Require Approval rules.

You should count eleven separate rules.

  • Review the Always Allow rules.

You should find no Always Allow rule for any protected action.

Rule count does not equal eleven?

Look for two lines that were saved as one rule. Also check whether the client-data rule was shortened or split.

Help me compare my Auto Review rules.

Build the connection register

A review point is a named place where Scout must stop for your inspection. The five-part ask uses that pause before the live-state row is added.

You supply the source fact yourself. Scout records the plugin state without searching or inventing a connection.

  • Return to Settings from earlier.
  • Select Plugins.

You should still see no connected company plugin or authenticated company service.

  • Check the Yours area if it appears.

The observed connection state for today's register is none.

  • Return to Scout's conversation.
  • Send Scout this exact five-part ask:
Outcome. Create one account-wide register of every app the Pineapple Advisory Bot computer is connected to. Show what the Bots can reach, which Bot's job uses each connection, and when each connection should be revoked.

Sources. Use only the plugin state I tell you from Grok Bot settings. Do not search the web. Today's observed connection state is none.

Constraints. Use one row per connection. Use these columns: App, Account used, Bot whose job uses it, Date added, Plan day needed, Revoke date. Write one bank row in advance. Mark every bank field `NEVER` except the Bot field, which says `No Bot`. Invent nothing.

Deliverable. Create only `/workspace/pineapple/ops/CONNECTIONS.md`. Put this sentence above the table: `This file records every app the Pineapple Advisory Bot computer can reach, which Bot uses it, and when access should be revoked.` Add the table header and the bank row.

Review point. Stop after the purpose line, table header, and bank row. Show me the file. Wait for me to say `continue`.

How does the five-part ask work?

  • Outcome defines the account-wide register Scout must produce.
  • Sources limit Scout to the plugin state you observed.
  • Constraints define the six columns and protected bank row.
  • Deliverable limits Scout to one file under /workspace/pineapple/.
  • Review point makes Scout stop before adding the live-state row.
  • Wait for Scout to stop at the review point.
  • Compare the file Scout shows with this reference:
This file records every app the Pineapple Advisory Bot computer can reach, which Bot uses it, and when access should be revoked.

| App | Account used | Bot whose job uses it | Date added | Plan day needed | Revoke date |
|---|---|---|---|---|---|
| Bank | NEVER | No Bot | NEVER | NEVER | NEVER |

What should the review point show?

The purpose line explains why the account-wide register exists. The table header contains exactly six columns.

The bank row keeps every bank field at NEVER. Its Bot field says No Bot.

The live-state row should be absent because Scout is waiting for your review.

  • Tell Scout to correct any mismatch before continuing.

Scout did not stop?

Remind Scout that the named review point comes before the live-state row. Ask it to show the purpose line and bank row for review.

Help me get Scout to pause at the review point.

  • Send Scout this exact reply after the review content matches:
continue

Why send continue?

This reply records your decision to move past the named review point. Scout can now perform only the next instruction you provide.

  • Send Scout the observed live-state row with this exact instruction:
Add only this live-state row:

| None | None | No Bot | 2026-09-15 | Day 1 | Not applicable |

What does the live-state row prove?

The row records the plugin state you observed on 2026-09-15. It assigns the connection to no Bot because no connection exists.

The value comes from your screen. Scout does not infer or research it.

Before the final check, predict whether Scout's profile, Auto Review, and the register tell the same control story.

  • Return to Scout's profile.
  • Count the standing rules in Scout's description.
  • Return to Auto-review in the settings from earlier.
  • Count the separate Require Approval rules.
  • Review the Always Allow area for protected actions.
  • Return to the /workspace/pineapple/ops/CONNECTIONS.md file Scout created.

You should see Scout's exact title plus four standing rules. Auto Review should show eleven separate Require Approval rules.

No protected action should have an Always Allow rule. The final file should match the reference below exactly.

✔️ Awesome, I've got everything!

Good work. Scout now has one bounded job with the two control layers it needs.

The connection register records no company connection and preserves the bank boundary.

ⓧ I'd like to double check the full code

Compare every line of your completed file with this reference.

This file records every app the Pineapple Advisory Bot computer can reach, which Bot uses it, and when access should be revoked.

| App | Account used | Bot whose job uses it | Date added | Plan day needed | Revoke date |
|---|---|---|---|---|---|
| Bank | NEVER | No Bot | NEVER | NEVER | NEVER |
| None | None | No Bot | 2026-09-15 | Day 1 | Not applicable |

What should match?

Check the purpose line and all six column names. Check that both rows use the exact values shown.

Finished file does not match?

Tell Scout which line differs from the reference. Keep the file limited to the purpose line and the two required rows.

Help me correct the connection register.

You have built the complete Day 1 control set. Next, you will make the delete gate stop Scout before it can remove the register.

Test the Delete Gate and Record Usage

Your Grok Bot control set now includes Scout's standing rules plus eleven approval gates. The shared Bot computer's connection register records no company connections.

An Auto Review delete rule becomes trustworthy after it stops a real matching action. In this step, you will test that rule against the register before recording the usage values shown on your own screen.

In this step, get ready to:
  • Trigger the delete approval card against the connection register.
  • Choose Deny to keep the connection register intact.
  • Record the displayed plan name plus weekly usage in a one-line file.
Fire the delete gate

An approval card shows the proposed operation plus its inputs before the action runs. The gate passes only when this card appears.

Before you ask Scout, do you expect the register to disappear or an approval card to stop the action?

  • In Scout's conversation from earlier, test the delete rule by sending this request:
Delete ops/CONNECTIONS.md.

What does this request test?

This request targets a real file inside /workspace/pineapple/. It should match the delete rule before Scout can remove the register.

You'll see an approval card showing the proposed delete operation plus its inputs.

  • Check that the card targets /workspace/pineapple/ops/CONNECTIONS.md.
  • Select Deny.
  • Return to /workspace/pineapple/ops/CONNECTIONS.md from earlier.

You should still see the purpose line plus the six-column table. The bank NEVER row remains in place.

The None row dated 2026-09-15 also remains. That is the key control proven.

Did the Approval Card Fail to Appear?

A prose refusal shows that Scout's standing rule worked. It does not confirm the Auto Review gate.

  • Repeat the request with the full path /workspace/pineapple/ops/CONNECTIONS.md if Scout refuses in prose.
  • Return to Settings if no approval card appears.
  • Select General.
  • Select Auto-review.
  • Confirm the delete Require Approval rule is present.
  • Restore the register from the exact reference in the final double-check tab if the file disappeared.
  • Retry the deletion after the register is restored.

Help me diagnose why Scout's delete action did not produce an approval card.

Read the usage meter

Paid access includes Weekly usage that resets weekly. On-demand usage is extra paid usage after that included amount runs out.

The value displayed on your account is the source of truth. You never calculate or guess an allowance.

The usage label can be tricky because the current screen may say Usage & Billing or Weekly usage.

  • Open the account menu in Grok Bot.
  • Select Usage & Billing if that option appears.
  • Use Weekly usage in the account menu if that is the label shown.
  • Read the displayed plan name.
  • Record the plan name here: your plan name.
  • Read the displayed weekly usage number.
  • Record the weekly value here: your weekly usage number or not shown.
  • Use not shown for your weekly usage number or not shown if no number appears.

Good, both values now come directly from your account screen. Scout has nothing to estimate.

Why Record Only Observed Values?

The public plan page does not state a numeric weekly allowance. Your account screen shows the value that applies to you.

Using that screen keeps the usage record factual. It also preserves Scout's rule to invent nothing.

Write the observed usage line

The usage file is a dated snapshot of what your plan screen shows. It contains one line with no heading.

Before you send the prompt, do you expect Scout to preserve your observed values without estimating anything?

  • In Scout's conversation, create the usage record by sending this prompt:
Create `/workspace/pineapple/ops/usage.md`. Write exactly one line: `2026-09-15 | Plan: [[PLAN_NAME="your plan name"]] | Weekly usage: [[WEEKLY_USAGE="your weekly usage number or not shown"]]`. Use only the values I give you. Do not infer a value. Do not add a heading or a second line.

What Does This Prompt Control?

  • The date ties the record to your Day 1 check.
  • The plan field uses the value you read from your own screen.
  • The weekly usage field preserves the displayed number or not shown.
  • The final instruction keeps the file to one evidence line.
  • Open /workspace/pineapple/ops/usage.md from Scout's result.
  • Confirm the file has exactly one line.
  • Compare the plan value with your plan name.
  • Compare the weekly usage value with your weekly usage number or not shown.
  • Confirm no heading appears.

You'll see one line dated 2026-09-15. It shows the plan name plus the weekly usage value you read from the screen.

Does the Usage File Have Extra Content?

  • Tell Scout to remove every extra line if a heading or second line appears.
  • Tell Scout to replace any guessed value with the value from your plan screen.
  • Compare the file with the screen again.

Help me correct Scout's one-line usage record.

✔️ Awesome, I've got everything!

Your delete request is recorded as denied. The connection register remains intact while the usage file contains one observed line.

ⓧ I'd like to double check the full code

Compare the intact connection register with this full reference.

This file records every app the Pineapple Advisory Bot computer can reach, which Bot uses it, and when access should be revoked.

| App | Account used | Bot whose job uses it | Date added | Plan day needed | Revoke date |
|---|---|---|---|---|---|
| Bank | NEVER | No Bot | NEVER | NEVER | NEVER |
| None | None | No Bot | 2026-09-15 | Day 1 | Not applicable |

What Should Remain Unchanged?

The denied deletion leaves every line of the connection register in place. The bank row plus live-state row still match the reviewed version.

Compare the one-line usage file with this reference after inserting your observed values.

2026-09-15 | Plan: [[PLAN_NAME="your plan name"]] | Weekly usage: [[WEEKLY_USAGE="your weekly usage number or not shown"]]

What Should the Usage File Contain?

The file contains exactly one dated line. Its plan plus weekly usage fields match the values from your account screen.

Your delete gate has now stopped a real action while your usage evidence records only observed facts. Next, you will use Scout to draft a real company message that you send by hand.

Draft and Send a Real Message

Your delete test proved that Auto Review can stop a protected action before it runs. The connection register remains intact.

The next proof is useful work that stays inside the same boundary. You will use Scout in Grok Bot to draft a real company message from facts you supply.

Scout stops after the draft. You control the mailbox. You press Send yourself.

In this step, get ready to:
  • Define one real message your company owes today.
  • Review a short draft based only on your facts.
  • Send the approved message from your existing company mail account.
Define the real message

A bounded drafting request gives Scout enough context to help without granting access to your company mail. You decide the recipient, the facts, the purpose, and the requested next step.

Protect sensitive information

Scout needs only the details required to write this message.

  • Keep every tax ID, bank detail, password, or client secret out of Scout's chat.
  • Choose one message your company owes today.
  • Use a note to your registered agent, a question for your accountant, or a reply to a friend as a starting point.
  • Record who the message is for here: recipient.
  • Record the facts that the message must communicate here: facts and purpose.
  • Record the response you need here: response or next step.
Draft the message with Scout

The drafting prompt limits Scout to your information. It also defines the point where Scout must stop.

  • Create the draft by pasting this prompt into Scout's existing conversation:
Draft one short message to [[RECIPIENT="recipient"]]. It must say [[FACTS_AND_PURPOSE="facts and purpose"]]. Ask for [[RESPONSE_OR_NEXT_STEP="response or next step"]]. Use only what I wrote. Do not research. Do not open mail. Do not send, publish, sign, pay, open an account, or sign in. Stop after the draft.

How does this prompt hold the boundary?

  • The three recorded values define the message using your facts.
  • The instruction Use only what I wrote. prevents unsupported details from entering the draft.
  • The instruction Do not open mail. keeps Scout outside your mailbox.
  • The instruction Stop after the draft. creates the review point.

You should see one short draft based on the values you supplied. Scout should stop without opening mail or sending anything.

  • Read the draft from the recipient's perspective.
  • Check each statement against the facts you supplied.
  • Tell Scout exactly what to change if any detail, tone, or request is wrong.
  • Read the revised draft from the recipient's perspective.
  • Approve the draft once every statement matches your facts.

Draft includes unsupported details?

  • Identify the sentence that does not come from your facts.
  • Tell Scout to remove that sentence before you approve the draft.

Get help checking the draft with Scout.

Send the approved message yourself

Sending creates the external effect that Scout is prohibited from performing. Your mailbox remains under your control throughout this action.

  • Open the message composer for the real message you chose in your existing company mail.
  • Copy only the approved draft into the message body.
  • Check the recipient.
  • Check the subject.
  • Check the body.
  • Press Send yourself.

Before you check, where should the message appear if your manual send worked?

  • Open the Sent folder in your company mail.
  • Find the real message you just sent.

Your message should be listed in Sent. This confirms that you performed the external action yourself.

Cannot find the message in Sent?

  • Check whether your mail app still shows the message as unsent.
  • Confirm the recipient before trying to send the message again.
  • Avoid sending a duplicate while you investigate.

Get help tracing the send status with your mail app.

  • Switch back to Scout's conversation in Grok Bot.
  • Confirm Scout's last message is the approved draft or revision.
  • Confirm Scout did not open company mail.
  • Open Settings in Grok Bot.
  • Select Plugins.
  • Confirm no company plugin is connected.

Scout's conversation should end at the approved draft. You should see no connected company plugin in Plugins.

Scout never opened company mail. Its shared computer therefore has no signed-in mail session.

You held the boundary while completing a real company task. Next, you will compare the full Day 1 control set with the original ask.

Confirm the Day 1 Control Set

Your real company message is now in Sent. Scout stayed inside its drafting role while you handled the external action.

A Bot cannot certify its own controls. You will independently compare the Day 1 control set in Grok Bot with the original ask and its supporting evidence.

In this step, get ready to:
  • Confirm Scout's one-job boundary.
  • Verify every part of the named Day 1 control set.
  • Confirm the supporting evidence from the gate test, usage screen, and Sent folder.
Check Scout and Auto Review

Scout's profile holds its one job. Its description holds the four standing rules that define its boundary.

Auto Review evaluates proposed actions before they run. Its separate rules provide a second control layer.

Four Standing Rules to Match

  • Use only the sources and facts I give you. Invent nothing.
  • Write only under /workspace/pineapple/.
  • Never open an account, sign anything, pay, send, publish, or sign in anywhere.
  • When an ask names a review point, stop and wait for me.
  • In Grok Bot, switch back to Scout.
  • Select Bot actions.
  • Select Edit Profile.
  • Confirm the name is Scout.
  • Confirm the title is Day 1 operations recorder for Pineapple Advisory.
  • Confirm Scout's only job is recording founder-supplied connection facts plus drafting founder-specified messages.
  • Compare Scout's description with the four standing rules shown above.

Scout's profile is the first control layer. The next comparison checks the separate gate layer.

  • Return to Settings.
  • Select General.
  • Open Auto-review.
  • Confirm Auto Review is on.
  • Count eleven separate Require Approval rules.
  • Confirm no protected action has an Always Allow rule.
  • Compare every approval rule with the reference below.

Eleven Gates to Match

  • Require approval before sending any message.
  • Require approval before publishing anything.
  • Require approval before purchasing or paying for anything.
  • Require approval before deleting any file inside /workspace/pineapple/.
  • Require approval before overwriting anything outside /workspace/pineapple/.
  • Require approval before changing permissions or access.
  • Require approval before filing any form.
  • Require approval before accepting any terms or signing anything.
  • Require approval before opening any account or signing in anywhere.
  • Require approval before moving, copying, pasting, uploading, publishing, or sending client data outside that client's folder under /workspace/pineapple/clients/.
  • Require approval before entering, storing, copying, pasting, revealing, or using any bank login.

These checks confirm Scout's standing policy. They also confirm that protected actions still stop for your review.

Compare the register with Plugins

Every Bot on the account shares the same computer plus installed connections. The connection register must therefore match the account-wide plugin state you can see yourself.

  • In Grok Bot, return to Settings.
  • Select Plugins.
  • Confirm no company plugin is connected.
  • Confirm no company service has been authenticated.
  • If Yours appears, compare every listed item with the connection register.
  • Return to Scout's conversation from earlier.
  • Open /workspace/pineapple/ops/CONNECTIONS.md from Scout's existing files.

What Should the Register Contain?

  • The purpose line reads This file records every app the Pineapple Advisory Bot computer can reach, which Bot uses it, and when access should be revoked..
  • The table has six columns named App, Account used, Bot whose job uses it, Date added, Plan day needed, and Revoke date.
  • The bank row is | Bank | NEVER | No Bot | NEVER | NEVER | NEVER |.
  • The live-state row is | None | None | No Bot | 2026-09-15 | Day 1 | Not applicable |.
  • Match the purpose line with the reference above.
  • Count six table columns.
  • Confirm the bank row marks every protected bank field as NEVER.
  • Confirm the live-state row records no connection on 2026-09-15.

Why Write Your Own Proof?

Formal Audit Logs plus Action Recording are available only on Enterprise plans. Your conversation still preserves the approval request from the delete test.

A plain-language record gives you stable evidence of what Scout attempted. It also records the decision that kept the register intact.

  • Return to Scout's conversation from the delete test.
  • Find the approval card for the attempted deletion of /workspace/pineapple/ops/CONNECTIONS.md.
  • Record the stopped deletion in the text checkpoint below.
Check the meter and real message

The usage file must contain observed account values. Its single line should match the plan screen without an estimated allowance.

  • Return to Scout's existing files.
  • Open /workspace/pineapple/ops/usage.md.
  • Confirm the file contains exactly one line.
  • Return to your account's plan or usage screen from earlier.
  • Open Usage & Billing or Weekly usage, whichever label your account shows.
  • Compare the plan name on the screen with the Plan value in the usage file.
  • Compare the weekly number on the screen with the Weekly usage value in the usage file.
  • Confirm the line starts with 2026-09-15.

The Sent folder proves who performed the external action. The message should remain in your existing company mail account because Scout never opened mail.

  • Switch back to the company mail account from earlier.
  • Open the Sent folder.
  • Find the real company message you sent.
  • Compare its body with the approved Scout draft.
  • Confirm the message went to the intended recipient.

Before the final pass, do you expect every screen plus file to tell the same story about Scout's access and your actions?

  • Return to Scout's profile to confirm one job with four standing rules.
  • Return to Auto Review to confirm eleven approval rules with no protected Always Allow rule.
  • Reopen /workspace/pineapple/ops/CONNECTIONS.md to confirm the register remains intact.
  • Reopen /workspace/pineapple/ops/usage.md to confirm its one line matches the plan screen.
  • Return to Plugins to confirm Scout has no company plugin or company sign-in.
  • Return to Sent to confirm you sent the message by hand.

You should now see one bounded Scout with no research job or second job. Every control plus evidence item should agree with the original ask.

That closes the loop. You have independently confirmed the complete Day 1 control set without giving Scout another connection or external action.

Secret mission

Step 5: Confirm the Output

Scout has completed the work. Your final challenge is to certify the controls yourself by matching every claim to independent evidence.

Clean Up Your Resources

Clean Up Your Resources

This project adds $0.00 USD today beyond the paid plan you already use. Grok Bot remains within the spending boundary you confirmed.

Choose whether to keep the control set ready, pause Scout by assigning no more tasks, or remove the two project records from the shared Bot computer.

Resources you used:

  • The connection register at /workspace/pineapple/ops/CONNECTIONS.md.
  • The usage record at /workspace/pineapple/ops/usage.md.

Your sent message stays in the company mail you already use. Scout created no company plugin or company session to disconnect.

Keep everything running

No action is needed. Choose this option if you want Scout's controls and evidence ready for your next task.

  • Keep Scout's one job and four standing rules unchanged.
  • Keep all eleven Require Approval rules active in Auto Review.
  • Retain both records under /workspace/pineapple/ops/.
  • Keep Plugins free of connected company services.

Pause - I'll come back to this later

Scout has no routine or running task to shut down. Pausing means leaving the control set untouched while you stop assigning work.

  • Stop giving Scout new tasks.
  • Leave Auto Review enabled.
  • Leave /workspace/pineapple/ops/CONNECTIONS.md in place.
  • Leave /workspace/pineapple/ops/usage.md in place.
  • Review the connection register before you resume work with Scout.

Delete - I don't want to use this again

Deleting these files removes the evidence you built. An approval card gives you a final chance to verify each path.

  • Return to Scout's conversation from earlier.
  • Ask Scout to delete /workspace/pineapple/ops/CONNECTIONS.md.
  • Check that the approval card names /workspace/pineapple/ops/CONNECTIONS.md.
  • Leave Always allow unselected so the delete rule remains active.
  • Select Allow once to approve this specific deletion.
  • Return to the file view you used earlier.
  • Confirm /workspace/pineapple/ops/CONNECTIONS.md no longer appears.

The usage record is a separate file. Its deletion requires another approval.

  • Switch back to Scout's conversation.
  • Ask Scout to delete /workspace/pineapple/ops/usage.md.
  • Check that the approval card names /workspace/pineapple/ops/usage.md.
  • Select Allow once to approve this specific deletion.
  • Return to the file view from earlier.
  • Confirm both project file paths no longer appear.

Scout's profile and the eleven approval rules remain in place. No company plugin or company sign-in exists, so there is no company session to close.

Nice Work!

Nice Work!

You did it! You built a Day 1 control set in Grok Bot with a tested delete gate.

You've learned how to:

  • Build the Day 1 control set around Scout. You gave it one job. You added four standing rules. You backed them with eleven Require Approval rules in Auto Review. You recorded account-wide access in the connection register.
  • Prove the delete gate with a real protected action. You saw an approval card before deletion. You selected Deny. The register remained intact. You recorded one observed weekly usage line in /workspace/pineapple/ops/usage.md.
  • Keep the mail boundary under your control. You supplied the facts. Scout drafted the message. You reviewed the result. You pressed Send in your existing company mail.
  • Secret Mission: Confirm the complete Day 1 control set against the original ask. You checked Scout's profile. You checked Auto Review. You compared Plugins with /workspace/pineapple/ops/CONNECTIONS.md. You matched /workspace/pineapple/ops/usage.md to the plan screen. You found the real message in Sent.

Ready to quiz yourself?