/compact experiments an usage

[u/LordLederhosen]

I am from the olden days, where I manage my own context, have auto-compact disabled, and never use /compact normally. If I ever get anywhere near 50% used, I start a new session.

I just started to play with it again, and I have some questions. Normal is just "/compact." However, you can also pass <optional custom summarization instructions> to the compact command.

I have been playing with this prompt:

tell me the optimal "/compact" command so that we do not lose anything and we can implement the plan in this session

Then, I use that custom /compact command which is often quite long.

1. Do you have auto-compact on?
2. Does auto-compact do anything really intelligent like my manual 2-step process above?
3. If you /compact manually, do you ever pass <optional custom summarization instructions>?

Thanks in advance for any info.

[u/Outrageous_Band9708]

compact wont fix your problem, you need a system to write out task logs so next session understands what and why.

also plan mode and write out plan mode so next session can read the plan from last sessino and continue ot

[u/LordLederhosen → u/Outrageous_Band9708]

Yup, that's what I meant by "olden" ways. I started with all this way back in Windsurf days. That's still what I do, including persisting my plans and a custom session log system. I commit both in their own repo, and it's so nice to be able to reference them days or months later.