Visual Team

Open-source working alpha

Your server.
Your tasks. Your setup.

The sample is ready to explore without an account. Developers can build from source and connect their own live setup. The code is free under Apache-2.0; your platform access and hosting may have separate costs.

The tested path: ChatGPT web and Windows Codex CLI 0.154.0-alpha.6.2. Later runtimes need separate checks. Live setup requires ChatGPT developer mode and your own MCP endpoint. This alpha has no accounts or persistent history.

1. Explore locally

You’ll need Git, npm 10+, and Node 20.19+ within 20.x, 22.13+ within 22.x, or 24+. Node 22 is used by CI.

git clone https://github.com/tinatsntx/project-visual-team.git
cd project-visual-team
npm ci
npm run build:site
npm run preview:site

Open the local sample. The current widget replays fictional fixtures in your browser. No MCP connection or native action runs here.

2. Start your own server

npm run build --workspace @visual-team/plugin-ui
npm run dev

The development MCP endpoint is http://localhost:8787/mcp; its health check is /healthz. For ChatGPT, host or tunnel your own instance at a reachable HTTPS URL. Keep the alpha to a single disposable workflow with non-sensitive metadata; it has no authentication or multi-user account system.

3. Pair your server and developer app

  1. In your local clone, change plugin/mcp.json to your own server’s /mcp URL before building the native package.
  2. Register that same endpoint as your own ChatGPT developer app.
  3. Replace the owner’s app mapping in plugin/.app.json with your registration’s matching app-… key and asdk_app_… id.
  4. If your Codex process sets VISUAL_TEAM_MCP_URL, it must point to the same server. Otherwise leave it unset to use the packaged configuration.

Do not use the coordinator’s shared alpha endpoint or developer-app identity. The guided-alpha installer is a separate, coordinator-prepared route.

4. Install and review the native hooks

Build the compatibility package from your configured clone, then add its local marketplace and plugin through Codex’s normal controls. Use the actual executable path and check the version first.

npm run build:native-codex-compat
npm run verify:native-codex-compat
$visualTeamCodex = 'C:\full\path\to\codex.exe'
& $visualTeamCodex --version
& $visualTeamCodex plugin marketplace add (Resolve-Path '.\dist\native-codex-compat').Path
& $visualTeamCodex plugin add visual-team@visual-team-native

Keep the generated marketplace in place. Open /hooks, review the nine Visual Team entries, and trust them normally. If another installation exists, resolve it through Codex’s supported controls first. Never copy into the installed cache or bypass trust.

5. Check a disposable task

Invoke $visual-team explicitly in Codex. Attach your registered app in ChatGPT and render the returned taskId. Run one harmless action and confirm fresh native evidence appears in the same widget. Keep capabilities private. Respond to any permission prompt in Codex itself.

Finish only completed work and label results honestly. A refreshed clock alone does not prove hook delivery. Missing hooks leave reported status.

Keep the limitations in view

Task data normally expires after about two hours, and a server restart clears it. There is no independent end-to-end proof for every third-party account or newer runtime. After hosted code changes, refresh your ChatGPT developer-app registration and open a fresh chat.

Full source setup guide ↗Ask a setup question

Read privacy and alpha limitations before connecting a live task.