What a thread can do
Search, read your books, and change them with you, each step through your thinking.
A thread doesn’t only answer. It does the work, and it brings your thinking into each step, not just the first one.
Looking things up
A thread can search the web, and your team’s Linear, Jira, GitHub, and Notion when they’re connected and everyone who reads the thread may see what they feed. It searches the way your chapters frame the problem, and what it finds comes back beside the chapters it bears on. The reply tells you where a source agrees with your thinking, where it pulls against it, and where it touches something you’ve left open.
Beside what you’re reading
A thread knows which chapter or part you have open next to it, so you can say “rename this chapter” or “does this hold for B2B?” without pointing. That doesn’t change what the thread is About.
Above each reply, its steps appear as it works: what it searched, which of your thinking it brought in, and what it read. Once it’s written, they fold into one line you can open. See See what Cranes brought into a reply.
Your books
A thread can read your books and pin chapters for you. It can also propose changes:
- rename a chapter or a part
- move a chapter to another part
- archive a chapter, or restore one
- say you see a chapter differently now
- share a chapter with the team or a group, or make it the team’s position (owners and admins)
- move a chapter from your own thinking to the team or a group
- add a note
A proposed change shows in the thread as a small card, with what your thinking says about it in the reply. Nothing changes until you choose Make this change. Not now leaves things as they are. In a group thread, only the person a change was proposed to can make it.