Skip to content

[RefImpl] Grok Build TUI host adapter #108

Description

@antman1p

Target runtime or language

Grok Build TUI

What this proves

Build a Guardian adapter against Grok Build TUI, alongside the Claude Code, Cursor, and NVIDIA NAT adapters in PR #22 and the Codex adapter in #89. Additional adapters strengthen the reference implementation and showcase ACS across platforms without blocking the benchmark.

Grok already loads Claude-shaped hooks and emits session_id / tool_name / tool_input, but the shipped Claude Code host does not govern it. Dogfood: #107.

Measured gaps:

  • tool_name is run_terminal_command (AGT fails closed as tool_unknown; destructive-shell rules never run)
  • PostToolUse has no $.tool_response.stdout (result gate cannot build an envelope; Grok uses a tagged toolResult with output_for_prompt)
  • shipped matcher ^(Bash|WebFetch)$ does not block PreToolUse; a Grok matcher must name run_terminal_command
  • $CLAUDE_PROJECT_DIR is the git workspace root, not the agt tree

A thin shim plus hookmap against unchanged packages/host-adapter is the same pattern as OpenCode. Please say which tree this belongs in: reference-implementations/agt/hosts/grok/ (subprocess, like Claude Code) or adapters/ in PR #22 (Python, signed envelopes, like Codex).

Do you intend to implement this yourself

Yes, I want this assigned to me

Current Priority Scope

Feeds the runnable Guardian reference implementation

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions