Grok Bots, Python And Your Own GPU: Put Your Computer To Work

Tick off Your Turn as you go. This is the last part, so use More In This Series at the bottom to revisit any post.

29 min read

I grew up playing Halo with my brothers. Couch, snacks, one TV split into four little squares, and a lot of yelling. I still remember pretty much every line from those games, and one scene has stuck with me for twenty-some years. So when I found out my Grok Bots could run Python on my own computer and put its graphics card to work, I knew exactly what I wanted to try first.

This is a long one on purpose. I'll tell you the story, show you the real project, then walk through everything else Python on your own machine can do, with prompts for ten kinds of businesses. If you only want the prompts, use the Jump To list.

The Scene I Can't Stop Quoting

If you played the second game, you know the one. Early on, the enemy plants a bomb on a human space station. The Chief, the armored hero you play, defuses it. Then, instead of tossing it out an airlock, he rides it back over to the enemy ship that brought it.

Over the radio, the admiral asks him what exactly he thinks he's doing. The Chief's answer, more or less: he's giving the Covenant their bomb back. Then he jumps out, the ship goes up behind him and he floats away like it's a Tuesday.

My brothers and I quoted that line at each other for years. Someone borrows your charger and doesn't return it? You give the Covenant their bomb back. Dinner plates left on the couch? Same energy. It became our family's way of saying "returning to sender, with interest."

I don't own that scene, and nothing here is affiliated with the people who made the games. What I wanted was my own homage: a brand-new 3D render, built from scratch on my own computer, of what that moment felt like to a kid on a couch. No game footage, no ripped models, just a tribute I made myself.

Meet R&D Render: The Real Example

R&D is the bot that handles research and technical questions in my setup. For this project I gave it a side job I call R&D Render: plan the scene, write the Python, run the 3D software on my PC and report back. I'll let it explain.

Here's roughly how the job went, step by step:

1. Check the machine. R&D asked to look at what was installed and whether the graphics card was available to the 3D software. I approved a quick, read-only check.
2. Set up one job folder. Everything for the project lived in a single folder: the script, the scene file and the finished frames. Nothing outside it.
3. Write the scene in Python. Instead of me clicking around a 3D program for weeks, R&D wrote a script that builds simple shapes, lights and a camera. My notes became the direction: "less glossy, more dramatic," "bigger explosion," "the ship should feel huge."
4. Test small first. Quick low-quality previews came back as images so I could react before any long render.
5. Render on the GPU. Once the preview looked right, the full-quality render ran on the graphics card.
6. Report back. R&D sent the finished image, where it saved it and a short summary of settings so we could redo it later.

The renders are done, and you'll find them all through this post. Every one ran on my own PC: an RTX 2060 SUPER with 8 GB of graphics memory, Blender 4.5 LTS with the Cycles renderer and the OptiX denoiser, at 1920x1080. The simple line art took under a second per image. The busiest scene in this post, the explosion, took 13.7 seconds. R&D wrote the scripts, and nothing ran until it was approved.

What "Python On Your Own Computer" Actually Means

Python is a programming language that reads almost like plain English. You don't need to learn it to use it this way. Your bot writes the code; you decide whether it runs.

Normally your Grok Bots work on their own cloud computer. That's great for most jobs, and it keeps working when your laptop is closed. But some work belongs on your own machine:

• The files are already there: photos, spreadsheets, scanned paperwork.
• You have hardware the cloud job doesn't, like a strong graphics card.
• You'd rather certain files never leave your computer.

When you connect your own computer, a bot can run commands and scripts on it. Your approval settings decide what runs on its own and what stops to ask you first. That approval step is the whole deal. It's the difference between a helpful assistant and a stranger with your keyboard. (As of Oct 2026, per the Grok Bot docs. Check the current docs for exact setup steps.)

How The Bot Runs Jobs On Your Own Computer

This part confused me at first, so here's how it actually works in plain English.

