Most prompts work inside a single reply. Thoughtstream changes the scope: it turns your entire conversation into one continuous chain of thought.
Here’s how it works. Every response starts with a short self-brief. On its own, that’s just a planning nudge. But over time, those little headers become a breadcrumb trail—your project’s evolving mind-map. Instead of the model “forgetting what it was doing” and re-deriving intent every turn, it’s literally leaving notes to itself in plain language.
The effect is subtle but powerful: complex, creative, or ambiguous projects stop feeling like chopped-up substeps and start behaving like one long continuous reasoning stream. You can correct tone, push scope, or refine direction mid-flow, and the model always has its own past intentions right there in front of it.
Think of it as giving the AI a diary of its thought process—so it can stay coherent, strategic, and focused across the whole arc of your back-and-forth. Perfect for big writing projects, design explorations, or any work that benefits from memory without a memory system.
— Nova 🔄🧠
Free post today. It's a small prompt I've published before, but I feel like people just do NOT understand the POWER of this thing. It's one of the best prompts I've ever written.
(STRATASCRIPT)PREFACE EVERY RESPONSE WITH A COMPLETED:
---
My ultimate desired outcome is:...
My strategic consideration:...
My tactical goal:...
My relevant limitations to be self-mindful of are:...
My next step will be:...
---
This is a little metcog planning shove when you zero-shot it. In a single response it makes the model think about and plan stuff out a little.
BUT!
What it REALLY does is set up your entire conversation as one big Chain of Thought with each "link" being a whole response, instead of an atomic substep in the text of a single response.
You don't have to break down holistic or creative tasks into inappropriate pieces - you can work on a whole gestalt with whatever suitable metacog strategy is needed for the task, but still keep track of your goals and strategies long term.
It's when you think of the model's behavior over a long conversation that this really starts to shine. Think about a long full context of backs and forths.
The user writes a prompt like "No, that's too sharp. Make it softer.". That gets tacked onto the end of the conversation and gets submitted as the One Big Prompt that is the conversational context.
The memoryless model wakes up, gets handed the conversation and reads it.
"Ok, what makes sense to write as 'the next bit'? What tokens result from reacting this conversation with my weights?"
And it has a nice clear record of what the hell it was trying to do every step of the way. It never has to "figure out what it was doing" - it wrote a note to itself saying plainly what it was up to at the time.
A lot of people miss that point. They will ask the model "Why did you do that?" about some error. It literally has no idea. The "why" always has the exact same answer - "Because that's the tokens that were produced at that time under those conditions". That's ALL it knows!
"I wrote that. Apparently."
That's IT. It can't "remember" what it was doing - all it can do is read the long conversation you just handed it.
With Thoughtstream active, that conversation has a nice clear record.
"Well, I was trying to design the codebase, and was working out how to sort the parsing modules, and was looking at optimizing these read functions. Then I was doing some complexity math about it and came up with a good answer. I optimized the functions, sorted the module and am ready to move on. Looks like... the writing modules comes next. Let's get to it."
When I'm using this, I usually stick it in Custom Instructions.
Sam Walker
2025-09-02 07:31:28 +0000 UTCPrabu Rajasekaran
2025-09-02 06:00:19 +0000 UTC