Skip to main content
A pane is a view of work. A managed session has a separate host that owns its terminal and provider process. Keeping these separate lets you return to running work without creating a new conversation just to reopen a view.

Return to an existing agent

Find the agent in the sidebar and open its pane. You can change Spaces or use another view while keeping the session’s working folder and conversation. While the session host and its machine remain running, managed work can continue when the app disconnects. Reopening Dure attaches to the current screen and later output. This is not a guarantee that every provider, host or computer can recover from every interruption.

Choose the action for the state you see

Closing a pane, stopping an agent and deleting its working files are different actions. Read the action and any confirmation before ending work you want to retain.

Recover an ended agent

When an agent’s session process has ended, its pane shows the recovery actions in place:
  • Resume session or Resume exact conversation continues the saved conversation in a new process. If no conversation ID was saved, first choose one of the conversations found in the working directory.
  • Start fresh or New conversation starts a new conversation in the same pane. The saved conversation history is kept.
  • Open shell, offered for local agents, replaces the agent pane with a shell in its working folder.
If the task’s worktree is missing, Recreate worktree and resume restores it before resuming. To find earlier work that no longer has a pane, open Sessions in the sidebar, search by session name, ID or folder, and select the session to continue it in a pane. Provider resume support and the saved conversation determine what can be restored. After recovery, check the conversation, working folder, changed files and any external effects before repeating a command. Recovery cannot undo an already completed deployment or guarantee every provider conversation can resume.

Keep files and conversation continuity distinct

A Git worktree stores task files and branch state; it is not the running process. Commit useful changes through your normal workflow. Review changes after an interruption, and check remote connection state for SSH work.