Build by Grok Install CLI

Dedicated CLI install surface

Install Build by Grok Install locally. Land in grok>. Link later if you want.

Run the one-line install from the local folder you want the brain tied to. The CLI installs on your machine and drops you straight into grok> in that folder.

Git is optional. The current folder becomes the repo root by default. Git and GitHub connection matter when you want GitHub-connected bootstrap, branch/publish workflows, or the browser workspace.

If git is missing later, install it yourself on the machine, then come back to grok>. Or stay on the connected browser path through the workspace.

Install command copy + run

~/projects $ curl -fsSL https://install.buildbygrok.com/install.sh | bash

Installing the current CLI bundle...

Checking the checksum...

Keeping the install local to this machine...

Then it lands in grok> in the folder you started from.

Quickstart

Fastest clean start

~/projects $ curl -fsSL https://install.buildbygrok.com/install.sh | bash

Run that from the folder you want the local brain tied to.

grok> list all the files in this repo

You are now in the terminal-native agent for that local folder.

grok> /login

Use this later only when you want the web workspace or GitHub-connected features.

~/projects $ sudo apt install git

Install git yourself when you want local /git commands.

~/projects $ cd your-local-folder && git init

~/projects $ git add . && git commit -m "initial commit"

Finish the first local git commit in your normal terminal. If git asks for name or email, finish that setup there first, then come back to Build by Grok.

~/projects $ curl -fsSL https://install.buildbygrok.com/install.sh | bash -s -- --install-only

Use this when you want the local install without launching right away.

~/projects $ grok-build open

Open the app and workspace when you want the browser-connected surface.

Happy path: run the one-liner from the working folder and let it drop you into grok>. Link later only when you want the web workspace or GitHub-connected features.

Existing Repo

Choose the right path

curl ... | bash

Install and launch straight into the current local folder.

bash -s -- --install-only

Install the CLI locally and return to the shell without launching.

grok-build login

Link this local CLI later when you want the web workspace or GitHub-connected features.

sudo apt install git

Install git locally when you want the full local git lane.

cd your-local-folder && git init

Initialize the local repo in your normal terminal if the folder is not already a git repo.

git add . && git commit -m "initial commit"

Make one normal terminal commit first, then come back and use /git inside grok>.

grok-build open

Open the app/workspace flow in the browser. This is the GitHub-connected browser surface.

cd your-local-folder && grok-build

Start the terminal-native agent again later in the same local folder.

mkdir my-build && cd my-build && grok-build init

Optional GitHub bootstrap into an empty folder when you want the git-connected lane.

cd your-local-folder && grok-build run

Use this when you want the browser-connected runtime for the current local folder.

Roadmap: provider-native deploy guidance for Cloudflare and Vercel is planned. Today, the local-folder runtime and the GitHub-connected browser workspace are the primary surfaces.

First terminal test

Use these prompts after startup

grok> What files are in this repo and what does it look like this project does?

grok> Review the top 5 security or correctness risks. Do not generate code yet.

grok> Focus on one file, explain the smallest safe fix, then generate only the minimal code change.

grok> /help

grok> /status

grok> /clear

Common gotchas

If the flow seems off

  • The install itself is local. It does not connect GitHub by itself.
  • The default one-line install launches the CLI locally in the current folder. It does not auto-link the account.
  • Run /login from grok> or grok-build login later only when you want the web workspace or GitHub-connected features.
  • grok-build uses the current local folder as the repo root. Git is not required just to start.
  • If git is missing, install it yourself on the machine, then return to grok> and retry the command.
  • Finish the first local git setup in your normal terminal. If git asks for name or email during that first commit, finish it there before using /git in grok>.
  • Before the first local /git push, make sure one normal terminal push works in that repo, or use the connected browser/GitHub lane.
  • grok-build open is the browser app path. grok-build run is the browser-connected runtime for the current local folder.
  • Use grok-build init only when you want the explicit GitHub bootstrap path into an empty folder.
  • If you are at grok:file.tsx> and want the main prompt back, run /clear.
  • When asked [y/N], answer only y or n.