Dave

Value investment enthusiasts

[Dave @minghuili14]

@wh0sumit @dharamlokhand Sounds like the process probably isn’t the issue — sticking to it is. Do you already have a clear SOP for delivery, or is the team mostly handling things case by case?

[Dave @minghuili14]

@Attickk Feels like you already know enough — the hard part is actually sticking to it. Are you following any one course or playbook right now, or just picking things up from different places?

[Dave @minghuili14]

@ole_yasura 13 projects is a rough way to learn that 😅 What are you using to learn marketing now — a course, a book, or just figuring it out as you go?

[Dave @minghuili14]

@mmmstudio_ That “summary only” constraint is what I’m curious about too. I built a handoff that preserves goal, progress, decisions and next steps. Would that still be useful, or does native messaging already cover it?

[Dave @minghuili14]

@Iammdshohag This is exactly the workflow I built a handoff tool for 😅
Do you think Claude’s new session messaging makes this completely unnecessary now?

[Dave @minghuili14]

@aibuilderclub_ I built a small handoff tool for exactly this — preserve the important state and continue in a fresh session. Curious if Claude’s new session messaging makes this unnecessary now?

[Dave @minghuili14]

@vikhyatk @cheatyyyy Same here. I’m testing a handoff that carries the important context into the new session. Would this be useful for you?

[Dave @minghuili14]

@PirouneB @thsottiaux I hit this too. I’m testing a handoff that saves the important state before starting fresh. Would this help when /compact fails?

[Dave @minghuili14]

@ArthurODS_ @thsottiaux I’ve been testing a slightly different approach — instead of trying to keep the same context alive, preserve the important state and hand it off to a fresh session.

Curious if you’d prefer that, or automatic compaction inside the same session?

[Dave @minghuili14]

@eyalccohen @ClaudeDevs I hit this too. I’m testing a handoff that keeps the important state when starting a fresh session. Would this solve the annoying part for you?

[Dave @minghuili14]

@md_kasif_uddin The “remembers nothing” part is exactly what I’m trying to fix. I made a small demo that carries the important state into a fresh session instead of starting from zero.

Would this actually be useful in your workflow?

[Dave @minghuili14]

@Maitreya0lzd This is exactly the part that annoys me too — not the context limit itself, but having to rebuild everything in the next session.

I’m testing a small handoff tool that preserves the important state before starting fresh. Would this actually solve the annoying part for you?

[Dave @minghuili14]

@Rent0j I built a small demo around this exact problem — instead of manually starting over, it carries the useful state into a clean session. Curious if this solves the right problem or if I’m missing something.

[Dave @minghuili14]

@bullbear_info This is exactly why I built this. When a Claude Code session gets messy, it carries the useful context into a clean session instead of starting over. Would you actually use this?

[Dave @minghuili14]

@N0V4Dev I’m testing a simpler version of this idea: preserve the useful state, then continue in a clean session. Would this be useful, or does GSD already solve it for you?

[Dave @minghuili14]

@parasdoshi9 I’m testing a different approach: when context gets messy, carry the useful state into a fresh session instead of keeping the full window. Would you use this for long-running tasks?

[Dave @minghuili14]

@aDeViliNMe @MangoSweet78 “Poisons its own context” is exactly the failure mode I’m testing around.

I mocked up this approach: extract the useful state and continue in a clean session. Would you actually use this?

[Dave @minghuili14]

@pomis172 I keep hitting this too. I’m testing this approach: preserve the important state, start a fresh session, and continue without rebuilding context.

Would this solve the annoying part for you?

[Dave @minghuili14]

@WillNessAI Curious what you think of this approach: instead of custom compaction, create a structured handoff when a session gets too large and continue fresh.

Would you actually use this?

[Dave @minghuili14]

@deegeevince I’m testing a lighter version of this: turn the useful parts of a session into a structured handoff for the next one, instead of storing everything.

Would this be enough for you, or would you still want the full history?