# Find an old conversation

Canonical: https://godspeedmissioncontrol.com/guide/find-a-conversation

Your conversations with Godspeed are saved in your own folder, with the answers you saw. So are new conversations with Claude Code, Codex and OpenCode, if you use them. This is your conversation archive.

## Search it

Ask Godspeed in your own words:

```text
Search my old conversations for the invoice reminder.
```

It also looks there by itself before it says it cannot remember a talk.

From a terminal on your computer, the same search is:

```bash
mc-prompt-archive search invoice reminder
```

If the terminal says the command is not found, see [Terminal commands](/guide/terminal-commands).

## What is in it

- **Kept:** what you typed and the answers you saw, from the day you installed or updated. A computer adds them once a day. A server installed with the one-line command adds your Telegram and notebook chats every hour.
- **Not kept:** chats that live only in a web browser or an online account, Claude Desktop, and the commands the AI ran in between.
- **Where:** `prompts/archive/` in your mission control folder, one file per machine per month.

Before anything is saved, a filter removes keys, passwords, email addresses and long random-looking strings.

## Keep a name out of it

1. In your home folder, open the folder `.godspeed` (on Windows `%USERPROFILE%\.godspeed`). This is not the `.godspeed` folder inside your mission control folder.
2. Open or create a plain text file called `redact.txt`.
3. Write one name per line, such as a client's name, and save it. From then on, the filter removes those names too.
4. To clean what is already saved, run `mc-prompt-archive rescrub` in a terminal.

## Switch it off on your computer

1. Open the file `device.env` in that same `.godspeed` folder.
2. Add this line and save the file:

   ```text
   GODSPEED_PROMPT_ARCHIVE=off
   ```

3. To check, run `mc-prompt-archive --dry-run`. It says "saving chats is switched off on this computer".

To remove chats already saved, switch the archive off first, then delete the files: otherwise the next run writes them again.

## Related

- [How it remembers](/guide/memory)
- [Where your data lives](/guide/where-your-data-lives)
