V1.0.1 - Parallel conversations and recommended tunnel setup

V1.0.1 — Parallel conversations and setup guidance

Released: 2026-09-20.

Changes

• Advanced conversations can select existing tasks in the same workspace even when another conversation uses that task or the Dashboard displays another task.
• ChatGPT conversation metadata pins task routing across MCP reconnects and server restarts. Independent calls can run concurrently on one transport; operations touching conflicting resources still coordinate through resource locks.
• Explicit messages to other chats use the task mailbox. Mailbox delivery does not automatically start the receiving chat.
• Active conversation tracking, review grouping and task selection prompts reflect the conversation's own task.
• Windows startup distinguishes stale ownership claims after PID reuse and reports the underlying startup error.
• The left sidebar stays within its column when a task description or handoff contains long identifiers. Environment controls, handoff timestamps and action buttons remain visible.
• Setup option 2 — OpenAI Secure MCP Tunnel is marked Recommended (Windows). The README covers access, installation, every wizard prompt, ChatGPT connection, repairs and upgrades.

Install or upgrade

Use Node.js 22+, npm and Git. The option 2 automatic installer requires Windows/PowerShell. Follow the complete README setup guide.

For an existing installation, stop its launcher, preserve .env, back up the configured WORKBENCH_PATH, and preserve local source changes before updating:

git fetch origin --tags
git checkout v1.0.1
npm ci
npm run build
npm start

Refresh the ChatGPT app/connector after the update and start a new conversation to load current tool definitions. Choose Advanced for multiple tasks; Basic retains its single-writer workflow. Existing saved connection choices are retained by setup.

Task permissions, workspace boundaries and conflict protection still apply. Workbench does not automatically resume other ChatGPT chats. Use separate worktrees when concurrent tasks need independent Git working copies.

Validation

• npm test — passed, including conversation routing, parallel execution, shared-task dispatch, permissions, Windows state ownership and restart recovery.
• node scripts/run-all-tests.mjs --readiness-only — passed with an isolated HTTP/MCP server.
• JavaScript syntax checks passed for the changed/new scripts and UI modules.
• Headless Edge rendering of the actual Workbench HTML/CSS with long task/handoff content reproduced the sidebar clipping before the fix. After the fix, checks at 1440, 1280, 1100, 900 and 414 px found no horizontal content overflow or controls outside the sidebar; the desktop render was also visually inspected.

Tunnel setup instructions were checked against the local wizard and official OpenAI documentation. A fresh account/tunnel installation was not performed as part of these release checks.

v1.0.0 - Basic recommended

v1.0.0 — Basic first

Released: 2026-09-14.

The first versioned release of MCP Plugins With ChatGPT Web brings project editing, review, approvals, persistent task context and optional parallel work into a local Workbench.

Recommended setup

Basic is the recommended experience for everyday coding. New projects use it by default. It offers the complete coding tool registry, a persistent project task, grouped changes, review and Undo/Redo. Advanced is available for multiple tasks, managed worktrees, preview runtimes and the integration queue.

Experience, permissions and tool profiles are separate settings. Basic does not mean read-only; Full does not automatically enable machine scope.

Included in v1

• Basic/Advanced experiences with one writer conversation per Basic project.
• Session-bound workspaces and tasks, managed parallel branches, previews and local merge coordination.
• Project-folder relocation and missing-folder detection that preserve task identity and recorded file history.
• Batched inspection, cursor-based process output and a slim MCP tool profile.
• Task handoffs available in slim; current-task summaries and bounded operation history.
• Recent auto memory within UTF-8 byte and line budgets; project skills loaded on demand.
• Optional conversational Ask/Auto/Full changes, enabled by the owner with WORKBENCH_REMOTE_POLICY_CONTROL=true.
• Setup wizard, local browser authentication, OAuth and tunnel helpers.

Correctness fixes included

• Workspace/task control requires Full with machine scope on the source task.
• Retargeting retains writer ownership while managed processes or preview leases are active.
• Approving an old handoff update detects a newer dashboard edit and preserves it.
• Pending file contents and raw arguments are omitted from bounded MCP history.
• Concurrent server instances cannot own the same Workbench state; crash recovery ignores claims belonging to dead processes.

Install or upgrade

Use Node.js 22 and Git. On Windows, PowerShell is also used by the included launchers.

git clone https://github.com/Mieruko/MCP_Plugins_With_ChatGPTWeb.git
cd MCP_Plugins_With_ChatGPTWeb
git checkout v1.0.0
npm ci
npm start

For an existing installation, stop its server, preserve .env and back up the configured WORKBENCH_PATH before updating the checkout. Do not discard local source changes. Run npm ci and npm run build, then start the server and refresh the connector's tool definitions.

Saved workspace experiences are retained; legacy workspaces without an experience value migrate to Advanced. Select Basic · Recommended in the experience dialog if you want the simpler workflow. Use a separate WORKBENCH_PATH for each concurrently running installation.

Boundaries

Release checks passed: npm test, npm run test:integration, and node scripts/run-all-tests.mjs --readiness-only. These include real local HTTP/MCP dispatch, two-session writer control, permission switching, stale handoff approvals, bounded history, state ownership and upstream proxy calls.

• Workbench Full controls this server's approvals. It cannot disable independent client/connector review.
• File Undo does not restore database, shell, Git remote or other external effects; handoff and permission metadata are not file Undo operations.
• Machine-scope processes use the server account's access. Docker sandboxing is optional and requires a locally available configured image.
• Session coordination covers Workbench-managed operations; external editors and detached processes remain outside those guarantees.
• Local HTTP/MCP tests exercise the release behavior. They do not certify every hosted ChatGPT connector or phone/browser configuration.

See the README for setup and experience documentation for coordination behavior.