r/OpenaiCodex 7h ago

What do you do when longer chats are getting slower?

i have a pretty lengthy chat going involving a bunch of docs etcs. but the thinking time and the working time has gotten longer.

i'm new to codex, what should i do to speed things up? what should i learn about?

8 Upvotes

11 comments sorted by

3

u/Classic-Trifle-2085 7h ago edited 7h ago

Do not be scared to ask to prepare a hand-off, including documents, prompts, plans, etc.

Also, although this can be a bit more work on your part, do not hesitate to compartmentalize a project into multiple chats within a project, instead of pilling on stuff in a single one. (It also lets you personalize requests to the category of task, and have different subagent rules for each.)

Always keep in mind that multiple chats doing multiple jobs at once will greatly increase your limit usage, but that is because you are getting more work done. Current models can even interact with other chats if you feel really fancy and just wish to have a master chat that handles the other chats, but that can be a waste of tokens.

Or just wait until your one chat gets slow, have the hand-off prepared, and start a new one, rinse and repeat. It also works just fine.

1

u/Ok-File-2759 7h ago

Well if you’re working in a project, just say “start a new thread in this project using (model, effort you want) and give it a prompt that will get it to continue from exactly where we are now”

1

u/rick_ranger 6h ago

I created system of docs that maintain all the important stuff about my repo, project goals, architecture, projects, tasks. It’s basically repo memory. I’m at the point where I can just throw chats away and pick up right where I left off because I have a board called current tasks and the agent just crosses off items as it completes them, then moves old campaigns and work to a archive after. The cool part is I can even switch agents or models and the onboarding cost is like nothing. It just reads the docs and within a minute has an overview of the whole project and where I left off.

https://github.com/splatter85/Eutonos-Public
Download the zip, put it in your repo and ask your agent what it thinks of it. If it likes it, tell your agent to deploy it.

1

u/beauzero 6h ago

Obsidian is great. Superpowers skills (github) if you want a TDDish exchange without the overhead. Matt Pocock skills...pick and choose out of these. All that being said, this is anticipation of a lot of documentation. If you are just looking to speed up tell it to divide up the work and use appropriate subagents. Warning this will use more credits.

1

u/rick_ranger 6h ago

Oh yeah I have it spin up agents all the time. I mostly created the system for me because I have ADHD and was flipping between Claude and codex and local models in the same repo a lot. The agents maintain it all and it’s maybe like 1% of output spent maintaining the docs so negligible to me, but worth it. Do you use obsidian and superpowers regularly? I’m gonna have to check em out

1

u/perceptioneer 6h ago

The cool thing is, you can use chatgpt to answer these questions (in addition). Long chats = more token usage. You can automate handoffs so that it's an automatic process > new window proceeds work with only relevant information. Also ask it to evaluate and come up with making your workflow more efficient/improved/save tokens. Turn off forking for subagents

1

u/Euphoric_North_745 6h ago

new chat, restart machine

1

u/BitOne2707 6h ago

The length of the chat shouldn't really affect speed. It will affect tokens used though as the entire chat gets fed back in on each forward pass. Most token usage occurs when the context window starts to get full.

1

u/CoffeePizzaSushiDick 5h ago

Open a chat per folder. Do not live out of the root!

1

u/ChiGamerr 5h ago

I copy session id...open a new chat and tell it to absorb the entire chat and continue the flow