C · Grok Build
You go from a folder of your files to a local repository — even if you do not know that word yet — then plan, review, and ship.
Two doors
New bench: folders, then what a repo is. No job repo yet? Pick a passion project — one small thing you actually want. That folder is your Build desk through C11. Already a repo: prove git status in a tree you already work in. Both meet at sign-in and the TUI. If the proof is a guess, take the new bench.
Passion project OK. Still two doors only — New bench / Already a repo. Passion project lives inside New bench.
After this
Finish the job here first. If you later want Grok inside software you own — a script, a site, a shop tool — open the API pathway. You do not owe that to Applied or Build.
New bench
You have never used a repo or a real terminal for this kind of work. Start here. Do not skip to Already a repo.
No job repo? Name a passion project now — a personal script, hobby page, shop utility, or toy with one run command. Owned files only. It carries through C11.
New bench
New bench, continued. After Folders, not magic. This is how a folder becomes a repository — still no GitHub account.
Already a repo
You can already open a terminal, cd into a git repo you work in, and paste git status. If that sentence is a guess, use Folders, not magic instead.
Both doors
Both doors. If grok --version already works, do not reinstall. Launch in the repo you just made (C0b) or the one you proved (Already a repo).
c2
c3
c4
c5
c6
c7
c8
c9
c10
c11
