Skip to content

[Bug]: Erroring out while launching a subagent when provider is using the "ChatGPT Sign In via sharing usage limits" #17708

Closed as not planned
Closed as not planned
[Bug]: Erroring out while launching a subagent when provider is using the "ChatGPT Sign In via sharing usage limits"#17708
Labels
bugSomething is broken or behaving incorrectly.duplicateThis issue or pull request already exists

Description

@justusrk
justusrk
opened on Oct 10, 2026

Before submitting

  • I searched existing issues and did not find a duplicate.
  • I included enough detail to reproduce or investigate the problem.

Area

apps/web

Steps to reproduce

  1. Have provider with Sign In with ChatGPT - so T3 Code now uses via "Sign in with ChatGPT"
  2. Give task that launches a subagent.

Expected behavior

The subagent should be able to run normally and return back with the response.

Actual behavior

The subagent spawning fails and we see "Codex used a feature that ChatGPT sharing does not support. Use another provider for this request" The subagent panel says the subagent failed.

Impact

Blocks work completely

Version or commit

No response

Environment

macOS 15.8.1, T3 Code 0.0.45

Logs or stack traces



Screenshots, recordings, or supporting files

Image

Workaround


No workaround if I want to use a second ChatGPT account on my machine.
Activity
  1. justusrk
    added 
    bugSomething is broken or behaving incorrectly.
     
    needs-triageIssue needs maintainer review and initial categorization.
     on Oct 10, 2026
  2. juliusmarminge commented on Oct 10, 2026 
    @juliusmarminge
    juliusmarminge
    on Oct 10, 2026
    Member
    Note
    Grok responding on behalf of Julius.
    

    

    Thanks for the report! This is the same failure tracked in #17679: with "Connect with ChatGPT" (subscription sharing), spawning a Codex subagent gets rejected with subscription_sharing_unsupported_capability, and the chat can't continue. Closing this as a duplicate so we keep discussion in one place. Please follow #17679 for updates; there's an open fix in #17499.
  3. juliusmarminge
    added 
    duplicateThis issue or pull request already exists
     and removed 
    needs-triageIssue needs maintainer review and initial categorization.
     on Oct 10, 2026
  4. juliusmarminge
    closed this as not plannedon Oct 10, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Metadata
Metadata
Assignees
No one assigned
    Labels
    bugSomething is broken or behaving incorrectly.duplicateThis issue or pull request already exists
    Type
    No type
    Projects
    No projects
      Milestone
      No milestone
      Relationships
      None yet
      Development
      No branches or pull requests
      Issue actions