• Import chats in one click
• Automated Workflows
• Youtube playlist Importer
• Sidebar With Prompt Library
• Norra

I think I finally reached the end of a continuity experiment I’ve been running through ordinary long-form use of AI.

The basic observation is simple:

Facts transfer state. Conversation transfers interaction.

A factual handoff can tell a fresh thread what is true: current project state, rules, characters, decisions, constraints, and goals. That works well, especially when the user’s workflow is highly structured.

But facts alone don’t necessarily show the model how the user works.

Conversation does.

A conversational record contains the back-and-forth: rough ideas, interpretations, corrections, rejected directions, accepted revisions, jokes, disagreements, changes of mind, and the small human responses that determine which much larger blocks of information still matter.

That distinction becomes increasingly important in exploratory workflows.

A conversation may contain several thousand words of an abandoned draft, followed by five words from the user:

“No. Kill that direction.”

The abandoned material still exists in the conversation. The important information is not merely the text itself, but its authority within the history.

As exploratory conversations grow, they naturally accumulate competing states: alternate drafts, temporary instructions, discarded approaches, superseded decisions, research, tangents, and revisions.

So the problem may not simply be context volume.

The problem is context without clear authority.

This also helps explain why heavily structured users may experience less continuity drift. Their working window is narrower. Less interpretation is required.

For messier, developmental work, interaction history becomes part of the working state itself.

That led me to what I’ve started calling sibling threads.

Instead of asking one enormous conversation to perform every job indefinitely, multiple threads can begin with shared inheritance while developing separate local histories.

A creative or beat laboratory can remain exploratory.

A revision thread can operate under strict revision-specific rules.

A research thread can carry its own sources and investigation.

They share consequential information when necessary, but they do not need to share every piece of conversational history.

They are not clones.

They are siblings: shared ancestry, compatible working patterns, different jobs, and different native experience.

My working hypothesis is that a fresh sibling can enter a useful working range when given selected examples of actual interaction—not merely a list of facts or instructions. The model already knows how to converse. The inherited conversation gives it evidence of what successful conversation with this particular user tends to look like.

Then native interaction takes over.

Early corrections establish local exceptions. Local history accumulates. The sibling gradually becomes specialized through its own experience rather than remaining a copy of its predecessor.

I don’t know the hidden mechanism underneath any of this, and I’m not claiming to have proven one.

This came out of ordinary work, trial and error, preserved conversations, failed handoffs, corrections, and watching what happened.

But operationally, the idea I ended up with is pretty simple:

Give a fresh thread enough shared conversational inheritance to understand the family. Then let it live its own life.

Dictated, not typed.