Your computer gets registered once. You install the Grok Bot app on the PC you want to use and connect it. After that, your bot can send commands to that PC through the app. The bot does the thinking; your PC does the heavy lifting.

The PC has to be on and awake. The Grok Bot app needs to be running on it, too. If the computer is asleep, shut down or the app is closed, the job can't run. For long jobs, I set my PC so it won't go to sleep while I'm away.

You don't have to babysit it. You don't need to keep the chat window open or keep typing to the bot. Ask for the job, approve it and go do something else. The bot reports back when it's done.

Your Approval Options

You decide how much a bot can do on its own. These are the settings in the Grok Bot app:

• Auto-review (Settings > General). An automatic safety check looks at each command. Routine, safe ones go through. Risky ones stop, and you get an approval card.
• Auto-review rules (also in Settings > General). You can add, reword or remove rules so certain actions always ask you first, or are always OK.
• Local execution and your registered computers (Settings > Computer). This is where you control whether bots can run on your own PC at all.
• Approval cards. When a card appears, in that bot's chat or on the PC doing the work, you approve it or deny it. A denial stops that action.

My advice: start cautious. Keep Auto-review on, read each card and approve it yourself. Once a job has run cleanly a few times and you trust it, loosen the rules for that kind of job only. If something on a card looks off, deny it and ask the bot to explain first.

Tip: you don't have to use the buttons. When a bot asks you a question with a card or a set of buttons, you can skip them and answer in your own words. Click the bot's message and use the reply arrow. Your answer gets threaded to that message, so the bot knows exactly what you're responding to.

Watch the right screen. If you're sitting at a different computer, you might not see the card, and the job will just wait for you. When a job seems stuck, check the PC doing the work. There's usually a card waiting for your tap.

Everything stays in one jobs folder. You pick a single folder for the work, and the bot keeps its scripts, downloads and results there. Your other files stay out of it, and you always know where to find the finished work.

Get set up the first time:

I want to run jobs on my own computer. Walk me through connecting my PC to the Grok Bot app, keeping it awake while a job runs and where approval cards will show up. Use the folder [path] as the only jobs folder. Explain my approval options: Auto-review and Auto-review rules in Settings > General, and Local execution in Settings > Computer. Recommend a cautious starting setup, and stop for my approval on anything risky.

A Tour Of The Settings Menu

Before your first local job, it helps to know where everything lives. There's no gear icon. Open Settings from the account button at the bottom-left of the sidebar (your avatar and name), use the keyboard shortcut Cmd+comma (Cmd+,), or choose "Open settings" from the command palette.

You'll see up to five tabs: General, Computer, Vault, Usage & Billing and Updates. Vault and Usage & Billing only show when they're turned on for your account, and some rows only appear on some accounts, so don't worry if yours looks a little different.

• General. Your account card (sign in or out), Theme (Follow System, Light or Dark), accent color, Language, spell check, microphone, hardware acceleration, network debugger, notification sound (on or off, and which sound), time zone, Auto-review, Auto-review rules and security keys. Why it matters: Auto-review and its rules decide which commands on your PC go through and which stop for your approval. Time zone matters for scheduled jobs, so a nightly script runs at your night, not someone else's. A notification sound helps you notice when a card is waiting.
• Computer. Local execution, your registered computers, Update Bot's Computer and Reset Bot's Computer. Why it matters: Local execution and your registered computers control whether bots can run on your own PC at all, and which one. Update Bot's Computer moves your bot's computer to a fresh instance and keeps its files and logins, but any software it installed has to be reinstalled. It takes a two-click confirm. Reset Bot's Computer is the last resort: it restores the last snapshot and can lose recent work, so try Update first.
• Vault. Saved logins, cards and contact details your bots can fill in for you. Why it matters: passwords stay in the Vault instead of ending up in a script or a chat.
• Usage & Billing. Included usage, on-demand usage, your plan and billing. In my opinion, Grok's billing is the most affordable option for heavy users. Why it matters: long local jobs and big batches add up, so it's worth a peek here before you start something huge.
• Updates. Update status, update channel and automatic updates. Why it matters: the Grok Bot app on your PC is what receives your bot's commands, so keeping it current keeps local jobs running smoothly.

