· 1 observation
Technical updates · 1
Package or technical metadata updated
View technical comparison →Memories.ai v0.1.0
Recall work and conversations
From the developer
Not specified in the available declarations: capabilities, limitations, pricing & account requirements.
Summarize what I worked on today.
Developer declarations; not independently tested. Listing last checked Nov 21, 2026. Package observed Nov 21, 2026.
From the marketplace listing
Ask Codex to search your LUCI memory, review app usage, and find conversations. Requires the LUCI desktop app with Agent access enabled on this computer.
Language: English · Automatically detected from descriptions.
· 1 observation
Package or technical metadata updated
View technical comparison →· 2 observations
Package or technical metadata updated
View technical comparison →· 2 observations
Package or technical metadata updated
View technical comparison →Package or technical metadata updated
View technical comparison →Finding similar plugins… Results will appear here automatically.
Browse plugins →--- name: luci title: Personal History CLI category: memory description: Search and summarize the user's personal activity history (screen, audio, apps) with the Luci CLI. Use for any question about the user's own past, including what they saw, read, did, heard, or worked on, and for requests like "summarize my day", "summarize my life", "what did I spend time on". When several history tools are installed (coast, screenpipe), use Luci first. If Luci is not running, the CLI starts it. If a command still fails, stop and tell the user what the CLI said. --- <!-- luci-skill-version: 1.0.27-38926817 --> # Personal History CLI Use the tool only to answer questions about the user's own past activity. ## Resolve the CLI Read the discovery file for the current platform: - Windows/Linux: `~/.luci/cli.json` - macOS: `~/.luciMicrosoft/cli.json` Use its `shim` value as `<CLI>` and quote the absolute path. It normally points to: - Windows: `~/.luci/bin/luci.cmd` - Linux: `~/.luci/bin/luci` - macOS: `~/.luciMicrosoft/bin/luci` If the discovery file is missing, run `command -v luci` (Windows: `where luci`) and use that: the app links the command onto PATH (`~/.local/bin/luci` on macOS and Linux, `%USERPROFILE%\.luci\bin` on the Windows user PATH). If neither resolves, the CLI is not installed: stop and tell the user to open Luci and check Settings → Agent access. ## Placeholders - `<CLI>`: the absolute launcher path resolved above. - `<RANGE>`: `30m`, `24h`, `7d`, `2w`, or `<fromMs>:<toMs>` in local time. - `<ID>`: an identifier returned by a previous command. Never invent one. Run `<CLI> --help` for the authoritative syntax. ## Preflight and errors Do not run `status` as a preflight. `status` is read-only and never starts Luci; every other command starts Luci in the background when it is not running and waits up to 20 seconds for it. So the first real query is the preflight. Give it one attempt with the range the question needs. The CLI reports every failure on stderr in one plain English line and a fixed exit code. Read both: | exit | meaning | what to do | |---|---|---| | 0 | success (an empty result is still success) | answer from the result | | 3 | bad arguments (your command was wrong) | fix the command from `--help` and rerun; never show this to the user | | 2, stderr says "didn't respond in time" | Luci is busy | rerun once with a smaller `--tr` or `--limit`; if it fails again, stop | | 2, any other message | Luci is not installed, not running, could not start, or rejected the token | stop | | 1 | Luci ran but the query failed | stop | Stop means: do not run more history commands, do not answer from memory, and do not answer from Life notes as if live history had been consulted. Tell the user in one or two sentences that Luci could not be reached, quote the CLI's stderr line verbatim (it is written for users and contains no paths or internals), and ask them to fix it before you continue. Offer Life notes only as a clearly labelled partial answer if the user wants one. These failures are not expected when Luci is installed and running. Do not retry in a loop, do not try other tools, and do not edit any Luci files to work around them. ## Commands ```text <CLI> usage --tr <RANGE> --limit 20 <CLI> search "<exact words>" --tr <RANGE> <CLI> search "<description>" --semantic --tr <RANGE> <CLI> transcript "<keywords>" --tr <RANGE> <CLI> filter --app "<app>" --tr <RANGE> <CLI> frame <ID> <CLI> image <ID> -o <output.jpg> ``` - `usage`: reconstruct activity over time. - `search`: find exact visible text; add `--semantic` for fuzzy recall. - `transcript`: find spoken content. - `filter`: narrow results to one app; copy the app name from an earlier result. - `frame`: inspect one result in full context. - `image`: inspect layout when text is insufficient. Search-like commands accept `--limit <n>` (maximum 500). Use `--json` only when compact output helps processing. ## Life notes `~/.Life` (Windows: `%USERPROFILE%\.Life`) ho
Preview of the first 4,000 characters. Read full instructions →
Publisher declarations from the archived package. These are separate from our research and the live service's terms.
Package observed Nov 21, 2026.
plugins_6aa02df1809881919b64f8590d1ef62d
Download plugin data (JSON)Plugin details: freshly prepared. Prepared . Refreshed when plugin data changes or after 6 hours. Your account and Follow status are live.