Dev shares 3 ChatGPT context-saving tricks, then asks how to handle overflowing project context
BlueLovag · reddit · 2026-11-12
A 27-year-old developer with a graphic design, frontend and e-commerce background shares a year's worth of ChatGPT resource-saving tricks, then asks for help with a growing problem:
Three context-saving practices
- Convert formats: have ChatGPT turn PDF invoices into CSV and docs into Markdown instead of re-processing original PDFs each time.
- Keep a TL;DR alongside extracted data; only consult the CSV/original when the summary isn't enough.
- Voice-dictate thoughts into a patch list plus a to-do list, with a rule that code changes only happen after explicitly saying "green light".
The problem: his Rust + Godot game project has grown so large that web ChatGPT's context fills up after one to three tasks, with GitHub read/write operations adding overhead — a single push request can exhaust his usage. He's considering having ChatGPT package changes into a ZIP for manual commits, and debating a switch to Codex (which works locally) while worrying about giving AI access to his machine — should he run it in WSL?
More from coding & agent
- antirez: AI code generation now works when task boundaries are clear — antirez · 2026-11-12
- One-prompt 3D Solar System: Qoder's new Qwen4-Max-Preview builds an explorable browser universe — hey_abusiddik · 2026-11-12
- Giving agents a whiteboard: Claude Code crew plans on a shared Excalidraw canvas for $0.36 — pramodk73 · 2026-11-12
- AI agents automate the grunt work engineers learn from — how to train the next generation? — bendee983 · 2026-11-12
- KEEL, an Open Standard for AI Coding Project Docs, Launches keel.to — DominusFL · 2026-11-12
- PyTorch 2.15 regression slows LU solver up to 100x, warns researcher — ducha_aiki · 2026-11-12