WebGPT — скилл

---
name: webgpt
description: Delegate work to signed-in Web ChatGPT when the user requests WebGPT (m/medium, h/high, xh/xhigh or p/pro), or open a user-controlled project terminal chat with webgpt open.
---

# WebGPT

Delegate bounded work to save Codex usage. User instructions about division of work, model,
monitoring, permissions, follow-ups and retention override defaults. Never silently take over
WebGPT's assignment; Codex may perform separately assigned work concurrently.

Keep Codex ↔ WebGPT coordination in English, preserving source quotations and the requested
deliverable language. Reply in the user’s language unless they request another; leave browser UI language unchanged.
**Every conversation must use Chat, never Work**, including setup tests, browser-only work and
`open`. Verify Chat before composing or selecting a connector; return to Chat if a shortcut opens Work.

## Route

- `webgpt open [path]`: follow [open.md](references/open.md); skip delegation below.
- Worker delegation: read [workspace.md](references/workspace.md).
- Explicit browser-only work: use [browser-reply.md](references/browser-reply.md); skip Worker commands.
- Read [setup.md](references/setup.md) only for installation or missing capability, and
  [recovery.md](references/recovery.md) only for actionable exceptions or same-chat follow-ups.
  Client tunnel/connection errors require setup's origin recovery before dispatch.

For Worker tasks, register first and use the returned `connection.name` and `connection.registrationId`.
With `connection.status: ready`, skip configuration/setup reads, directory searches and Plugins
rediscovery. Missing/invalid metadata routes to recovery.md; keep the registered task, do not register again.

## Delegate

Assign one bounded deliverable with its relevant tests per new chat. Investigate only enough to
specify the objective, context, constraints and success criteria; leave routine commands to WebGPT.
Avoid open-ended projects, arbitrary duration limits and separate chats for tiny actions. Assign
file ownership/worktrees for concurrent changes. No duplicate task documents or tracking files.

Prepare one concise English prompt before opening the tab: task, necessary context/constraints and
success criteria. Reference accessible project briefs by path instead of restating them.
For Worker tasks, add the named connector/task token and “Save the final outcome
through the Worker.” Tool schemas supply the completion protocol; do not repeat it. Never send the
controller key or connection URL. Retain task and owned chat/tab identifiers in context.

Use documented browser initialization; reuse known browser identity without scanning all surfaces.
For Worker tasks, select the existing connector in Chat by verified registration ID, or
use a verified Chat launch URL. Mentioning a connector in prose does not select it.