History and saved sessions

Find and reopen an earlier conversation on the host where it ran.

An agent and its session

An agent is the live conversation you interact with. Its session is the saved conversation that lets you find and reopen earlier work. A saved session can exist when no agent is actively working on it.

Disconnecting from a remote host is a third case: the agent may still be running on that host. Reconnect to inspect it rather than immediately launching a replacement.

Resume from History

1. Connect to the host where the original conversation ran.
2. Open History and locate the conversation using its preview, project, backend, and last-active information.
3. Use the resume action to reopen it.
4. Read the restored conversation before sending a new request.
5. Send a follow-up that states what you want to do next.

Continue from the approach we chose yesterday. First check the current files and tell me whether anything has changed that affects the plan.

Reopening a session should not be confused with asking it to do more work. The next message supplies that instruction. Files may have changed since the conversation was saved, so give the agent room to inspect their current state.

Resume context and current files

Use meaningful names and close a task with a concise decision: what was completed, what remains, and where the changes live. This makes it easier for you to choose the right conversation later.

Context limits, compaction, and resume behavior depend on the harness. Tyde presents the session through a shared interface, but a long conversation still operates within its backend’s capabilities.

If a conversation seems missing

Check the selected host and any History filters first. Work performed on a home server belongs to that host; switching to the laptop’s local host does not move its sessions. See History and reconnect recovery before starting the task again.