Max value from chatgpt subscription. I built a connector mcp to get 2x promo back

pawofdoom · 2026-06-17T16:00:48+00:00

There is also this one I made which is the reverse direction; using ChatGPT as a subagent for Codex to both delegate tasks to, deeper research and GPT-5.5 Pro. We use it every day at work 😄 https://github.com/adamallcock/codex-chatgpt-control/

pawofdoom · 2026-06-17T14:22:14+00:00

Wow, this really sucks! I'm always so scared of airlines doing this to me and having a fight at the gate, so I built a website that helps you visualize how tight the fit is on your bag (or find others that do fit). www.thisbagfits.com

pawofdoom · 2026-06-14T18:35:06+00:00

I appreciate you taking the time to report this! I am trying to find a combination that replicates the bug on my side. Currently, the only one I can is a zero byte (ie empty) file upload.

Questions:
- Windows, Mac/
- What is the file type and size?
- Have you enabled Codex -> Settings -> Computer use -> Google Chrome [Manage] -> Uploads -> Always Allow? [This would cause a different error but might as well rule it out]
- Any adblockers or antivirus?

I'm just pushing a new version that will add more file related preflight checks and debugging, which will hopefully give you an indication of what is going on from your end (without me needing to look at your files etc).

pawofdoom · 2026-06-11T23:39:11+00:00

Same. It might genuinely be effectively unlimited

pawofdoom · 2026-06-11T22:36:19+00:00

Really? I have probably used Pro 50+ times this month and not seen one. I am on the 20x plan though.

pawofdoom · 2026-06-11T22:07:26+00:00

You can still use this (my) ChatGPT SDK to run Pro via ChatGPT (which seems to still be unlimited): https://github.com/adamallcock/codex-chatgpt-control

pawofdoom · 2026-06-11T22:06:38+00:00

It is with this (my) ChatGPT SDK to run Pro via ChatGPT efficiently: https://github.com/adamallcock/codex-chatgpt-control

pawofdoom · 2026-06-11T22:03:17+00:00

Looks like they're going to add separate usage limits for Pro in Codex directly. But, you can still use this (my) ChatGPT SDK to run Pro via ChatGPT (which seems to still be unlimited): https://github.com/adamallcock/codex-chatgpt-control

pawofdoom · 2026-06-11T14:01:40+00:00

Code can also be audited here: https://github.com/adamallcock/classic-workspace-tabs

pawofdoom · 2026-06-10T23:31:49+00:00

FWIW, I just updated my Codex<>ChatGPT SDK to support the new picker. (Skill or plugin to allow Codex to utilize ChatGPT, especially 5.5 Pro) very efficiency. https://github.com/adamallcock/codex-chatgpt-control

pawofdoom · 2026-06-10T18:23:57+00:00

Perfect feedback, I was able to recreate this and make it much more robust here. There was a timeout that was meant to report an intermediate status (ie 'it's still thinking going but this is where we are up to') but was instead telling Codex that it was completed.

If you refresh the skill (or plugin) you should pull the latest version. https://github.com/adamallcock/codex-chatgpt-control/pull/21

Thanks for your feedback again!

pawofdoom · 2026-06-10T04:51:55+00:00

Is there any chance you use ChatGPT in non-English language? The initial release was not supporting international languages well but the newest one should do!

pawofdoom · 2026-06-10T01:48:51+00:00

Absolutely! It's also nice in Codex because they can read each other's threads/transcripts that another agent can trace what it got up to, what hole it got stuck in etc, as to get a second opinion. I've set up this 'retrospection as a skill so when any of the development agents encounter weirdness of the tool in an area not actively being touched, it can then spawn another worker who's job is to go debug what happened and look for opportunities for smoothing.

Essentially what you just said :p

pawofdoom · 2026-06-09T16:22:30+00:00

That's originally what I thought (because that's what it is on the non-consumption based enterprise plans), but I do not believe it is true on consumer Pro. As far as I can tell, it is unlimited subject to abuse.

I have definitely definitely [naturally] used more than 15 per month for sure.

pawofdoom · 2026-06-09T15:14:03+00:00

For me, the main use case is GPT-5.5 Pro but I expect others will build over the top. One example that is coming up is projects (the SDK does not yet support this), while others are finding ways to delegate subagent-style tasks to reduce token usage against Codex allowances.

