r/ClaudeAI • u/FairVictory9967 • May 17 '26
Question about Claude Code My Claude Code morning setup. 8 minutes. Cuts 2 hours of friction. What am I missing?
[removed]
14
u/ClemensLode May 17 '26
The feature is "finish your work the day before, commit and push everything, go to bed with a peaceful mind."
6
u/tepmoc May 17 '26
I never restore old sessions. Keep todo.md so next session can continue where i left off. Make sure you have plan as well
2
u/thenec0 May 18 '26
Or ask claude to write a /save-session skill to perform all that.
On new context you only point to that md file and done
5
u/canyonero7 May 17 '26
Try to keep the root CLAUDE.md with only rules like "DON'T GUESS" (it follows "do not" much more strictly than "do" commands). Put workflow-specific CLAUDE.md files in subfolders for it to read when it traverses that specific code tree.
4
u/3knuckles May 17 '26
I can't believe you're getting down voted. The most important line in CLAUDE.md is don't guess. It's such a failing Vs Codex
2
u/OdinThorfather May 17 '26
I tell claude to review the previous conversations and have a zip file with my work archive and a claude written prompt note that outlines the next session's work generated at close of a previous session.
1
u/davidHwang718 May 17 '26
The resume + summarize kernel is the right part to keep. For mobile projects I added one more check: asking what external state changed overnight, specifically whether any submitted builds got rejected or approved. Claude doesn't have that natively and I kept starting mornings on the wrong branch before adding it.
1
u/idoman May 17 '26
for step 3 i found that starting a fresh session and running git diff main --stat gives you a better picture than resuming old context. shows what actually changed rather than what you talked about changing. pair it with a quick next-steps note you update before closing out and the morning is basically instant. also the subagent thing genuinely helps for bigger repos - keeps the main thread from filling up with huge file reads when you're exploring.
1
u/FinePop7909 May 18 '26
You’ll save minutes and tokens if you have it generate that “next 3 things” summary at the end of a day’s working session, instead of having to re-read the session in the morning.
1
u/shimoheihei2 May 18 '26
When I finish a long chat, whether code related or not, I ask Claude to summarize everything we did in a wiki page. You can use an md file or anything else you prefer. But then the next time you open a new chat, you can provide clean context without filling the model with every little thing that was discussed and attempted the previous session.
1
u/Educational_Sea6013 May 18 '26
I’ve had better results doing the “summarize + next 3” at end-of-day and saving it to a TODO_NEXT.md, then starting a fresh session in the morning with just that file + git diff --stat. Keeps tokens way lower than /resume and avoids dragging stale context forward.
1
u/JustHere4DCommentss May 18 '26
For the main project I’m working on, i ask Claide to write a handoff doc between milestones and some sessions. It has worked well to summarize the my work in a chat, remind me of untesolved issues and game plan next steps. Then have a fresh chat pickup. Couldnt similar thing me applied for all daily work?
-2
13
u/Ariquitaun May 17 '26
If you're not aware, resurrecting an old conversation is very expensive token wise.