heyvivbuilds
Region: US
Wednesday 17 June 2026 22:07:45 GMT
3048
125
104
2
Music
Download
Comments
Jah Feel :
you have to structure your folders to have the context needed so that you literally never need a handoff.
2026-07-23 00:23:45
0
Where Is Brad :
Handoff way sooner - try at a stopping point, but if I get to 40-50% I handoff. I haven’t compacted in months. Even before compacting at 60%+ context window you’re already getting poor performance and poor efficiency and high token usage. Handoff way earlier
2026-07-08 22:23:06
2
James :
Commit your changes. Scroll up and edit the last message that successfully produce a response and edit that message to ask for a hand-off.
2026-06-17 22:18:33
20
Places to Breathe :
Create a folder that holds all memory. Tell your agent to save all memory and prepare a handoff in a new session - level up - always know when you’re getting close to full - when the handoff is ready verify memory is updated inside your folder on desktop and then ask for master prompt for new session
2026-06-27 17:20:30
3
Mountain man :
Hook up Gmail and let Claude write and read to Gmail as saved memory. It is massive compared to native memory.
2026-06-20 13:18:12
4
ChasingGnosis :
You need a 2nd Brain system. Check my GitHub (link in bio), I have a /start /sync /wrap system that keeps everything sorted.
2026-06-18 04:18:05
4
Errol :
I know this doesn’t help you now, but I’m a militant pre-scoper. We discuss what we’re doing before any code is generated/altered and decompose the deliverables to the smallest bits. I go as far as reading the .md files before I even start up a new session
2026-06-18 06:13:30
6
Jonny :
Have Claude write the plan to a markdown and update the markdown file as it goes. That way if you lose your session or it gets too long you can just clear it and have it pick right back up where it left off.
2026-06-18 20:48:51
4
cliffrosen185 :
I generally transition to a new session by around 40% of context. For where you wound up, you could /rewind to a point where compacting works
2026-06-18 02:16:46
2
Calvin :
When I get 3/4 of the way through the context window I have Claude write up notes of what it’s goal is, what it’s tried so far, and what it thinks next steps should be. Then I clear context and have the new session read the notes and ask how it wants to proceed. You should skim the notes too. Sometimes there’s a fundamental misunderstanding of the problem that you can correct.
2026-06-18 16:10:19
3
builtbyjess :
Yup, handoff. I also try to separate my chats as well. For example, one for building, one for strategy, etc... it's too many to remember but, it helps so I don't have to keep handing off.
2026-06-17 22:33:42
5
David Fontenelle :
Make a chat a supervisor and one the worker. Let the supervisor chat give instructions and get updates form the worker chat or coworker… ext that way one chat hold the memory and can tell a bee chat where to pick up from.
2026-06-18 12:50:54
2
Richard B :
Start a new session with Claude or whayever model you want and have it parse the Ai Operations pages in the tensaengineering.dev website. Then ask it to build you a system that solves this problem and gives you session continuity.
2026-06-19 00:42:18
2
Joe Feser :
Use codex
2026-06-19 02:21:14
1
userusergitgit :
Check usage. Might be out of tokens already. I start a new session and ask it to pick the project back up and give it an original prompt to tell it to make it stored in a manner that can be resumed by any new agents/sessions.
2026-06-18 18:33:42
1
Newbxxy :
Start over. If you've gone that far down the rabbit trail, it will lead nowhere productive.
2026-06-18 14:00:32
2
Crisco_Alpha :
sidenote: I havent tried this but, if you switch models to a 1M model to compact, then ask it to summarize and save the session to a file, maybe that might help?
2026-06-18 13:29:15
1
LaurenMann0405 :
I wouldn’t say I’m experienced, I’m not quite a year in, but I only let a chat go for about 15-20 messages before I ask for a handoff and start a new chat. 🤷🏻♀️
2026-06-18 03:23:44
3
Stanton :
Are you working in an IDE, or Claude Code desktop? Or CLI? I might have a solution for you.
2026-06-18 14:58:57
1
MetalDrgn :
you need to go back and edit a previous response where it can capture information to a file for a new session
2026-06-18 23:09:30
1
billy7217 :
you can copy the whole chat into a txt file and have the next chat read it.
2026-06-27 21:59:30
1
buildwithadamai.com :
If the chat is inside of a project just start a new chat session lol unless Claude doesn’t have project awareness
2026-06-18 13:16:23
2
Pete :
checkpoint, update docs. clear chat. create audit, document, remediation, resolution, research improvements, loop until 100% deliverable.
2026-06-19 00:15:38
1
coena.creates :
You might go up to some of the conversations and put in there what didn’t work and kind of get a starting point. Are you using Claude cowork? Also, what about copying some of your files into ChatGPT and having them give you a summary of what you have tried.
2026-06-18 02:41:23
1
Knight_Trader :
I would start over. Sometimes when the context window gets too long the model can lose sight of a goal and end up working on smaller trivial things that it knows it can fix. New session brings a fresh set of eyes.
2026-06-23 16:34:46
1
To see more videos from user @heyvivbuilds, please go to the Tikwm
homepage.
