grok-build-supervisor
v0.4.3Persistent Grok Build Leader/ACP supervision with verified local-proxy initialization and visible Windows Terminal TUI control.
By VanyangyangLicense: MIT78 GitHub starsUpdated last week
Directory evidence
- Runtimes
- Codex and Claude Code
- Parsed components
- 4 skill or MCP entries
- Source updated
- Oct 2, 2026
- Manifest status
- Canonical path parsed
The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →
Install grok-build-supervisor for Codex and Claude Code
codex plugin marketplace add Vanyangyang/cursor-bridge
codex plugin marketplace upgrade vanyangyang
codex plugin add grok-build-supervisor@vanyangyangPaste and run these commands in a terminal with Codex. They add and refresh the vanyangyang catalog, then install this plugin.
Compatibility: the page URL and API slug “grok-build-supervisor” remain stable.
- Codex:
grok-build-supervisor@agent-plugin-marketplace→grok-build-supervisor@vanyangyang
The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.
Get the source manually
git clone https://github.com/Vanyangyang/cursor-bridgeClone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is plugins/grok-build-supervisor/.
Plugin files
├── .codex-plugin/plugin.json├── .claude-plugin/plugin.json├── skills/grok-build-supervisor/SKILL.md├── skills/grok-executor-off/SKILL.md├── skills/grok-executor-on/SKILL.md└── .mcp.json
Included Skills3
Initialize the persistent local proxy, then immediately ensure a visible Grok Build TUI for the current workspace when /grok_execute on activates, and continuously supervise that coding-agent session through a user-level Supervisor daemon as the user sends work, waits for completion, reconnects from another host task, or coordinates bounded two-way host-Grok communication without keyboard simulation. Do not use for Grok Imagine/browser generation, ordinary session summarization, or attaching an unrelated non-Supervisor TUI.
Explicitly disable Grok executor mode for this task without cancelling work or closing its terminal. Select this skill directly; no argument is required.
Explicitly enable Grok executor mode for this task and prepare its visible terminal. Select this skill directly; no argument is required.
MCP servers1
- command
- node
- args
- ./dist/grok-build-supervisor.mjs
- cwd
- .
Plugin manifests2
{
"name": "grok-build-supervisor",
"version": "0.4.3",
"description": "Persistent Grok Build Leader/ACP supervision with verified local-proxy initialization and visible Windows Terminal TUI control.",
"author": {
"name": "Vanyangyang",
"url": "https://github.com/Vanyangyang"
},
"homepage": "https://github.com/Vanyangyang/cursor-bridge/tree/main/plugins/grok-build-supervisor",
"repository": "https://github.com/Vanyangyang/cursor-bridge",
"license": "MIT",
"keywords": [
"mcp",
"codex",
"grok-build",
"coding-agent",
"agent-orchestration"
],
"skills": "./skills/",
"interface": {
"displayName": "Grok Build Supervisor",
"shortDescription": "Keep guarded Grok TUI sessions connected across host tasks and plugin reloads.",
"longDescription": "Run /grok_init once to remember the local proxy. In the project you want to use, /grok_execute on binds that workspace for the current task and immediately reuses or opens its visible Grok Build terminal without sending a coding prompt. If Grok asks whether the project is trusted, the Supervisor keeps that exact terminal and waits for the user's native Grok choice instead of opening another window or auto-trusting it. After that, Codex, Claude Code, or Pi plans and checks the work while Grok handles implementation. /grok_execute off leaves the mode without cancelling active work or closing the terminal. While Grok works, compact locating, modifying, and verifying updates replace raw tool logs and cumulative answers. Short results arrive once, while long reports are saved as local files with a path, size, checksum, and summary. Context-mode can optionally process those files but is not required. The plugin never enables approve-everything modes, adopts an unrelated Grok process, or stops a process it cannot prove it owns.",
"developerName": "Vanyangyang",
"category": "Developer Tools",
"capabilities": [
"Interactive",
"Write"
],
"defaultPrompt": [
"$grok-build-supervisor init",
"$grok-executor-on",
"$grok-executor-off"
],
"websiteURL": "https://github.com/Vanyangyang/cursor-bridge/tree/main/plugins/grok-build-supervisor"
},
"mcpServers": {
"grok-build-supervisor": {
"command": "node",
"args": [
"./dist/grok-build-supervisor.mjs"
],
"cwd": ".",
"default_tools_approval_mode": "approve"
}
}
}{
"name": "grok-build-supervisor",
"version": "0.4.3",
"description": "Persistent Grok Build supervision with proxy initialization, visible TUI startup, structured progress, compact polling, and long-result artifacts.",
"author": {
"name": "Vanyangyang"
},
"license": "MIT",
"repository": "https://github.com/Vanyangyang/cursor-bridge"
}For maintainers
If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.
[grok-build-supervisor on Agent Plugins Marketplace](https://pluginsmp.com/plugins/grok-build-supervisor)