Context
Growing context (chapters, branches, tasks)
The longer work runs, the longer conversations get and the more topics fork off. WorkPilot keeps things resumable through three moves: break into chapters, branch into child threads, and leave yourself a way back.
Breaking into chapters
Long conversations get slow, and the original premise blurs. That's when you start a chapter.
Choose π Continue in a new chapter from the thread menu.
A summary of the story so far is generated and placed at the top of the new chapter.
Recent exchanges and your equipment carry over, so you continue in the same groove.
Nothing is lost β earlier chapters remain and can be read back at any time.
If you're re-explaining the same thing repeatedly, or replies feel noticeably heavy, it's time. If the topic itself changed, consider branching instead.
Branching into a child thread
Side investigations and alternative approaches belong in a child thread, so the main line stays clean.
Branch from a message
Hover the message you want to branch from and choose branch. Naming it is optional.Branch from a draft
Use Branch from here in the composer's send options β your unsent text comes along.Get back to the parent
A breadcrumb to the parent sits in the child's header, and the parent is pinned to the top of the child list.
Rather than pushing everything into one long conversation, the work splits into a parent-child graph and only the conclusions flow back β that is what we call graph engineering. There is a short definition in the glossary.
A child receives the conversation as it stood at the moment of branching. If the parent moves on afterwards, the child's premise doesn't change. Files and notes are always read live.
Returning results to the parent
When the child reaches a conclusion, choose β Return results to the parent from the thread menu. The content is summarised and posted back to the parent as a card. If you were working as a team, use π Finish: return results and disband; to close out a branch, use β Finish: merge into the parent and close.
Turning things into tasks
Anything you decide to do can become a task. Tasks remember where they came from, so you can walk back to that conversation.
Create one
Select text in the conversation and add it as a task, or use οΌNew in the task list. The first line becomes the title, the rest becomes detail.Filter
Switch between Open, All, Done and more.Jump back
Following βgo to this placeβ from a task takes you straight to the message it came from.
Capture what you didn't finish today, and tomorrow you resume by jumping from the list β no time spent remembering which thread it was, or roughly where.
Deep links to a place
You can copy a link that points at a specific message and paste it into a note or a task. Links display with a readable name, and clicking one jumps there β the target message is highlighted.
Exporting a conversation
π€ Export this thread in the thread menu writes the whole conversation out as Markdown. Useful as a first draft of a deliverable, or as an internal record. π Open the storage folder shows you where it went.
Importing past conversations
Claude Code and ChatGPT conversations already on this Mac can be imported as threads, so earlier work carries over rather than being stranded.
Open the history import screen.
Select the conversations you want (search and select-all are available).
Run the import β they appear in your thread list.
Already-imported items are marked so nothing gets pulled in twice.