Smol Command

/smol (or its alternative, /compact) is a slash command that compacts your conversation history while maintaining critical context.

In contrast to /newtask which generates a new task, /smol consolidates your ongoing conversation into a thorough summary, liberating context window space while enabling you to persist working within the same task.

Conceptualize it as distilling the pertinent portions of a conversation while eliminating the remainder.

Using the /smol Slash Command

When your context window is approaching capacity but you wish to remain in the same task:

• Enter /smol (or its alternative /compact) in the chat input field
• Sypha will assess your conversation and generate a comprehensive summary that retains essential information
• You'll have an opportunity to examine this summary and offer feedback if necessary
• Upon acceptance, the extensive conversation history is substituted with this compressed version

Example

I employ /smol when I'm immersed in a complex debugging session and need to persist in the same task. Following exploration of multiple strategies and examination of numerous files, my context window becomes congested with all the exchanges.

By utilizing /smol, I can compress all that exploration into a succinct summary that captures what we've discovered, which files we've reviewed, and what strategies we've attempted. This creates space to continue the debugging without sacrificing the insights we've accumulated.

The fundamental distinction from /newtask is that I'm remaining in the same conversation flow instead of establishing a separate task. This is especially beneficial when I'm amid something and don't wish to context switch.

Inspiration

Here are effective ways I utilize /smol in my workflow:

• Throughout extended brainstorming sessions, I employ /smol to consolidate our exploration prior to implementing the selected solution, all within the same task.
• When troubleshooting intricate issues that require multiple file inspections and test executions, I use /smol to encapsulate what we've learned while advancing the debugging process.
• For incremental development, I apply /smol after finishing each feature to condense the implementation specifics while maintaining the key decisions and methods accessible.
• When collecting requirements from various sources, I use /smol to extract the vital needs into a brief summary before transitioning to the design phase.

Smol vs Newtask

People frequently inquire when to apply /smol versus /newtask. Honestly, it's a question of personal preference and your objectives. Here are some recommendations:

• Apply /smol when you're in the midst of something and wish to continue in the same task. It's ideal when you're deeply engaged in a debugging flow or brainstorming session and don't want to disrupt your momentum. The limitation? After you compress your history, you cannot retrieve those detailed conversations.
• Apply /newtask when you're at a logical transition juncture and desire to start anew. It's excellent for progressing from planning to implementation, or when you want to safeguard your complete conversation history (since it establishes a new task instead of overwriting your existing one).