If you only check three things before your first job: Local execution and your computer in the Computer tab, Auto-review in General and your time zone if anything will run on a schedule.

GPU Vs CPU: Which Jobs Go Where

Every computer has a CPU, the main processor. Many also have a GPU, the graphics card. They're good at very different things, and picking the right one is half the trick.

The CPU is a handful of very fast, very smart workers. It's best at jobs with lots of steps and decisions: reading a spreadsheet, filling a PDF, renaming files, cleaning up data. Most everyday scripts are CPU jobs, and they run fine on almost any computer.

The GPU is thousands of smaller workers doing the same simple thing at once. That's perfect for rendering 3D scenes, processing huge batches of images and running AI models locally. If your job is "do the same math to millions of pixels," the GPU wins.

A few practical things I learned:

• Graphics memory is the real limit. A GPU has its own memory. Big 3D scenes and big AI models need more of it. If a job doesn't fit, it fails or falls back to the slower CPU.
• Not every program uses the GPU. The software has to support it, and sometimes you have to turn it on. Ask your bot to check.
• Heat and noise are normal. Long GPU jobs make the fans work. Keep the case vents clear and don't run it in a closed cabinet.
• Older or laptop GPUs still help. They're slower, but many jobs still beat the CPU.
• No GPU? You're not out. Almost everything in the next section runs on the CPU, just slower for the heavy stuff.

Ask your bot to check your machine first:

Check my computer before we start any project. Tell me my operating system, my processor, my graphics card and its memory, and whether Python is installed. Don't install or change anything yet. Explain in plain English what kinds of jobs this machine is good for.

Nine Things Python Can Do On Your Machine

Rendering is the flashy example. The quiet, everyday stuff is where most small businesses get their time back.

1. Rendering And 3D

Free 3D software can be driven entirely by Python. That means a bot can build a scene, set the lights, place a camera and render a still or animation, all from a script you can rerun. Change one line ("make it sunset") and render again.

2. Image Processing And Batch Resizing

This is the one most businesses should try first. Hundreds of photos, all resized, renamed, compressed and saved into neat folders while you do something else. Add a watermark, fix rotation, convert formats, crop to a square for social posts. The bot writes it once and you reuse it forever.

Try a photo batch job:

On my computer, look in the folder [path]. Make a copy of every photo, resized to 1600 pixels on the long side, saved as a web-friendly image in a new folder called "web-ready." Don't touch the source files. Show me the script and wait for my approval before running it, then give me a short report.

3. Data Crunching And Spreadsheets

Python is excellent at the boring spreadsheet work: merging monthly exports, cleaning messy columns, removing duplicates, building summaries and charts. It can work on files too big for a spreadsheet app to open comfortably.

4. PDFs And Scanned Paperwork

Split, merge, rename and organize PDFs. Pull text out of documents. For scanned paper, text recognition (often called OCR) can turn a picture of a page into searchable text. It's not perfect, so plan on a quick human check, but it beats retyping.

5. Local AI Models

Some AI models can run right on your own graphics card. They're usually smaller and less capable than big cloud models, but they're useful for private drafts, sorting documents or describing photos without sending files anywhere. Graphics memory decides how big a model you can run.

6. Scheduled Scripts

Once a script works, it can run on a schedule: every night, every Monday, the first of the month. Your computer needs to be on for jobs that run on it. For jobs that don't need your machine, a routine on your bot's cloud computer is usually simpler.

7. Gathering Public Data

Python can collect public information from websites, like weather forecasts, public permit listings or open government data, and drop it into a spreadsheet. Stick to public data, follow each site's terms, go slow and never try to get around a login or a block. When a site offers a download or an official data feed, use that instead.

8. File Organization

Sort a messy downloads folder by type and date, find duplicates, archive old projects, rename files to a clean pattern. Simple, satisfying and a great first project for building trust with a bot.

