Organize, share & export topics
Topics keep each piece of work in its own thread — findable, shareable, and exportable. This page covers the topic sidebar, folders, and every way to get a conversation out of Wingman.
The topic sidebar
Inside a conversation, the topic sidebar is your filing cabinet. Its header names the current agent — click it to switch agents without leaving the sidebar. The quick nav above the list jumps to Search, New Chat, Customize, My Documents, User manual, and Get Desktop App; a More options control reveals the entries past the first two.
The list itself groups topics by time or by your own rules, searches by title and content, and pages when it gets long — pick the page size that fits how much you keep. It can also import topics from JSON and bulk-delete old ones when it is time to clean house.
| Topic action | What it does |
|---|---|
| Rename | Give the topic a title that matches the work — do this once the task is clear. |
| Favorite | Pins the topic so it stays easy to find. |
| Duplicate | Copies the topic before trying a different direction. |
| Share | Opens the share modal — formats below. |
| Delete | Removes the topic; bulk cleanup handles many at once. |
How conversations are named
Wingman names a new conversation from your first message. When it cannot find a short name, the conversation takes the first words of that message instead, and you can rename it whenever the work takes shape.
The name also heads the open conversation. A name too long for the header ends in an ellipsis so it never covers the header buttons; hover it to read the whole name.
All topics and project folders
Two bigger containers organize topics themselves. The all-topics drawer shows every topic across agents, with side threads nested under their parent topic — the place to find a branch you made last week. Project folders (session groups) group related agents and their sessions: create one from the sidebar + menu, rename or configure it inline, and delete it when the project ends.
Share and export a topic
Sharing a topic
Open the share modal
Open the topic menu and choose Share. The share modal offers five tabs — Screenshot, Text, PDF, JSON, and Fork — each for a different audience.
Pick the format for the audience
Screenshot renders the conversation as a clean image for slides and chat apps. Text copies portable Markdown for wikis and PRs. PDF makes a paginated document. JSON exports the raw conversation for backup or import elsewhere. Fork duplicates the conversation into a new topic in your own workspace — the quickest way to branch before trying a different direction.
Tune what goes in
Every tab has its own settings panel on the right, and the options differ by format. Text and PDF share the same four: include the system prompt, show the role in front of each message, keep your own messages, and keep tool calls. Screenshot adds width and image type; JSON adds a full-or-simple export mode. Change a setting and the preview follows — on the PDF tab, press Generate again to rebuild the document.
Exports are copies, not links
Export as PDF
PDF is the format for people outside the conversation: a paginated A4 document, roles and headings intact, that reads the same in an email thread and a review meeting.
Set the toggles first, then press Generate PDF — the document is rendered on the server, so this takes a few seconds and longer for a long topic. When it appears, page through it in the preview, open it full-screen to check the layout, then Download PDF. Changed your mind about a toggle? Regenerate PDF rebuilds it in place.
When a PDF does not come out
| What you see | What it means | What to do |
|---|---|---|
PDF generation timed out — the server did not respond in time. Please try again. | The export did not finish within a minute. Usually a very long topic or a slow moment on the server. | Press Generate PDF again. If it keeps timing out, export a single message instead of the whole topic, or use the Text tab and print from there — and tell your administrator, who can check the chat service's outbound access. |
The PDF preview took too long to load. You can still download the file, or try generating it again. | The document was built, but your browser could not render the preview — often a slow connection or a blocked script on a locked-down network. | Download the PDF and open it in your normal reader; the file is fine. Or retry from the error panel. |
| A red message with the server's explanation | The export failed outright. The reason is printed underneath the heading. | Retry from the panel on the right — your toggles are still set — and include the exact message if you report it. |