Grok Feather

The Grok Feather lists Grok Build TUI sessions on the Perch and resumes them in a real PTY pane. It ships compiled into toowl, the same way the Claude Feather does. Bring your own grok or groka binary; the Feather handles the rest.

Which binary runs

If groka is on your login-shell PATH, toowl uses it — including when you type grok in a toowl pane. A toowl-owned shim directory is prepended to PATH; it never overwrites ~/.local/bin/grok. If groka is missing, grok is used.

Install the CLI from the Perch

No Grok binary? The rail is an install card, not an empty list. Install Grok runs the official installer (https://x.ai/cli/install.sh) in a pane so you can watch it. That is not an Aviary install — Aviary installs Feathers (Perch chips), not vendor CLIs.

Sessions

Sessions are read from $GROK_HOME/sessions (default ~/.grok/sessions). Subagent and forked child sessions stay off the rail. Click a row to grok --resume <uuid> in that session's own working directory. Header + starts a fresh Grok session when this Feather is active.

Aviary vs this Feather

Grok is first-party. Optional chips (Codex, and later more agents) install from the Aviary at toowl.dev/aviary so they never appear unless you ask.