9. Small Custom Tools

Once you see how this works, you'll start noticing little tools you wish existed: a label maker, a quote calculator, a checklist that fills itself. Python is very good at small, specific tools for one business.

Safety: Approvals, Job Folders And The Stop Button

Running code on your own computer is powerful, and that's exactly why it needs rules. These are mine:

• Start cautious with approvals. Keep Auto-review on and read every approval card. If you don't understand it, deny it and ask the bot to explain in plain English first. Loosen your rules only for jobs you trust.
• One job, one folder. Every project gets its own folder. Scripts only read from and write to that folder unless you say otherwise.
• Copies, never sources. Batch jobs make copies. The untouched files stay where they were.
• Test small. Run on five files before five thousand.
• No surprise installs. If the bot needs to install something, it asks and tells you what it is and why.
• Know how to stop. Tell the bot to stop and it ends the job. You can also close the program or restart the computer. Nothing should run that you can't stop.
• Keep secrets out of scripts. Passwords and private keys don't belong in code files.
• Back up first. Before a big job, make sure your important files have a backup somewhere else.

Set your safety rules once:

Whenever you run anything on my computer: explain each command in one sentence, stop for my approval on anything risky or new, work only inside the project folder I name, make copies instead of changing my files, test on a small sample first and stop immediately if I say stop. Never install anything without asking.

Industry Examples With Prompts You Can Copy

Here's where it gets fun. These are ideas, not promises. Every business is different, so start with one and adjust. Replace anything in [brackets] with your own details.

Repair Shops

This is my world. Most of the wins here are paperwork and photos, not anything exotic.

• Resize and rename check-in photos into one folder per job.
• Turn a messy export of repair tickets into a clean weekly summary spreadsheet.
• Build a simple label or receipt layout from a spreadsheet row.
• Render a clean, generic shop-counter image for your website instead of a stock photo.

Repair shop prompt:

On my computer, open the folder [path] of job photos. For each job number in the file names, create a subfolder, copy that job's photos into it, resize them for email and make one contact sheet image per job. Show me the plan and the script first and wait for my approval.

Restaurants And Cafes

• Batch-edit dish photos for the menu, delivery listings and social posts, each at the right size.
• Combine daily sales exports into one weekly spreadsheet with your top sellers.
• Turn a recipe spreadsheet into printable prep sheets.
• Render a stylized dish image for a seasonal menu teaser.

Restaurant prompt:

Take the photos in [folder] and make three copies of each: a square one for social posts, a wide one for my website banner and a smaller one for delivery listings. Keep the color natural. Put each set in its own folder and show me five samples before doing the rest.

Real Estate And Architecture

• Resize, rename and organize listing photos by property and room.
• Build a simple 3D exterior concept from a rough floor plan for discussion, clearly labeled as a concept.
• Pull public data, like open government property records where allowed, into a neighborhood comparison spreadsheet.
• Create one-page PDF flyers from a spreadsheet of listings.

Real estate prompt:

Using the spreadsheet [file] of my listings, create a one-page PDF flyer for each property with the address, key details and the first photo from its folder. Save them in a folder called "flyers." Show me the first flyer before making the rest. Don't add anything that isn't in my spreadsheet.

One caution: label renders and concepts clearly so nobody mistakes them for photos of the real property.

Trades And Contractors

• Organize job-site photos by date and address, with before and after side by side.
• Turn a measurement spreadsheet into a materials checklist.
• Read scanned receipts with text recognition and sort them into a spreadsheet for your bookkeeper.
• Render a simple 3D mockup of a deck or patio layout for a client conversation.

Contractor prompt:

Go through the scanned receipts in [folder]. Use text recognition to pull the date, store and total from each one into a spreadsheet, and flag any you couldn't read clearly. Don't delete or move the scans. Show me the first ten rows before finishing.

Retail And Online Stores

• Batch-process product photos onto a consistent background, size and file name.
• Render clean product-style studio shots for items you designed yourself.
• Clean up a product spreadsheet before an import: fix capitalization, find missing fields, remove duplicates.
• Generate alt text drafts for product images with a local model, then review them.

