DeepCode saves your conversations so you can return to a task without explaining it again. Each conversation belongs to a project folder and includes your messages, DeepCode's replies, and its tool activity. DeepCode calls this a Session in every interface.
Open DeepCode in your project folder and enter:
/resume
Choose a conversation from the list. To search conversations from other projects,
use /resume all. In Desktop/Web, select a saved Session under its Project.
If you know the Session ID, you can open it directly from your terminal:
deepcode --resume SESSION_IDReplace SESSION_ID with the ID shown for your conversation. Read the latest
messages, then tell DeepCode what you want to do next.
If the conversation is still working on a Turn, for example one you started in another terminal, the TUI shows what that Turn is doing now (the answer so far, the thinking, a tool that is running or waiting for your approval) and follows it to the end. Steps it finished before you joined are not shown again; the latest messages printed above them give the context.
You can start a task in the TUI and open the same conversation in Desktop or Web. On the same computer, use the same DeepCode version and configuration directory so all three interfaces show your projects and history.
While DeepCode is working, send a message to adjust the current task. To save a
separate instruction for afterward, use /queue in the TUI:
/queue When the current fix is finished, update the README example to match.
You can also handle an approval from another open interface. Closing a window
leaves running work in the background; use /stop or the stop button to interrupt
it. If you are using a Goal, pause the Goal to prevent it
from continuing automatically.
After a connection problem, return to the conversation and check where the work stopped before sending it again. See Troubleshooting.
| What you want to do | Desktop / Web | TUI |
|---|---|---|
| Start a Session | New Session | /new [title] |
| Resume local history | Select it under the Project | /resume |
| Find history from every Project | Browse the project list | /resume all |
| Attach a file | Composer attachment | @path/to/file |
| Change the next Turn's model | Composer model picker | /model |
| Adjust reasoning effort | Composer effort picker | /effort |
| Cap the Session's context window | Model picker context control | /context |
| Choose tool access | Composer access picker | /permissions |
| Pick an agent preset | Preset picker | /preset |
| Load Skills for the next Turn | Composer Skills control | /skill <name> |
| Create a reusable Skill | Skills → Create Skill | $skill-creator |
| Set or revise a durable Goal | Goal panel | /goal |
| Queue the next instruction | Composer while a Turn runs | /queue <text> |
| Stop the active Turn | Stop control | /stop |
| Re-run the last Turn | Retry control on the Turn | /retry |
| Compact a long conversation | Automatic under pressure | /compact (also automatic) |
| Change transcript detail | Transcript detail menu | /transcript or Ctrl+O |
| Rename or delete a Session | Session menu | /rename <title> · /delete <id> |
Archiving hides a Session without deleting its history. Permanent deletion removes the Session records but never your repository files.
When a conversation becomes long, use /compact to summarize its older messages
and make room for more work. DeepCode keeps the recent messages and tool results,
and saves the summary for the next time you open the conversation.
Summarizing is a model request and can take a while. A message sent to the conversation in the meantime, for example from another window, starts when the summary is done. If there is nothing worth compacting yet, DeepCode says so and leaves the conversation unchanged.
DeepCode also compacts automatically as the conversation approaches the model's context limit. To use a smaller limit, see context settings.
Give conversations descriptive names so they are easy to find:
/rename Fix flaky auth tests
Use /new to start another task. If you changed the model, reasoning effort,
or context cap in this conversation with /model, /effort, or /context, the
new conversation keeps the current model and those settings; otherwise it
follows your default settings, as a new task in Desktop or Web does. Use
/clear when you want to keep the current Session but clear its conversation
context.
To remove a saved conversation, use /delete SESSION_ID or the delete action in
Desktop/Web. This permanently removes its records while keeping your project
files. Finish or stop its active work before deleting it.
DeepCode normally stores your conversation files in ~/.deepcode/sessions/ and
its task, approval, and Automation data in ~/.deepcode/state/deepcode.sqlite3.
Large tool outputs may also be stored in your project's .deepcode/tool-results/
directory. Keep these files when backing up work you want to resume. An output
that no Session has used for 90 days is removed.
For a consistent backup or to recover an earlier installation, follow the backup and restore guide. Back up your project files separately. Keep the database during troubleshooting: conversation files alone cannot restore all of its saved information.