A rootless Kali NetHunter lab on Termux, optimized for coding and building, with Grok Build as the on-device pair programmer. No root, no custom kernel.
GrokHunter is an overlay. Full statement: CREDITS.md · grokhunter credits
| Layer | Credit |
|---|---|
| Install engine | jorexdeveloper — termux-nethunter, termux-distro |
| Host | Termux team — app, packages, Termux:X11 |
| Guest OS images | Kali / Offensive Security — NetHunter rootfs |
| AI agent | xAI — Grok Build, Grok models |
We are not affiliated with those projects; we depend on them and give credit.
No. It uses Termux + proot only.
The current focus is coding and building. The stack is general-purpose Linux on Android; treat it as a portable development lab.
Termux is the Android host. nethunter / nh enters Kali (proot guest). pkg is host; apt is guest. install.sh (rootfs) runs on Termux; overlay-only from a Kali clone is OK for wrappers.
echo "PREFIX=${PREFIX:-unset}"
command -v pkg; command -v apt
command -v nethunter; command -v grokhunterDeeper playbook: skill host-lab · grokhunter host. Persist the TUI with skill session-lab (tmux / grok --resume). MCP tools: grok mcp (skill mcp-lab; grokhunter mcp is the agent). Plugins: grok plugin (skill plugin-lab). Grok .rhai pipelines: skill flow-lab (not GitHub Actions). Disk: skill storage-lab. Editors: skill editor-lab. Hooks: skill hooks-lab. Completions/aliases: skill shell-lab.
| Bare Termux | GrokHunter Rootless | |
|---|---|---|
| Packages | Termux repos | Full Kali apt |
| Grok | Extra setup | One flag (--with-grok) |
| Desktop | Limited | XFCE + Termux:X11 |
| Identity | Generic shell | Coding-lab profile + skills |
Grok Build (grok / grokhunter). Optional: Aider with the same xAI key.
XFCE is the recommended default (light, familiar, works well with Termux:X11).
Only if you want a graphical desktop. Shell + grok is enough for most pair-programming sessions.
Yes. Larger screens work well with nh-x11 + XFCE.
That used to be a hard fail. It is now a warning. Termux’s Android host often has no /etc/os-release. Kali NetHunter should have it (or /usr/lib/os-release). Coding still works either way.
Usually a false alarm. Cloudflare often returns 403 to curl on https://x.ai, and https://api.x.ai/v1/models returns 401 without a key. Both mean the network works. Doctor now treats those as reachable. A real outage is http_code=000 / timeout.
The lab often runs as root inside proot, so git defaults to root@localhost.localdomain (or an empty ident that becomes kali@localhost). GitHub cannot map that to a user.
grokhunter git-identity setThat uses gh if logged in, else GH_TOKEN / GITHUB_TOKEN, else the GitHub origin owner on this clone. Or set the GitHub noreply from settings/emails:
git config --global user.name "Your GitHub name"
git config --global user.email "ID+LOGIN@users.noreply.github.com"Use overlay-only so you do not re-enter the termux-distro / rootfs path:
# Clone:
cd ~/GrokHunter && git pull
bash install.sh --overlay-only --with-completions
grokhunter ensure
grokhunter skills install
# One-liner (no git):
GROKHUNTER_REFRESH=1 bash <(curl -fsSL https://raw.githubusercontent.com/FineComputer14451/GrokHunter/main/install.sh) \
--overlay-only --with-completionsYes — overlay-only (no rootfs / termux-distro):
bash install.sh --overlay-only --with-x11 --with-aider
bash install.sh --overlay-only --with-grok --with-v9-models --with-completions
# refreshes CLI wrappers + skills under ~/.local/bin and ~/.grok/skillsProduct skills are any skills/<name>/SKILL.md in the repo. grokhunter skills install copies all of them. Core health is still the coding trio (skills=N/3); x11-desktop and nethunter-recon are optional.
Coding Team agents (true multi-agent system prompts): benjamin, lucas, harper, coding-team install to ~/.grok/agents/. Grok loads them at runtime via /config-agents or spawn subagent_type. See CODING-TEAM.md.
Requires at least one --with-* flag.
grokhunter models status
grokhunter models install
grokhunter ai-smoke # SpaceXAI Responses smoke (needs XAI_API_KEY)
bash scripts/ci-unit.sh # local unit checks (no network)~/.grok/secrets.env (mode 600). Never commit this file.
Grok Build is cloud-oriented. For local models, use tools like Cline/Aider with Ollama on a machine that can run them; phones rarely have enough RAM for strong local coding models.
No.