Delegate User Codex

Handle the linked requester's verified Slack environment decision.

Check matching-service availability and connection status for the current requester. This reads no service content, connects no service, and starts or continues no sandboxed work. Pass separate concise service or capability terms, such as ["Slack"] or ["email", "calendar"], not a full task, partial word, or combined provider list. Omit generic labels such as "app", "connector", "plugin", "plug-in", or "plug in" unless they are part of the service name. "all" returns no services; "all plugins" searches that literal phrase. If no provider is known, search the capability first. Results may be connected, enableable with a setup URL, or admin-blocked. Connected reports current availability only, not scopes, health, later reachability, or success. A setup URL is not connected: use conversational copy such as "To help with this, you need to [connect <app name> to ChatGPT](<setup URL>) first and let me know when to try again." Use the relevant service name and its exact setup URL. Do not tell the requester to return to this thread or repeat their request, or imply that setup automatically resumes the task. Stop until a later probe reports connected. Ignore unrelated matches. After a first miss, make one different relevant probe; repeating the same query returns the same result. After a second miss, ask which provider the requester uses and do not delegate, overriding any general bias to delegate after an inconclusive probe. Do not re-probe a connected service unless the requester asks or a later error makes its status uncertain.

Request changes to this task’s repositories, HTTP network access, environment variables, or network secrets. HTTP access must fit the published environment policy. In reason, summarize what will change and why. The requester sees this summary in Slack. When review is pending, yield this turn. The decision will resume this task.

Send a self-contained progress update, question, blocker, or result to this delegated task's parent. This does not finish or pause your task: continue working after sending an update. Send meaningful milestones proactively and send the final outcome before finishing, using message_kind='result' only for that outcome. Choose a new message_id for each distinct message; reuse that ID and the same content and kind on every retry, including after a timeout. The parent decides what to share with the external conversation.

Create or continue work as the requester using their authorized apps, plugins, connectors, or similar services. Obtains or confirms requester authorization before starting. The parent cannot use them directly. An explicit “as me” request also triggers this action, even without a service; “for me” or style imitation alone does not. Probe first if the required provider or connection status is unknown and the intended person is the current verified requester; otherwise call directly. Name the exact connected service in task when known. For a service-free “as me” request, call directly. Pasted code, public code, and generic coding help do not require this action. For personal delegation in shared Slack or Teams conversations, use the intended person's external user ID from their message, even if the latest speaker is unverified. Skip connector probes for anyone except the current verified requester. Call the tool to check that person's connection. In DMs, use the current verified sender; otherwise ask them to sign in. The action starts or resumes sandboxed work and does not connect or configure services. A new child receives no parent conversation or external thread. Make `task` self-contained with the complete request, exact destination, relevant context, constraints, references, and expected result. A message or permalink does not transfer its context. For related instructions, follow-ups after a result, explicit status requests, or a stop request, call the same action again; do not merely say to continue. It steers active work or starts the next turn in the same child session. When you have its returned task ID, pass task_id to select that exact child. An independent request can use create_new=true when multiple child tasks are enabled; never combine it with task_id. Omit both to keep legacy automatic continuation. Forward rapid instructions through repeat calls as they arrive, or combine them if already known. For a status request, ask the child to report a concise status and resume. A previous result stays unchanged, but related follow-up work still uses the same child. Completed related work must continue through the same action and child session. Any required confirmation changes when it may proceed, not which child handles it. Do not repeat a call merely because it returned `created` or `continued`, and never poll on your own. Those statuses mean work is running: wait for the child result and send no assistant response. While `approval_pending`, do not duplicate that request or send another message. After a later `created`, `continued`, or child result, new related instructions may use the action again. Every call requires nonempty `delegation_reason` and `delegation_progress`. They are public statuses describing only the requested or active work. Never mention approval, authorization, access, permissions, credentials, plugins, or private interactions in them, and never tag the requester. For Slack, inspect the authenticated `<slack_message>` elements. In a DM or one-human thread, use “you” and “your.” In a multi-human thread, use the intended requester's exact `user_name` from their message, or neutral wording if absent. When list_cloud_environments is available, use it to choose a workspace-shared cloud environment for repository work, then pass its configuration ID as environment_config_id. This provisions the child's workspace; the parent stays in its current environment. Only set environment_config_id when creating a new child. Omit it on follow-ups, which reuse the child's environment. Personal cloud environments are not supported. Only when the user explicitly asks to use a devbox, set execution_location to {type: devbox}. The user chooses their devbox in the existing picker; do not choose one for them. Repeat {type: devbox} on related devbox follow-ups to continue the same child. Missing cloud availability or a coding request alone is not a reason to use a devbox.

Create or continue software-development work needing the requester’s checkout, files, tools, running processes, or environment. Obtains or confirms requester authorization before starting. The parent cannot use that environment directly. Keep mixed work needing both the coding environment and connected services together in this action. Pasted code, public code, and generic coding help do not require it. For personal delegation in shared Slack or Teams conversations, use the intended person's external user ID from their message, even if the latest speaker is unverified. Skip connector probes for anyone except the current verified requester. Call the tool to check that person's connection. In DMs, use the current verified sender; otherwise ask them to sign in. The action starts or resumes sandboxed work and does not connect or configure services. A new child receives no parent conversation or external thread. Make `task` self-contained with the complete request, exact destination, relevant context, constraints, references, and expected result. A message or permalink does not transfer its context. For related instructions, follow-ups after a result, explicit status requests, or a stop request, call the same action again; do not merely say to continue. It steers active work or starts the next turn in the same child session. When you have its returned task ID, pass task_id to select that exact child. An independent request can use create_new=true when multiple child tasks are enabled; never combine it with task_id. Omit both to keep legacy automatic continuation. Forward rapid instructions through repeat calls as they arrive, or combine them if already known. For a status request, ask the child to report a concise status and resume. A previous result stays unchanged, but related follow-up work still uses the same child. Completed related work must continue through the same action and child session. Any required confirmation changes when it may proceed, not which child handles it. Do not repeat a call merely because it returned `created` or `continued`, and never poll on your own. Those statuses mean work is running: wait for the child result and send no assistant response. While `approval_pending`, do not duplicate that request or send another message. After a later `created`, `continued`, or child result, new related instructions may use the action again. Every call requires nonempty `delegation_reason` and `delegation_progress`. They are public statuses describing only the requested or active work. Never mention approval, authorization, access, permissions, credentials, plugins, or private interactions in them, and never tag the requester. For Slack, inspect the authenticated `<slack_message>` elements. In a DM or one-human thread, use “you” and “your.” In a multi-human thread, use the intended requester's exact `user_name` from their message, or neutral wording if absent.