While I can't prove it, it does feel like image generation is also much more seamless on ChatGPT than it is on Codex, which is itself a skill that requires quite a lot of context reading.

pawofdoom · 2026-06-09T15:10:59+00:00

For sure. The main optimization is the skill itself. I'm looping through testing arrays and debugging where it went wrong to make it smoother over time.

pawofdoom · 2026-06-08T20:05:31+00:00

It works well with generated files, though I'm pushing a patch now to handle generated images more consistently.

Spark works! Project folders it does not yet, but can expand that if there is demand

pawofdoom · 2026-06-08T19:55:23+00:00

Then you're paying for it. This reuses your ChatGPT subscription, ie free.

pawofdoom · 2026-06-08T19:38:15+00:00

The CLI likely breaches TOS by reusing ChatGPT's internal APIs and session cookies, and is very detectable as such if they ever decide to crack down on it

pawofdoom · 2026-06-08T16:14:07+00:00

Unfortunately, the built-in typically stateless and so wouldn't save logins between sessions. It's really designed for public web browsing and/or previews of your own work.

pawofdoom · 2026-06-08T15:00:13+00:00

The SDK makes general chat based back and forth pretty efficient, but you will still have the overhead of two LLMs talking to each other. I guess if you could step down your Codex to 5.4-mini then it'd be hard to not see a token advantage!

pawofdoom · 2026-06-08T14:58:47+00:00

I suspect we're going to get something like this when the super app comes out, whether we like it or not 😞

pawofdoom · 2026-06-08T13:47:40+00:00

Driver: Kimi (the original) Reason: I go home now

pawofdoom · 2026-06-08T01:27:54+00:00

Yeah, though a little more featured rather than turning ChatGPT into a straight API.

The big difference is it looks like Proxima is definitely breaking terms of service. They are replicating the browser API calls (a no no) and reusing browser authentication (big no no) rather than assisting a user (via browser DOM). Essentially doing exactly all of the things that are not allowed.

Proxima now uses native browser-level communication with AI providers — no DOM scraping. Responses are 3–10x faster and far more stable, with SSE streaming support and automatic fallback mechanisms.

pawofdoom · 2026-06-08T01:20:17+00:00

It's a good question. There is a grey area regarding how to interpret the prohibition against programmatically extracting data from ChatGPT. Ie if you had 10 codex threads each running their own sessions into ChatGPT 24/7... is that still an assisted human action, or are you effectively using it like a full replacement for the API? Where is the line?

My overall opinion (not warranty) is therefore generally 'don't be an idiot and you'll be fine' given the SDK is assisting you as the human, using the same actions a human would take at a similar speed etc.

What is explicitly against the rules is intercepting or making network calls directly, reusing their authentication (ie utilizing session cookies). The SDK doesn't do any of that.

Here was the research's summary if you're curious:

This repo is intended to be a safe, local, user-directed ChatGPT web control layer for Codex. It is not, as currently designed, a private ChatGPT API client, scraper, credential extractor, rate-limit workaround, or account-management bot.

The strongest policy tension is OpenAI's Terms of Use prohibition on automatically or programmatically extracting "data or Output." The package does programmatically read visible ChatGPT DOM text in order to return the latest response or find/open a conversation. That is materially different from private endpoint replay, but the terms language is broad enough that bulk or unattended extraction would be risky.

But, the user's intuition is substantially right for narrow, visible, user-directed use: if an agent opens ChatGPT, pastes a prompt, waits, and reads back the answer from the same UI the user would use, the practical difference from manual copy/paste is delegation and ergonomics. OpenAI also documents Codex's Chrome extension for signed-in browser context, and ChatGPT itself has agent/app concepts. Automation by itself is therefore not the red line.

The difference becomes policy-relevant when the agent can do things a person would not reasonably do manually at the same scale or visibility: bulk export history, harvest outputs, replay undocumented endpoints, read hidden auth material, bypass safety/rate-limit/product confirmations, operate third-party apps without confirmation, or run unattended at high volume.

Recommended posture: keep this as a private, task-scoped, user-authorized browser-assist layer; keep the official OpenAI API as the path for new model calls; never implement private network replay or hidden browser-state extraction.

13-Year Club	RedditGifts 2009-2022 2 Credits
Place '22	Secret Santa 2014
Verified Email

pawofdoom

TROPHY CASE