Why AI chat should branch, not scroll
Linear chat buries the alternatives you explored. A branchable workspace keeps every path, its provenance, and the ability to replay it.
Template post. This file is marked
draft: true, so it only appears when runningnpm run dev. Rewrite it into your first real post, or delete it.
Every serious piece of thinking forks. You try one framing, then another; you compare two models, two prompts, two datasets. A linear chat log flattens all of that into one scroll, and the alternatives you rejected — often the most informative part — disappear.
The cost of a single thread
When the conversation is linear, exploring an alternative means either polluting the current context or starting over and re-explaining everything.
- Context gets longer and noisier with every detour.
- There is no record of why one path was chosen over another.
- Reproducing a result later means scrolling and guessing.
What branching changes
In Trilix, each step is a node in a graph. You can fork from any point, run the branches in parallel, and merge what worked back together.
| Linear chat | Branchable workspace |
|---|---|
| One path, overwritten | Every path kept |
| Context only grows | Prune and recompute partially |
| Hard to audit | Provenance on every step |
A small example
question ──┬── branch A: summarise with model X
└── branch B: summarise with model Y ── merge → final answer
Try it
Open the workspace and fork your next conversation instead of scrolling it.