Conversations
A conversation is a persistent thread with one agent. It holds the history the agent reads for context, and it survives closing the app.
When to use it
Section titled “When to use it”A conversation is the default way to work with an agent. Start a new one when the subject changes; keep using an existing one while you are still on the same body of work.
What the agent reads
Section titled “What the agent reads”At the start of every run, the agent assembles its context from the conversation it is in — plus its prompt, its relevant memories, and, if the conversation belongs to one, the project’s context.
It does not read your other conversations. Two threads with the same agent are independent; anything the agent should carry between them belongs in memory or in the project.
Starting a new one versus continuing
Section titled “Starting a new one versus continuing”| Start a new conversation | Continue the existing one |
|---|---|
| The topic changed | You are refining the same result |
| The thread is long and full of dead ends | The earlier history is what makes the answer good |
| You want a clean comparison while iterating | The agent is mid-task |
Long threads are not free: everything in them competes for the model’s attention, and eventually for its context window. A thread that has wandered through three subjects produces worse answers than three focused threads.
History and returning to work
Section titled “History and returning to work”Conversations are listed by recency, so the thread you were in is the one at the top. Opening it restores the full history, including the tool calls each run made.
Work continues while you are away. If you close the app during a run, the run keeps going on the server; when you come back, the result is in the thread. See Runs.
Finding and organizing
Section titled “Finding and organizing”A workspace accumulates threads. Four things keep the list usable:
- Search looks through titles and message bodies, so you can find a conversation by something said in it rather than by what it was called.
- Pin keeps a conversation at the top of the list — the one you return to daily.
- Rename replaces the title Endue generated from your first message. Titles are a summary, not a label you chose, so renaming is worth it for the ones you keep.
- Archive takes a finished conversation out of the list without deleting it. Archived threads stay searchable and can be reopened; the sidebar stops showing them.
Copy link puts a link to the conversation on your clipboard. It is a bookmark for you, not a share — opening it requires your account.
Grouping into projects
Section titled “Grouping into projects”When several conversations concern the same body of work, put them in a project. An agent working inside a project reads the project’s context, which is the cheapest way to stop re-explaining background in every thread.
Limits
Section titled “Limits”- A conversation cannot be moved to a different agent.
- Agents do not read each other’s conversations, and the same agent does not read across its own threads.
- Very long threads eventually exceed the model’s context window; the practical fix is a new conversation, with anything durable moved into memory or the project.