SuperAPI AI Directory

PinkCode

Open-source desktop GUI for Grok Build with parallel agent sessions, live activity timelines, usage visualizations, file-change review, and permission controls over ACP.

Open website

About this tool

PinkCode is a desktop graphical interface application focused on Grok Build, with the core goal of solving two problems that are difficult to manage in a terminal environment: advancing multiple agent tasks simultaneously, and intuitively understanding agent activity and costs.

Purpose and Positioning PinkCode transforms the Grok Build command-line workflow into a visual desktop workspace, but keeps grok itself in control of the process. It communicates with Grok Build via ACP (Agent Client Protocol) over stdio, and does not run an independent agent loop. Therefore, its role is a front-end interface for Grok Build, rather than a replacement for its agent logic.

Main Capabilities

  • Multi-session task panel: supports running multiple Grok Build tasks side by side for centralized management.
  • Real-time timeline: tracks the activity of each task in a readable form, reducing the difficulty of understanding the status of multiple tasks.
  • Workspace browser: used to browse workspace files and status.
  • Permission management: the host-side permission gate intercepts reverse RPC calls (such as session/request_permission, fs/write_text_file, x.ai/exit_plan_mode, x.ai/ask_user_question), and decides whether to allow or deny agent operations based on the configured risk policy.
  • Usage dashboard: shows where credits and tokens go, helping users understand consumption.

Technical Architecture and Communication Method PinkCode is built on Tauri 2, React 19, TypeScript, and Rust. It communicates with Grok Build via ACP (JSON-RPC over stdio), involving prompts, session/set_mode, session/set_model, usage/recap extensions, and lifecycle notifications. This design keeps it lightweight and relies on Grok Build's existing agent capabilities.

Installation and Usage

  1. Install Grok Build: PinkCode requires the Grok Build CLI to be installed first. On Windows use PowerShell, and on macOS / Linux / WSL use the corresponding command. By default, Grok stores data under ~/.grok on macOS/Linux, and under %USERPROFILE%.grok on Windows, and the location can be changed by setting GROK_HOME.
  2. Install PinkCode: download the prebuilt installer from GitHub Releases. Windows x64 provides an NSIS installer; macOS provides Apple Silicon and Intel builds; Linux requires building from source, and a CI installer is not currently available.
  3. On some Wayland compositors (such as niri, Sway, Hyprland, etc.), Overlay CSD and acrylic transparency effects have rendering issues with WebKitGTK. Specific flags can be used as a temporary workaround, and can be removed after this technology stack handles default window decorations.

Applicable Scenarios Suitable for developers or teams that need to manage multiple Grok Build tasks simultaneously and pay attention to agent activity details and resource consumption, especially when they want to replace pure terminal operations with a graphical interface.

Limitations PinkCode does not run an independent agent loop, and its functionality depends entirely on the existence and operation of the Grok Build CLI. The Linux platform requires building from source, and there is currently no CI installer. Rendering issues in the Wayland environment require temporary flags as a workaround. Other functional details, charging methods, or pricing information are not currently provided.