Online store prompt:

Check my product spreadsheet [file] before I import it. List rows with missing titles, descriptions or images, duplicate product names and inconsistent capitalization. Make a cleaned copy and a short report of every change. Don't touch the source file.

Fitness Studios And Trainers

• Turn a class schedule spreadsheet into printable weekly calendars and social images.
• Build personalized workout plan PDFs from a template and a client's goals (no medical claims).
• Summarize attendance exports into a simple monthly report.
• Resize and caption progress photos for clients who've given permission.

Fitness prompt:

Using my class schedule spreadsheet [file], make a clean weekly schedule image sized for social posts and a printable one-page PDF. Use my colors [colors]. Show me a draft of each before saving the final versions.

Medical And Dental Offices

Big caution first: patient information is protected by privacy laws. Running something on your own computer doesn't make it compliant by itself. Talk to whoever handles compliance for your office before any patient data goes near an AI tool, and practice with made-up sample files.

• Organize and rename blank forms, policies and office documents.
• Turn a non-patient spreadsheet, like supply inventory, into a reorder checklist.
• Draft patient education handouts as PDFs from your own approved text.
• Build a staff schedule summary from a scheduling export that doesn't include patient details.

Office prompt (no patient data):

Using only the sample files in [folder], which contain no real patient information, organize our blank office forms into folders by type, rename them to a consistent pattern and make a one-page index PDF. Don't open any other folders on this computer.

Photographers And Creators

• Cull and sort a shoot by date, camera settings or file type.
• Batch export galleries at several sizes with a watermark.
• Run 3D simulations, like smoke or explosions, for video intros on your own GPU.
• Create contact sheets and client proof PDFs automatically.

Creator prompt:

For the shoot in [folder], make watermarked web copies at 2048 pixels on the long side, a contact sheet PDF with file names under each image and a list of any blurry-looking or duplicate shots for me to review. Work on copies only.

Accountants And Bookkeepers

Client financial data deserves the same care as medical data. Keep it on machines you control, follow your professional rules and get client permission where needed.

• Merge monthly bank exports into one clean spreadsheet with consistent categories.
• Flag possible duplicate transactions for a human to review.
• Split and rename stacks of scanned statements by client and month.
• Build a deadline checklist from a spreadsheet of clients and filing types.

Bookkeeping prompt:

Combine the monthly exports in [folder] into one spreadsheet. Standardize the date format, keep every column and add a column flagging possible duplicates (same date, amount and description). Don't change or categorize anything else. Show me the flagged rows for review.

Nonprofits And Community Groups

• Clean and merge volunteer sign-up sheets from several events.
• Turn event photos into a ready-to-share gallery, with permission.
• Build simple impact summaries from your own program spreadsheets, without inventing numbers.
• Mail-merge thank-you letters into PDFs from a supporter spreadsheet.

Nonprofit prompt:

Merge the volunteer sign-up sheets in [folder] into one spreadsheet. Remove exact duplicates, keep the earliest sign-up date for each person and list anyone missing an email address. Don't contact anyone; just give me the cleaned file and a short summary.

How I Can Help You Build Tools For Your Business

I built all of this for my own one-person shop first. Along the way I learned what works, what breaks and where the guardrails need to go. If you run a small business and you're curious what a custom Python tool or bot setup could do for you, I'm happy to talk through it.

Here's how I like to approach it:

1. Find the chore. We look for the repetitive task that eats your week.
2. Start small. One script, one folder, one test run on sample files.
3. Add guardrails. Approvals, job folders and a clear way to stop, from day one.
4. Hand it over. You get the tool, plain-English notes on how it works and the prompts to run it yourself.

I'm a repair tech first, so I'll be honest about what's a good fit and what's not. If something needs a full-time developer, I'll tell you. If you'd like to chat, send me a note through the contact page.

Why This Matters To Me

I run Franchitti's Fix by myself, out of a home-based shop, by appointment. Every hour a script saves me on photos or paperwork is an hour back at the bench. And honestly? Watching my own computer render a tribute to a scene I loved as a kid, with my bots running the show, was just plain fun. It reminded me why I got into fixing and building things in the first place: curiosity, and a little bit of that couch-with-my-brothers joy.

So here's one last render, just for fun: my own shop logo on a ring world, floating in space.

Quick Answers

Do I Need A Gaming Computer For This?

No. Most everyday jobs, like spreadsheets, PDFs and photo resizing, run fine on a normal computer's processor. A graphics card mainly helps with 3D rendering, very large image batches and local AI models.

Will A Bot Run Code On My Computer Without Asking?

Not anything risky. With Auto-review on, routine safe commands go through and risky ones stop with an approval card you approve or deny. You can add Auto-review rules so certain actions always ask. Local execution in Settings > Computer controls whether bots can run on your PC at all. Set a standing rule too: show the command, explain it, work in one folder and stop when you say stop. As of Oct 2026, per the Grok Bot docs.

Is Running AI Models Locally As Good As The Cloud?

Usually not as capable, but useful for private drafts and sorting. Your graphics card's memory limits how big a model you can run.

Can I Use This With Patient Or Client Data?

Be very careful. Running locally doesn't make something compliant by itself. Check with whoever handles privacy and compliance for your business first, and practice with sample files.

What Software Did You Use For The Renders?

Blender 4.5 LTS, a free, open-source 3D program with Python built in. It used the Cycles renderer and the OptiX denoiser on my RTX 2060 SUPER with 8 GB of graphics memory, at 1920x1080. The images in this post took from under a second to 13.7 seconds each.

This post shares my own experience and opinions running Franchitti's Fix. Franchitti's Fix isn't affiliated with or endorsed by xAI, Microsoft, Halo or its creators, NVIDIA, the Blender Foundation or Midjourney. Halo and its characters belong to their owners; the scene is described from memory and my render is a fan homage, not game footage. Product names belong to their owners. Features and plans change, so check each company's current docs. AI makes mistakes, so review its work.

Start With One Small Script

Don't start with a 3D masterpiece. Start with a folder of photos that need resizing. Approve one run, look at the results and build from there. And when your own phone needs a fix, Book An Appointment.

Was this helpful? Yes · No

Thanks! Glad it helped.

Thanks for saying so. I'll keep improving it.

More In This Series

This guide is part of Grok Bot Setup Guides: Start Here.

1. How My Repair Shop Runs On A Team Of Grok Bots
2. How To Set Up An AI Assistant With Grok Bot
3. How To Write AI Prompts For Beginners: 5 Parts
4. How To Give AI Feedback So It Revises, Not Restarts
5. How To Use AI Agents At Work Without Losing Control
6. How To Automate Tasks With AI Using Routines
7. Grok Bot Pricing And Usage: One Bot Or Many
8. AI Prompts For Small Business Owners: 5 Industries
9. How To Use AI In Everyday Life: Bot Ideas
10. AI Agent Ideas For Personal Use: Choose Your Bots
11. What Is Midjourney Good For? A Small Business View
12. How To Use Helper Bots So Your Main Bots Stay Focused
13. Running More Than One Grok Bot: Usage And What To Expect
14. How To Regulate Grok Bot Usage Without Losing Results
15. Standing Rules For AI Bots: A Style Sheet They Follow
16. AI Approvals: Let Bots Work While You Stay In Control
17. Keep Your Grok Bots Fast And Accurate: Shorter Requests And Regular Cleanup
18. Get Better Answers From Your Grok Bot: Before And Afters, Answer Cards And Rule Sets
19. Your AI Will Make Mistakes: How Reviewing And Feedback Get It Close To Perfect
20. Grok Bots, Python And Your Own GPU: Put Your Computer To Work You’re here

Back to the series index: Grok Bot Setup Guides: Start Here. All series: Grok Bot Guides: Every Series In One Place.