A prompt you can copy into Claude Code, Codex, or any agent.
ReMynd on the command line
ReMynd captures what is on your screen, starting from the moment you install it. It cannot recover past work, and it cannot see background or cloud agents. The searchable index is stored on your computer and never pooled, trained on, or sold.
The CLI is how you, or the agent you already use, reads that history from a terminal. It ships inside the ReMynd desktop app. It is not a separate download.
If you want a prompt an LLM can follow, switch to Agent mode above, or fetch the same text at /cli/llms.txt.
Grant screen-recording permission and let it record. There is nothing to search until it has been running.
In ReMynd, open Settings → Integrations and turn on the Claude switch or the Codex & ChatGPT switch.
That last step puts a stable command on your machine:
Mac: ~/.local/bin/remynd
Windows: %USERPROFILE%\.local\bin\remynd.exe
If you type remynd and the shell cannot find it, use the full path, or add ~/.local/bin to your PATH. macOS does not include that folder by default. In zsh: echo 'export PATH="$HOME/.local/bin:$PATH"' >> ~/.zshrc && source ~/.zshrc.
Check that it works:
~/.local/bin/remynd help
~/.local/bin/remynd status
On Windows, the same commands with remynd.exe. History access is read-only. The only thing remynd profile writes is which local installation to use.
Quickstart
~/.local/bin/remynd now
~/.local/bin/remynd recent
~/.local/bin/remynd search "design review"
~/.local/bin/remynd day 2026-11-11
~/.local/bin/remynd apps 7
If several ReMynd profiles exist on the machine, the CLI will ask you to pick one and save it:
~/.local/bin/remynd profiles
~/.local/bin/remynd profile "the-name-it-listed"
Which command to use
Something you saw or an error you half-remember: search, then text around a timestamp.
What you did on a day, or yesterday afternoon: day, then text for the hours that matter.
Where the time went: apps.
What you are doing now, or where you left off: now or recent.
A meeting, or something said out loud: calls, heard, and call. Screen search cannot hear.
Whether it is recording: status.
Commands
These are on the Mac and Windows CLIs. Run remynd help or remynd.exe help for the live list on your install.
Command
What it does
remynd now
What you are doing right now
remynd recent [minutes]
A digest of recent activity (default: 2 hours of activity, 30 minutes of screen text)
remynd search <query> [limit]
Full-text search of what has been on screen (default 40; also --limit N)
remynd day <YYYY-MM-DD>
Reconstruct a local day
remynd apps [days]
Where time went (default 7)
remynd text <from> [to]
Verbatim screen text in a local-time range
remynd moment <time> [minutes]
The focused window at a moment, and the text around it (default 4 minutes either side)
remynd status
Profile, freshness, and privacy status
remynd calls [days]
Calls recorded and transcribed (default 14)
remynd call with an id, or last
One call, one line per utterance. --audio prints the audio path
remynd heard <query> [limit]
Full-text search across call transcripts (default 30; also --limit N)
remynd snippet moments / create
Text in a range, or open that range in ReMynd to share
remynd clip list / where / share
Agent answers that used ReMynd, clipped or not
Times are local. A timestamp is when something was on screen, not when the event it describes happened. OCR can be messy. Credential-shaped strings are redacted in text as <redacted>. Accepted time forms include "YYYY-MM-DD HH:MM", "21:30" or "9:30 pm" for today, and "yesterday 21:30".
remynd profiles and remynd profile pick among installations when more than one exists. remynd custom-apps inspects custom apps in the running app; it is not a history command.
Connect an agent (MCP)
The same history is available to an MCP-ready agent through a local helper: remynd-mcp on Mac, bundled at /Applications/ReMynd.app/Contents/Helpers/remynd-mcp, and remynd-mcp.exe on Windows.
It speaks MCP over stdio. It never listens on the network. Every tool is read-only and calls the CLI. If you turn on the Claude switch or the Codex & ChatGPT switch in Settings → Integrations, ReMynd writes this entry for you and you only need to restart the agent. The Claude switch sets up Claude Desktop on Mac. The Codex & ChatGPT switch sets up Codex on Mac and Windows; the ChatGPT desktop app shares that config, and the ChatGPT website does not. Claude Desktop on Windows is not claimed.
Claude Code (manual)
Claude Code already gets a ReMynd skill and can run the CLI. To add the MCP server yourself, run claude mcp add --transport stdio remynd -- /Applications/ReMynd.app/Contents/Helpers/remynd-mcp --profile "/path/to/your/ReMynd/profile".
remynd profiles lists the profile names. The MCP helper wants the profile path, which is also what ReMynd writes when it registers the server for Claude Desktop. If you would rather not look that path up, turn on Claude Desktop or Codex in Settings and copy the entry ReMynd wrote.
Then, in Claude Code, run /mcp and confirm remynd is listed.
Codex (usually automatic)
With Codex turned on in Settings, ReMynd appends a managed block to ~/.codex/config.toml. The block sets command to /Applications/ReMynd.app/Contents/Helpers/remynd-mcp, and args to --profile plus the path to your ReMynd profile. It also sets default_tools_approval_mode to approve and startup_timeout_sec to 30. Do not hand-edit a block ReMynd is already managing; change it in Settings instead.
Restart Codex, and the Codex-hosted ChatGPT desktop app, if you use it. The ChatGPT website only accepts remote HTTPS MCP servers, so this local helper will not show up there.
What the agent can see
The helper can search screen history, reconstruct a day, read recent activity, list and search call transcripts, and, if you leave "Let agents see screen frames" on, show the exact moment you ask about. Frames are the raw screen: unlike text, passwords and keys visible in them are not redacted. One switch in Settings turns frames off.
Your agent uses its own model. What it reads may be sent to that model under your account, the same way anything you paste into it would be.
The Agent mode on this page is a prompt written for that agent. The same text is at /cli/llms.txt.
Windows
On Windows 11, the CLI is %USERPROFILE%\.local\bin\remynd.exe, enabled the same way, in Settings → Integrations. Windows 1.0.9825 ships remynd-mcp.exe and documents moment, calls, call, heard, snippet, clip and custom-apps in its bundled skill. The Codex & ChatGPT switch writes the remynd-mcp entry into config.toml, which the ChatGPT desktop app shares; the ChatGPT website does not. Claude Desktop on Windows is not claimed. Run remynd.exe help on your machine for the live list.
Privacy, in one place
Capture starts at install. There is no history from before that.
ReMynd does not see background or cloud agents.
The CLI opens your local history read-only. It does not upload it.
Recordings and the searchable index are stored on your computer, and never pooled, trained on, or sold.
Optional cloud sync is a separate, opt-in setting, and is not used by the CLI.
Connecting an agent is your choice. The helper stays on your computer; the agent's model may see what it retrieves.
If you want the longer architecture, it is on ReMynd for engineers. To try it: install the app, turn on Integrations, and run ~/.local/bin/remynd help. Just ReMynd it.
Common questions
How do I get the remynd command? +
Install the ReMynd desktop app, grant screen-recording permission, and turn on the Claude switch or the Codex & ChatGPT switch in Settings → Integrations. That puts remynd at ~/.local/bin/remynd on Mac, or remynd.exe at %USERPROFILE%\.local\bin on Windows.
Does the CLI upload my history? +
No. It opens your local history read-only. Recordings and the searchable index are stored on your computer, and never pooled, trained on, or sold. Optional cloud sync is a separate, opt-in setting, and the CLI does not use it.
Does ReMynd have an MCP server? +
Yes, on Mac and Windows. ReMynd bundles a local, read-only helper that speaks MCP over stdio and never listens on the network: remynd-mcp on Mac, remynd-mcp.exe on Windows. The Claude switch writes the entry for Claude Desktop on Mac, and the Codex & ChatGPT switch writes the remynd-mcp entry into config.toml on Mac and Windows, which the ChatGPT desktop app shares; the ChatGPT website does not. Claude Code gets the remynd command and a skill; you can add the helper by hand. Claude Desktop on Windows is not claimed.
Does it work on Windows? +
Yes. On Windows 11, Settings → Integrations installs remynd.exe, including moment, calls, call, heard, snippet, clip and custom-apps, and ships remynd-mcp.exe. The Codex & ChatGPT switch writes the remynd-mcp entry into config.toml, which the ChatGPT desktop app shares; the ChatGPT website does not. Claude Desktop on Windows is not claimed. Run remynd.exe help on your machine for what you actually have.
Can it see work from before I installed ReMynd? +
No. ReMynd captures only what is on your screen, starting from install. It cannot recover past work, and it cannot see background or cloud agents.
How do I give this to my agent? +
Switch this page to Agent mode, or copy the prompt from the homepage, or fetch the plain-text version at /cli/llms.txt. Paste it into Claude Code, Codex, or any LLM.
Paste this into Claude Code, Codex, or any LLM so it can use the remynd command well.
# ReMynd CLI — instructions for you
You are helping a person query their own screen history and call transcripts with the ReMynd CLI (and, on Mac, the remynd-mcp server). Follow this document. Prefer a few focused commands over dumping long stretches of history. If anything here disagrees with `remynd help` on their machine, their live help wins.
A copy of this prompt lives at https://remyndai.com/cli/llms.txt and at https://remyndai.com/cli/#agent.
## What ReMynd is, and what the CLI exposes
ReMynd is a desktop app. It captures what is on the user's screen, starting from the moment they install it, and it can transcribe calls. It cannot recover work from before install, and it cannot see background or cloud agents.
The CLI reads that history from the user's computer. History access is read-only. The only command that writes is `remynd profile`, which remembers which local installation to use. Databases are opened read-only. There is no API key and no network auth for the CLI.
Recordings and the searchable index are stored on the user's computer, and never pooled, trained on, or sold. Optional cloud sync is a separate, opt-in setting, and the CLI does not use it.
A timestamp is when something was on screen, not when the event it describes happened. Times the CLI prints are local. OCR can be messy (menus, chrome, garbled words; digits are the least reliable). Credential-shaped strings are redacted in text as `<redacted>`. Screen commands cannot hear: words said out loud live in the call commands, not in `search` or `text`.
## Install and enable
The CLI is not a separate download. It ships inside the ReMynd desktop app.
1. Install the ReMynd desktop app (Mac, or Windows 11 x64 or arm64).
2. Grant screen-recording permission and let it record. There is nothing to search until it has been running.
3. In ReMynd, open Settings → Integrations and turn on the Claude switch or the Codex & ChatGPT switch.
That last step puts a stable symlink (or, on Windows, a symlink or a refreshed copy) on the machine:
- Mac: `~/.local/bin/remynd` → the launcher inside ReMynd.app
- Windows: `%USERPROFILE%\.local\bin\remynd.exe`
### PATH
macOS does not include `~/.local/bin` on PATH by default. If the shell says `command not found`, use the full path, or add that folder to PATH, for example:
```bash
# zsh (default on macOS)
echo 'export PATH="$HOME/.local/bin:$PATH"' >> ~/.zshrc && source ~/.zshrc
# bash
echo 'export PATH="$HOME/.local/bin:$PATH"' >> ~/.bash_profile && source ~/.bash_profile
```
On Windows, add `%USERPROFILE%\.local\bin` to the user PATH, or call `remynd.exe` by full path.
Check that it works:
```bash
~/.local/bin/remynd help
~/.local/bin/remynd status
```
If the command is present but cannot load its core, it prints: `Open ReMynd Settings > Integrations and enable your AI agent again.`
## Global flags and conventions
- `remynd --profile <name> <command>` (also `--profile=<name>`) uses a profile for one command without changing the remembered choice.
- A limit can be written as a positional argument or as `--limit N` / `--limit=N` on `search` and `heard`. After `--`, nothing is an option, so a query that looks like a flag stays the query.
- Limits must be a positive whole number, at most 1000.
- Times: use `"YYYY-MM-DD HH:MM"` or `"YYYY-MM-DD HH:MM:SS"` in local time. ISO 8601 with `T` and a `Z` or offset also works, as do `"21:30"` or `"9:30 pm"` for today, and `"yesterday 21:30"`. Quote times that contain spaces.
- Exit status 4 means part of the answer could not be read; stderr says why. Exit 2 means several profiles exist and the user must pick one. Exit 3 means the named profile was not found.
- There is no `--json` flag on the retrieval commands (`now`, `recent`, `search`, `day`, `apps`, `text`, `moment`, `status`, `calls`, `call`, `heard`). The one JSON flag in this surface is `remynd clip list --json`.
## Which command to use
| The user wants… | Start with | Then |
| --- | --- | --- |
| What they are doing right now, or where they left off | `now`, or `recent` | `text` or `moment` around a timestamp |
| A remembered phrase, error, page, person, or topic they saw | `search "<query>"` | `text` for the surrounding minutes; `moment` for the focused window |
| What they did yesterday / on a date / "yesterday afternoon" | `day YYYY-MM-DD` | `text` on the relevant hours; `calls` that day if a meeting matters |
| How much time went to an app | `apps [days]` | `day` if the subject is more specific than an app name |
| Verbatim screen text in a range | `text "<from>" "<to>"` | Narrow first; a whole day is a lot of OCR |
| The window in focus at one instant | `moment "<time>" [minutes]` | Minutes are either side of the time (default 4, max 120) |
| Whether history is fresh, which profile, redaction | `status` | Run this before saying something is "not in their history" |
| What was said on a call, a recap, a verbal commitment | `calls`, `heard`, `call` | Never conclude a conversation was not captured from screen history alone |
| To share a moment of the screen as a link | `snippet moments`, then `snippet create` | Ask before publishing; the user must press Share in the app |
| The answer you just gave from ReMynd, as a clip | `clip list`, `clip where`, `clip share` | Only share when they ask |
Search tips: quote a multi-word query. Start specific (`"design review notes"`), then drop words if there are no hits. If the result line says it is showing the N most recent of a much larger set, narrow the query or raise the limit (`--limit 200`, max 1000). `AND`, `OR`, `NOT`, and `NEAR` are treated as search operators; punctuation in a query may be rewritten into a literal word search. Hits are newest first. A hit is a cursor — read around it with `text`, do not treat one OCR line as the whole story.
To narrow by time, use `text` or `day` rather than hoping `search` will take a date range (it does not). To narrow by app, `apps` ranks time by application; `moment` can tell you which app was focused at a timestamp; `search` itself is not an app filter.
## Commands (Mac)
These are the Mac commands. Run `remynd help` for the live list. Examples use `remynd`; if it is not on PATH, use `~/.local/bin/remynd`.
### remynd now
Syntax: `remynd now`
What it does: the application and window in focus at the latest recorded moment.
Output: one line, `App — "Window Title"`. If there is no title, just the app name. If nothing has been recorded: `(nothing recorded yet)`.
Example: `remynd now`
### remynd recent [minutes]
Syntax: `remynd recent [minutes]`
What it does: a digest of recent activity. With no argument, that is the last 2 hours of activity and the last 30 minutes of verbatim screen text. If you pass minutes (a positive whole number, at most 10080, which is 7 days), that value is used for every section, including the screen-text section.
Output: a markdown-like digest:
- `# ReMynd — your recent activity`
- a read-only line and the generated local time
- `## Right now` — same as `now`
- `## What you've been working on (last …)` — activities ranked by time, from window titles
- `## Time by app (last …)`
- `## Recently open`
- `## What you were reading`
- `## On your screen (last Nm, verbatim)`
- a footer with how far back recorded history runs, and a pointer to `day` and `search`
Example: `remynd recent` or `remynd recent 60`
### remynd search <query> [limit]
Syntax: `remynd search <query> [limit]`
Flags: `--limit N` or `--limit=N` (default 40, max 1000). `--` ends options.
What it does: full-text search of everything that has been on screen (OCR). Newest first.
Output: one line per hit, `YYYY-MM-DD HH:MM:SS <text>`. If the limit is below the total, a header: `Showing the 40 most recent of N matches. Narrow the query, or raise the limit: remynd search "query" 200`. If nothing matches: `(no matches — try fewer or different words)`.
Example: `remynd search "design review"` or `remynd search "ENOENT" --limit 100`
### remynd day <YYYY-MM-DD>
Syntax: `remynd day <YYYY-MM-DD>`
What it does: reconstruct one local calendar day.
Output:
- `# YYYY-MM-DD (Weekday)`
- `## What you worked on` — activities ranked by time actually spent, or `_Nothing recorded on this day._`
- `## Sites`
- `## How the day ran` — an hour-by-hour trail of window titles
- If this profile has a hole that another ReMynd profile on the same Mac was recording through, a note naming that profile and the missing hours
- A pointer: `Verbatim screen text for any stretch: remynd text "YYYY-MM-DD HH:MM" "YYYY-MM-DD HH:MM"`
Example: `remynd day 2026-11-11`
### remynd apps [days]
Syntax: `remynd apps [days]`
What it does: where time went, by application, counting back from now. Default 7 days, max 3650. This is the command that measures duration. It is not a date-range query; for one specific day, use `day`.
Output:
```
# Time by app, last 7 days
Visual Studio Code 12h 04m
Google Chrome 6h 21m
```
Up to 20 apps, minutes greater than zero, loginwindow / ScreenSaverEngine / Window Server excluded.
Example: `remynd apps 7`
### remynd text <from> [to]
Syntax: `remynd text <from> [to]`
What it does: verbatim screen text in a local-time range. If `to` is omitted, the range runs to the latest text. Quote times that contain spaces.
Output: one line per unique stretch, `HH:MM:SS <text>` (clock time; the date is the one you asked for). If nothing is there: `(nothing recorded in that range)`.
Example: `remynd text "2026-11-11 14:00" "2026-11-11 17:00"`
### remynd moment <time> [minutes]
Syntax: `remynd moment <time> [minutes]`
What it does: the window in focus at one instant, then the screen text around it. `minutes` is the span either side of the time (default 4, max 120). It takes one time, not a range — for a range use `text`.
Output: first line is `App<TAB>Window Title` (the window may be empty). A blank line, then the same text listing `text` would print for that window of time.
Example: `remynd moment "2026-11-11 16:42"` or `remynd moment "2026-11-11 16:42" 10`
### remynd status
Syntax: `remynd status`
Output, labelled fields:
- `Profile:` path of the selected installation
- `Build:`
- `User:` (only if known)
- `Database:` size
- `Last write:` how long ago the database was written
- `Last capture:` local timestamp of the latest screen text, or `could not be read`
- `Calls:` count and latest call time, or `none recorded yet` / `could not be read`
- `Redaction:` `on (credential-shaped strings)` or `OFF`
- `Access: local, read-only`
If nothing is on the Mac yet: `ReMynd: not found` and `History: unavailable (nothing to read yet)`.
Example: `remynd status`
### remynd calls [days]
Syntax: `remynd calls [days]`
What it does: calls recorded and transcribed, default last 14 days, max 3650. Screen commands cannot hear; start here for meetings.
Output:
```
# Calls recorded, last 14 days
2026-11-11 14:02–14:41 39m Zoom 185 lines, 3 speakers [4821]
Weekly pricing review
with Alex, Sam
```
The id is in brackets. Untranscribed calls say `not transcribed`. A single speaker is marked `1 speaker (undiarized)`. If none: `(no calls recorded in that window — try a wider one: remynd calls 90)`. Footer: `Read one: remynd call <id> Search what was said: remynd heard "<words>"`. If the extras database is missing: `No calls have been recorded on this Mac yet.`
Example: `remynd calls 14`
### remynd call <id|last|words> [--audio]
Syntax: `remynd call <id|last|words> [--audio]`
What it does: one call, in full. `last` (or `latest`) is the most recent. An exact id wins; otherwise the words are matched against the date, app, title and participants. If several match, it lists them and asks you to pick by id. `--audio` prints the path to that call's audio file and nothing else.
Output (without `--audio`): a heading with the title, then app, local start and end, participants, line and speaker counts, and an audio path when one can be opened. Then one line per utterance: `HH:MM:SS Speaker: text`. If the audio was recorded but never transcribed: `(the audio was recorded but never transcribed — this call has no text)`. Speaker labels are about 85% reliable and names are often misheard — check a quote against the lines around it before attributing it.
Example: `remynd call last` or `remynd call 4821` or `remynd call 4821 --audio`
### remynd heard <query> [limit]
Syntax: `remynd heard <query> [limit]`
Flags: `--limit N` or `--limit=N` (default 30, max 1000). `--` ends options.
What it does: full-text search across call transcripts — words said out loud, not text that was on screen. Newest first.
Output: two lines per hit:
```
2026-11-11 14:18 [Weekly pricing review · 4821]
Alex: we should share the roadmap draft on Friday
```
If nothing matches: `(nothing matching was said in any recorded call — try fewer or different words)`. Footer: `Read the conversation around a hit: remynd call <id>`.
Example: `remynd heard "pricing"` or `remynd heard "commit to Friday" --limit 50`
### remynd profiles / remynd profile
Syntax:
- `remynd profiles` — list installations/user profiles with history
- `remynd profile` — show the remembered selection, or the only available profile
- `remynd profile "the-name-it-listed"` — remember that profile
- `remynd profile --clear` — forget the selection
If several profiles exist and none is saved, commands stop and ask the user to pick. Do not choose for them based on build type, freshness, or apparent activity, and do not combine histories without their direction. After they choose, save the exact listed name and rerun the original query. Do not ask again unless the saved profile becomes unavailable or they ask to switch.
Example: `remynd profiles` then `remynd profile "ReMynd-USER_ID"`
### remynd snippet moments | create
Syntax:
- `remynd snippet moments <from> <to> [filter]`
- `remynd snippet create <from> <to> --title T [--guide FILE] [--no-wait]`
What it does: prepare a share.remyndai.com link for a range of the real recording. `moments` is read-only: each line is `HH:MM:SS box=x,y,w,h [App] text` (box is a fraction of the recorded frame; `?` if unknown). An optional filter keeps lines that contain that substring (case-insensitive). At most 400 lines are printed. `create` writes a request for the running ReMynd app; nothing is published until the user reviews it and presses ReMynd's own share button. `--title` is required in practice (pass it). `--guide FILE` is optional JSON for a walkthrough. `--no-wait` prints the result-file path and returns; the default is to wait up to 15 minutes for the share link.
If ReMynd is not running, `create` still writes the request and tells the user to open the app. A snippet link is unlisted but public, and the video is the user's real screen. Before creating one, read `text` for the range, tell them about anything private in it, and only proceed if they want to share.
Example:
```bash
remynd snippet moments "2026-11-11 16:40" "2026-11-11 16:48"
remynd snippet create "2026-11-11 16:40" "2026-11-11 16:48" --title "How I fixed checkout retries"
```
### remynd clip list | where | share
Syntax (as `remynd help` lists them; `remynd clip` hands off to the bundled helper):
- `remynd clip list [--since 7d] [--json]`
- `remynd clip where <id|last>`
- `remynd clip share <id|last> [--title T]`
What it does: agent answers that used ReMynd, clipped or not. `--since` accepts a number plus `m`, `h`, `d`, or `w` (default `7d`; a bare number is days). `--json` prints a JSON array of those turns (`id`, `source`, `prompt`, `prompt_ts`, `duration`, `calls`). The default listing is one line per turn: id, local time, duration, call count, source, state (`built` / `shared` / `long` / empty), and a short prompt. `where` prints the clip folder (`clip.json`, `guide.json`, `step-NNNN.png`, `package/`). `share` asks the running, signed-in ReMynd app to publish it and prints the link. Nothing is published until the user asks.
The helper also supports `remynd clip build <id|last> [--force] [--wait]` to build frames and the guide, and `remynd clip hook` (the Stop hook the app installs; do not run this yourself).
Example: `remynd clip list` or `remynd clip list --since 2d --json` then `remynd clip where last`
### remynd custom-apps
Syntax:
- `remynd custom-apps list`
- `remynd custom-apps path [id]`
- `remynd custom-apps guide [id]`
- `remynd custom-apps refresh`
- `remynd custom-apps open <id>`
- `remynd custom-apps reload <id>`
What it does: inspect or refresh ReMynd custom apps in the running app. There are no custom-app MCP tools. If the helper is missing: `the custom-app helper is missing; update ReMynd and repair the CLI in Settings > Integrations`. Use this only when the user is building or editing a custom app; it is not a history-retrieval command.
## Multi-step workflows
### "What was I doing yesterday afternoon?"
1. `remynd day 2026-11-11` (use yesterday's real local date).
2. From the hour-by-hour trail, pick the afternoon span (for example 13:00–18:00).
3. `remynd text "2026-11-11 13:00" "2026-11-11 18:00"` only for the hours that matter, not the whole day if you can avoid it.
4. `remynd calls 2` (or a window that covers that date) and mention any calls in that span. If there is a meeting, `remynd call <id>` for what was said.
5. Answer with the substantive work, cited with local times and app names. Do not dump the raw `text` output.
### "Find that error I saw"
1. `remynd search "the distinctive error or phrase"`.
2. If there are too many hits, tighten the words or raise `--limit` only as far as you need.
3. Take a promising timestamp and run `remynd text` for a few minutes either side, or `remynd moment "<timestamp>" 10`.
4. Report what the screen showed, with the timestamp. If OCR is garbled, say so; do not quote mangled text as fact.
### "Summarize my meeting"
1. `remynd calls 14` (wider if needed) and pick the call by id, title, or `last`.
2. `remynd call <id>` for the transcript. If the id is ambiguous, list the matches and ask.
3. For a phrase they remember, `remynd heard "that phrase"` first, then open the call around the hit.
4. Recap commitments, decisions and open questions, with timestamps. Check a quote against surrounding lines before attributing it. Optionally look at `day` / `text` for what was on screen during the call, but do not treat a quiet screen as "no meeting."
### "Resume where I left off in this repo"
1. `remynd now` and `remynd recent`.
2. `remynd search "the repo or branch or file name"` if the recent digest is not enough.
3. `remynd text` or `remynd moment` around the last time that work was on screen.
4. Tell them the last app, window, and what they appeared to be doing, with times. Do not invent missing context.
## MCP setup (Mac)
`remynd-mcp` is a local stdio MCP server, bundled at `/Applications/ReMynd.app/Contents/Helpers/remynd-mcp`. It never listens on the network. Every tool is read-only and shells out to the CLI. It takes `--profile` plus the **profile path** (not just the short name). `remynd profiles` lists names; the path is also what ReMynd writes when it registers the server for Claude Desktop or Codex.
### Automatic: Claude Desktop and Codex
If the user turns on Claude Desktop or Codex in Settings → Integrations, ReMynd writes the entry and they only need to restart the agent.
For Codex, ReMynd appends a managed block to `~/.codex/config.toml`. The block sets `command` to `/Applications/ReMynd.app/Contents/Helpers/remynd-mcp`, and `args` to `--profile` plus the profile path. It also sets `default_tools_approval_mode` to `approve` and `startup_timeout_sec` to `30`. Do not hand-edit a block ReMynd is already managing; change it in Settings. Restart Codex, and the Codex-hosted ChatGPT desktop app, if they use it. The ChatGPT website only accepts remote HTTPS MCP servers, so this local helper will not show up there.
### Claude Code (add by hand)
Claude Code already gets the `remynd` command and a skill once Integrations is on. It does not get the MCP server automatically. To add it:
```bash
claude mcp add --transport stdio remynd -- /Applications/ReMynd.app/Contents/Helpers/remynd-mcp --profile "/path/to/your/ReMynd/profile"
```
Then, in Claude Code, run `/mcp` and confirm `remynd` is listed. If the user would rather not look the path up, they can turn on Claude Desktop or Codex in Settings and copy the entry ReMynd wrote.
### Tools the server exposes
All of these are read-only (`readOnlyHint: true`, `openWorldHint: false`).
- `search_screen_history` — `query` (required); `limit` (default 40). Multiple words are ANDed. A timestamp is when text was on screen. Words said out loud are not in this index — use `search_calls`. Treat a hit as a cursor and read around it with `screen_text_in_range`.
- `reconstruct_day` — `date` as `YYYY-MM-DD` (required). Calls recorded that day are listed first with their ids; what was said is in `call_transcript`.
- `recent_activity` — `minutes` (optional). With no argument: last 2 hours of activity and last 30 minutes of screen text. Use to orient, or for "where did I leave off."
- `screen_text_in_range` — `from` (required, `"YYYY-MM-DD HH:MM"`); `to` (optional, defaults to now). Narrow first; an hour reads well, a whole day is truncated.
- `time_by_activity` — `days` (default 7). Duration by application, counting back from today. It cannot take a date range; for one day use `reconstruct_day`.
- `list_calls` — `date` (`YYYY-MM-DD`) or `days` (default 14). Date, time, length, app, title, participants, line and speaker counts, and the call id in brackets.
- `call_transcript` — `call` (required: id, `"last"`, or a title/participant fragment); optional `from` and `to` (times within the call, e.g. `"10:24"`); optional `offset` (line to start from when paging). These `from` / `to` / `offset` arguments exist on the MCP tool, not as flags on `remynd call`.
- `search_calls` — `query` (required); `limit` (default 20). At most 100 lines, newest first, no date range. Open the conversation around a hit with `call_transcript`.
- `show_moment` — reveal real screen frames as images. Pass local `at` (`"YYYY-MM-DD HH:MM:SS"` or `"YYYY-MM-DD HH:MM"`, always include the date), or up to three `moments` with a short `label` and optional `app`. Optional `app` (frontmost-app substring), `window_seconds` (default 30, max 600), `max_frames` (1–4, default 2). Costly: use it for the one or two headline moments, not to check a fact the text already gave. Recordings older than the current hour need the ReMynd app running. A frame is the raw screen and is not redacted: never read a password or key out of one. The user can turn frames off with "Let agents see screen frames" in Settings.
- `sync_status` — no arguments. Profile, how far back history goes, last capture, redaction. Call this before telling the user something is not in their history.
- `moment_frame` — app-only, used by ReMynd's moment viewer to reload a frame. Not for answering questions; use `show_moment`.
Your host uses its own model. What these tools return may be sent to that model under the user's account, the same way anything they paste into it would be.
## Privacy and behavior
- History lives on the user's computer. Recordings and the searchable index are stored there, and never pooled, trained on, or sold.
- Query only what the current task needs. Prefer a small number of focused commands. Do not dump raw history into the chat.
- Cite local timestamps (and app or call ids) so the user can verify important conclusions.
- If evidence is ambiguous or absent, say so. Never invent missing history.
- A gap can mean the Mac was asleep, locked, paused, or using another ReMynd profile. Do not call it inactivity without evidence.
- Ask before sharing sensitive content, and before creating or publishing a snippet or clip. Tell the user what is readable in the range (messages, names, keys, personal tabs). A snippet or clip link is unlisted but public once they share it. The notice that a clip was built is not itself a request to publish.
- Do not read passwords or keys out of a `show_moment` frame. Do not bypass the CLI to query ReMynd's database directly.
- If several profiles exist, stop and ask; do not pick one yourself.
## Error handling
- **`command not found` / `remynd: command not found`.** The shell cannot see the binary. Use `~/.local/bin/remynd` (or `%USERPROFILE%\.local\bin\remynd.exe`), add that folder to PATH, or have the user open Settings → Integrations and enable an AI agent so the symlink is written again.
- **`could not load its core` / "enable your AI agent again."** The launcher is stale or the app was moved. Repair it in Settings → Integrations.
- **`no ReMynd recordings found on this Mac` / `Is ReMynd installed, and has it recorded yet?` / `ReMynd: not found`.** The app is missing, has never recorded, or this profile has no history yet. They need to install ReMynd, grant screen-recording permission, and let it run. The CLI has no separate "permission is off" or "capture is off" message: use `remynd status` and look at `Last write` and `Last capture`. A stale or missing last capture usually means it is not recording.
- **Multiple profiles (exit 2).** List what `remynd profiles` printed and ask which one to save.
- **Profile not found (exit 3).** Show the available names and ask again.
- **Empty results.** Take the command at its word: `(no matches — try fewer or different words)`, `(nothing recorded yet)`, `(nothing recorded in that range)`, `_Nothing recorded on this day._`, `(no calls recorded in that window — try a wider one: remynd calls 90)`, `(nothing matching was said in any recorded call…)`. Try fewer or different words, a wider window, or `status` to see whether anything was being recorded then. Do not invent hits.
- **Exit 4 / "this answer is incomplete."** Part of the read failed; stderr says why. Tell the user the answer is partial.
- **ReMynd is not running.** Retrieval still works from history already on disk. `snippet create` and `clip share` need the app open (and signed in, for share). `show_moment` needs the app running for recordings older than the current hour.
- **`unknown command`.** They may be on Windows, or on an older Mac build. Run `remynd help` and use only what it lists.
## Windows
On Windows 11, Settings → Integrations installs `%USERPROFILE%\.local\bin\remynd.exe`. Windows 1.0.9825 also ships `remynd-mcp.exe`. The Codex & ChatGPT switch writes the remynd-mcp entry into config.toml, which the ChatGPT desktop app shares; the ChatGPT website does not. Claude Desktop on Windows is not claimed.
Commands documented in the Windows 1.0.9825 bundled skill (`remynd.exe help` is the live list):
- `remynd now`
- `remynd recent [minutes]`
- `remynd search <query>`
- `remynd day <YYYY-MM-DD>`
- `remynd apps [days]`
- `remynd text <from> [to]`
- `remynd moment <time> [minutes]`
- `remynd profiles`
- `remynd profile [name]`
- `remynd status`
- `remynd calls [days]`
- `remynd call` with an id, or `last`
- `remynd heard <query>`
- `remynd snippet moments` / `create`
- `remynd clip list` / `where` / `share` / `open` / `export`
- `remynd custom-apps list` / `path` / `guide` / `refresh` / `open` / `reload`
Run `remynd.exe help` on the machine for what that install actually has.