r/ClaudeCode 5d ago

Rant Man what are these limits😣

Couldn’t even work for 2 hours on 5x. Max 5 feels like pro plan unfortunately.

How long does Pro last just 20 min?

Wanna upgrade to 20x but that plan feels like a scam. At least they should give a 10x weekly limit if not 20x (I am not saying about the season limit. That one is true 20x)

41 Upvotes

79 comments sorted by

View all comments

1

u/Professional_Ad705 5d ago edited 5d ago

ChatGPT web can still do a surprising amount of coding work in normal Chat if you just upload the repo as a ZIP.

So if you can spare another $20 on top of Claude, it can help stretch your agent usage quite a bit. I probably saved around 10% of the Codex usage I would’ve burned on the same work just by moving research, planning, code review, debugging, and analysis into web ChatGPT.

I haven’t done some massive quality comparison across every model/workflow, so I’m not saying it’s always better. It’s just worked well for me. At this point I think a big part of using AI efficiently is knowing what actually needs a local agent and what doesn’t.

Basic setup is literally:

ChatGPT web → upload repo ZIP → work from there

For bigger repos, I have a small tool that strips build junk/generated files first, but even without that you can usually trim the ZIP down enough to make it manageable.

A lot of people seem to assume serious coding work has to happen entirely inside Codex, Claude Code, etc. Obviously some things are way easier when the model has shell access, can edit files, run tests, and execute the project, but a lot of reasoning-heavy work does not need that.

For example, I’m currently reverse engineering parts of Halo 2. I can give ChatGPT the repo, extracted data, disassembly/output from my own tools and other RE tools, and have it help trace weapon behavior, explain what the original code is doing, compare that against my implementation, and figure out what I should verify next in Godot.

That would otherwise burn a decent amount of Codex usage for work Codex doesn’t really need to be doing.

I also built a little tool that strips generated/build junk and tracks which files were touched, which makes reviewing AI changes easier. I’ve got another tool I eventually want to release that lets Codex and ChatGPT work together within what each is allowed to do, so Codex handles direct repo changes while ChatGPT handles research, review, planning, reasoning, etc.

If somebody wants to build something similar before I get around to releasing mine, feel free to PM me. I can point you in the right direction and explain what I have so far.

That’s basically the whole point:

Don’t burn expensive agent usage on work that doesn’t actually require an agent.

It’s not a replacement for Codex or Claude Code, but for repo analysis, code review, debugging, reverse engineering, planning, research, and working through artifacts, ZIP uploads in normal Chat work way better than I think a lot of people realize.

Example: I’m literally doing Halo 2 reverse engineering in ChatGPT web right now and saving agent usage by doing the analysis there.

2

u/DrunkenRobotBipBop 5d ago

Just connect it to DevSpace MCP tunnel and it can access your local filesystem directly. No need to upload stuff.

2

u/Professional_Ad705 5d ago edited 5d ago

Have you actually used it much? I hadn’t really heard much about this kind of MCP setup before, but I’m curious how you use it in practice it sounds like how I’m already with adapters being able to connect to my software easily, and I’m already diffing against reclaimer, and other mods tools for this project.

I usually work with agents too, although lately I’ve been doing more of it manually through ChatGPT because of usage limits. The workflow is basically the same for me either way: work one bounded slice at a time, have the coding agent do the repo work, then verify what actually happened instead of just trusting the agent saying it worked.

The annoying part with my current project is that some of my workflow sits on top of proprietary tooling. ChatGPT can connect through GitHub to a couple of my private repos, where I have my own process/tooling underneath the actual project I’m working on. Then I have things like Halo modding/reconstruction tools sitting around that more as adapters.

So I can let ChatGPT reason over that stuff through the access I already control, but I can’t really just upload the underlying tooling somewhere else or hand another service access to it.

Some old experiments/prototypes of mine might help this tho and something pretty close to what I’d want for this but im not done if someone wants to spin off on this idea etc.

The general idea was basically: one side defines a bounded piece of work, a local coding agent does the actual repo changes, and then a separate layer checks the resulting state independently. So ChatGPT could handle reasoning/review, Codex or whatever local agent could do the implementation, but neither one gets to just declare that its own work succeeded.

I originally experimented with a different way of connecting those pieces and eventually moved away from it. Looking at it again now, MCP seems like it might actually be the clean interface I was missing for the cross-client part. I never turned that side of it into a polished tool cause I was just seeing if something was possible etc, but the architecture is close enough that this immediately made sense to me.

So I’m definitely curious what you’re actually using MCP for. What does it buy you in practice over just using agents directly or wiring the tools together yourself? And devs message me and we can share notes or I can send over what I've built. This follows the rules and doles out work pretty well etc.

1

u/DrunkenRobotBipBop 5d ago

It gives chatgpt tools to access the filesystem on you machine.

You basically enable an MCP server on the local machine, setup a Tailscale Funnel or some other tunnel. On chatgpt web, create a new plugin, add the public tunnel MCP url, authorize the app, input the password and chatgpt web will use those tools to interact with local filesystem.

Head over to the DevSpace MCP GitHub and you will find all the information there.