---
name: Save Thread
slug: save-thread-2
category: Automation
description: Save Thread imports real Claude Code or Grok Build session messages into nmem when the user explicitly asks to save a session. It is used for checkpointing conversations, not for summaries or automatic saves.
github: "https://github.com/nowledge-co/community/tree/main/nowledge-mem-claude-code-plugin/skills/save-thread"
language: Python
stars: 166
forks: 35
install: "npx degit https://github.com/nowledge-co/community/tree/main/nowledge-mem-claude-code-plugin/skills/save-thread ~/.claude/skills/save-thread"
installs_to: ~/.claude/skills/save-thread
source_path: nowledge-mem-claude-code-plugin/skills/save-thread/SKILL.md
collection_size: 25
category_size: 2226
collection_url: "https://dirskills.com/collections/nowledge-co/community"
added: 2026-09-08T05:34:52.097Z
last_synced: 2026-09-08T05:34:52.097Z
canonical_url: "https://dirskills.com/skills/save-thread-2"
---

# Save Thread

Save Thread imports real Claude Code or Grok Build session messages into nmem when the user explicitly asks to save a session. It is used for checkpointing conversations, not for summaries or automatic saves.

**Install:**

```bash
npx degit https://github.com/nowledge-co/community/tree/main/nowledge-mem-claude-code-plugin/skills/save-thread ~/.claude/skills/save-thread
```

## README

# Save Thread

## When to Save

**Only when user explicitly says:**
"Save this session" | "Checkpoint this" | "Record conversation"

Never auto-save or suggest.

## Tool Usage

Use `nmem t save` to import the current session. Use `claude-code` in Claude Code and `grok` in Grok Build:

```bash
# Save current session for current project
nmem t save --from claude-code
# In Grok Build:
nmem t save --from grok

# Save with custom summary
nmem t save --from claude-code -s "Brief summary of what was accomplished"
# In Grok Build:
nmem t save --from grok -s "Brief summary of what was accomplished"

# Save all sessions for current project
nmem t save --from claude-code -m all
# In Grok Build:
nmem t save --from grok -m all

# Save for specific project path
nmem t save --from claude-code -p /path/to/project
# In Grok Build:
nmem t save --from grok -p /path/to/project
```

**Options:**
- `--from`: Source app (`claude-code` for Claude Code, `grok` for Grok Build)
- `-s, --summary`: Optional brief summary (recommended)
- `-m, --mode`: `current` (default, latest session) or `all` (all sessions)
- `-p, --project`: Project directory path (defaults to current directory)
- `--truncate`: Truncate large tool results (>10KB)

**Behavior:**
- Auto-detects sessions from `~/.claude/projects/` for Claude Code or `~/.grok/sessions/` for Grok Build
- Idempotent: Re-running appends only new messages
- Thread ID: Auto-generated as `claude-code-{session_id}` or `grok-{session_id}`

## Thread vs Memory

Thread = real session messages | Memory = distilled insights (different purposes, can do both)

## Response

```
✓ Thread saved
Summary: {summary}
Messages: {count}
Thread ID: claude-code-{session_id} or grok-{session_id}
```

## Troubleshooting

If `nmem` is not in PATH: `pip install nmem-cli`, or on Arch Linux `yay -S nmem-cli` / `paru -S nmem-cli`

For remote servers: run `nmem config client set url https://...` and `nmem config client set api-key ...` once on this machine.

Run `/status` to check server connection.