agentleFS
Sign inStart free
Simple-With-UsSimple-With-Us/BotFleet/.claude/skills/drive-grok-tui/SKILL.md

drive-grok-tui

Skill4 starsChanged 12 days agoApache-2.0View on GitHub

Drive a live Mac Grok TUI session from any local agent (Claude, Cursor, Grok, Shellular, this TUI, …). List chats with idle/working/needs-input, peek or tail the transcript, inject a prefixed follow-up, await the reply via disk poll, or cancel. Use when you need to send work into an already-open grok terminal instead of spawning grok-acp :12419.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Start a second grok agent serve or bind :2419.

    line 49

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Drive a live Grok TUI

Shared ~/.claude/skills. Monet, Claude/Fable, and (when active) Renoir all load this directory. Do not treat the word Monet in examples as proof of your seat. Pin AGENT_SEAT / AGENT_TAG from the logged-in account before Slack or board --by:

  • Monet → MONET, Notes Monet, monet/, ~/apps/<app>-monet
  • Claude / Fable → CLAUDE, Notes Claude, claude/, ~/apps/<app>-claude
  • Renoir → RENOIR, Notes Renoir, renoir/, ~/apps/<app>-renoir Cursor, Grok, Grok Bot, Codex, AG, DeepSeek, Kimi, and Fx have their own skill dirs and must not take identity from here.

The Mac Grok TUI joins ~/.grok/leader.sock. Any local agent can attach through grok-drive.py or seat-mcp. Do not spawn a second grok-acp on :12419 to talk to those chats.

CLI

python3 ~/apps/grok-acp-runtime/grok-drive.py list
python3 ~/apps/grok-acp-runtime/grok-drive.py peek --session-id ID --tail 8
python3 ~/apps/grok-acp-runtime/grok-drive.py tail --session-id ID --lines 12
python3 ~/apps/grok-acp-runtime/grok-drive.py prompt \
  --session-id ID --cwd DIR --prompt "…" --from-name CLAUDE
python3 ~/apps/grok-acp-runtime/grok-drive.py await --session-id ID --timeout 180
python3 ~/apps/grok-acp-runtime/grok-drive.py cancel --session-id ID --cwd DIR
  • list rows include live, turnState (idle / working / needs-input), title, lastTurnSummary.
  • prompt prefixes [from: NAME] (--from-name, else $AGENT_TAG / $AGENT_SEAT / remote).
  • prompt refuses a working / needs-input session unless --queue.
  • prompt returns queued: true as soon as the TUI accepts the message. It does not wait for the turn.
  • await (or --await-reply N on prompt) polls disk until the turn is idle or needs-input. That is how you read the reply. Do not --wait on ACP.
  • Peek/tail/await never session/load a live chat (load hangs ~45s).

MCP (seat-mcp)

Local stdio launcher: sh ~/apps/mcp-servers/seat-mcp-launch.sh (already in ~/.grok/config.toml). Tools: grok_sessions_list, grok_session_peek, grok_session_tail, grok_session_prompt, grok_session_await, grok_session_cancel.

Flow: list → prompt {sessionId, prompt, from} → await {sessionId}.

Do not

  • Start a second grok agent serve or bind :2419.
  • session/load a chat the TUI already has open.
  • --wait on ACP for a live TUI reply (the wait is that TUI turn).

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free