# AI use cases for DSH Memento (PerryLink/dsh-memento)

Repo: [PerryLink/dsh-memento](https://github.com/PerryLink/dsh-memento) | Use cases: 4 | Page: https://dedupedai.com/use-cases/perrylink-dsh-memento/

A DeepSeek Harness plugin that gives agent sessions bounded, approval-gated, auditable cross-session memory stored in a local SQLite database.

This file holds every use case of this repo. Each one starts with a "## " heading and ends with its URL.

- Keep workspace conventions across agent sessions: https://dedupedai.com/use-cases/perrylink-dsh-memento/keep-workspace-conventions-across-sessions/
- Review every memory write before it is saved: https://dedupedai.com/use-cases/perrylink-dsh-memento/approve-every-memory-write/
- Audit what the model saw and what it wrote: https://dedupedai.com/use-cases/perrylink-dsh-memento/audit-what-the-model-remembered/
- Find earlier session discussions with memory_recall: https://dedupedai.com/use-cases/perrylink-dsh-memento/recall-earlier-session-discussions/

## How to keep workspace conventions across agent sessions with DSH Memento

Repo: [PerryLink/dsh-memento](https://github.com/PerryLink/dsh-memento) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README

Store project facts once so each new DeepSeek Harness session starts with them in the system prompt.

**Who it is for:** A developer on DeepSeek Harness who keeps re-explaining the same test commands and repo conventions at the start of every session.

**The problem:** Each new session starts with no memory of project conventions, so the same context has to be typed again.

**The outcome:** Conventions saved in the agent track workspace layer appear in the frozen snapshot of every later session.

### Steps

1. Run `dsh plugin --profile web add dsh-memento` to install the plugin.
2. Run `dsh --profile web --dump-config | grep -A3 'id: memento'` to confirm the memento row is present.
3. Run `/memory add` and store one convention, such as the test command, in the agent track workspace layer. (inferred, check the README)
4. Start a new session and check that the stored convention is in the injected snapshot.

### Prompt to paste into your agent

```text
In the dsh-memento repo, store the test command for <project> in the agent track workspace layer with /memory add, then run /memory list. Expected output: the new entry listed under agent and workspace. Verify that the memory_stats total increased by one.
```

### Caveat

The repo has been FROZEN since 2026-10-05, so expect no new fixes and pin the version you install.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/perrylink-dsh-memento/keep-workspace-conventions-across-sessions/

## How to review every memory write before it is saved with DSH Memento

Repo: [PerryLink/dsh-memento](https://github.com/PerryLink/dsh-memento) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README

Keep writePolicy at ask so each add, replace, or remove waits for your approval.

**Who it is for:** A team lead or careful developer who does not want the model to write facts into memory without review.

**The problem:** A model may save incorrect or unwanted facts to long-term memory without anyone noticing.

**The outcome:** Every proposed write is held for approval, and a denied write leaves a *-denied audit row instead of changing memory.

### Steps

1. Run `dsh plugin --profile web add dsh-memento` to install the plugin.
2. Run `dsh --profile web --dump-config | grep -A3 'id: memento'` and confirm writePolicy is ask.
3. Trigger a memory write in a session and deny it in the approval prompt.
4. Run `/memory audit` and find the *-denied row for that write.
5. Run `/memory list` and confirm the denied entry is absent.

### Prompt to paste into your agent

```text
In the dsh-memento repo, confirm writePolicy is ask, trigger one memory write from <session>, deny it, then run /memory audit. Expected output: a *-denied audit row for that write. Verify that /memory list does not show the denied entry.
```

### Caveat

The gate only covers writes that go through the plugin service, and the README does not describe the approval prompt layout, so check the exact flow in your own harness build.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/perrylink-dsh-memento/approve-every-memory-write/

## How to audit what the model saw and what it wrote with DSH Memento

Repo: [PerryLink/dsh-memento](https://github.com/PerryLink/dsh-memento) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README

Rebuild the memory write history from the plugin audit table and the session log.

**Who it is for:** A security-minded engineer or reviewer who needs evidence of every memory change in a DeepSeek Harness profile.

**The problem:** Without a record, it is hard to tell which memory entries came from the model and which were approved by a person.

**The outcome:** A list of memory writes with their approval outcomes, plus a visible note where the session log does not record memory events.

### Steps

1. Run `/memory audit` to list the plugin audit table.
2. Read the gap line if it appears, which means the session log does not record memory event types.
3. Match each audit row with its approval/asked and approval/decided pair in the session log.
4. Set auditRetentionDays in the memento config if you need audit rows removed after a set number of days; 0 keeps them forever. (inferred, check the README)

### Prompt to paste into your agent

```text
Using the dsh-memento repo on profile <profile>, run /memory audit and list each write with its outcome. Expected output: rows from the plugin audit table, plus the session-log gap line if it is shown. Verify that each write has a matching approval/asked and approval/decided pair in the session log.
```

### Caveat

The README says the session log does not yet know the memory event types, so the audit is only complete when the approval pair and plugin table are both checked.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/perrylink-dsh-memento/audit-what-the-model-remembered/

## How to find earlier session discussions with memory_recall with DSH Memento

Repo: [PerryLink/dsh-memento](https://github.com/PerryLink/dsh-memento) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README

Search a bounded set of past session matches so a new session can pick up an earlier decision.

**Who it is for:** A developer returning to a project after several days who needs the reasoning from an earlier session.

**The problem:** Earlier decisions are scattered across old sessions, and reading full logs takes too long.

**The outcome:** A short list of relevant snippets from recent sessions, capped by the configured limits.

### Steps

1. Run `dsh plugin --profile web add dsh-memento` to install the plugin.
2. Call the memory_recall tool with a short query about the topic you need. (inferred, check the README)
3. Check that each session shows no more than recall.snippetCap snippets.
4. Adjust recall.windowDays or recall.snippetChars in the memento config if results are too narrow or too wide. (inferred, check the README)

### Prompt to paste into your agent

```text
In the dsh-memento repo, call memory_recall with the query "<topic>" and list the matched snippets. Expected output: bounded memory matches and recent session-history matches. Verify that no session returns more snippets than the recall.snippetCap setting.
```

### Caveat

Vector recall is off by default and uses a fake hash embedding, so keyword-style queries are the more reliable choice.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/perrylink-dsh-memento/recall-earlier-session-discussions/