Save Thread

nowledge-co/community/nowledge-mem-claude-code-plugin/skills/save-thread

by nowledge-co1f4d7eb61466dbfc93ce8d7a0a806c4d4a196dd0No licenseListed Oct 9, 2026Updated Oct 9, 2026

Save the real Claude Code or Grok Build session messages only when the user explicitly requests it. Use nmem t save to import the recorded session, not a summary-only checkpoint.

Instructions onlyProductivity & Workflow

AI-generated overview

Saves real Claude Code or Grok Build session messages to an nmem thread when the user explicitly asks.

What it does: This skill instructs the agent to import the current coding session into nmem using the nmem t save command, choosing the source app (claude-code or grok). It supports options for a brief summary, saving the current session or all sessions, a specific project path, and truncating large tool results. It also documents the expected confirmation response and troubleshooting steps such as installing nmem-cli or configuring a remote server.
When to use it: Use it only when the user explicitly asks to save, checkpoint, or record the conversation. It is not meant to run automatically or be suggested proactively.
Requirements: Requires the nmem CLI (installable via pip install nmem-cli, or yay/paru on Arch Linux) and access to local session files under ~/.claude/projects/ or ~/.grok/sessions/. Remote use needs a configured server URL and API key. No scripts ship with the skill.

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 projectnmem t save --from claude-code# In Grok Build:nmem t save --from grok
# Save with custom summarynmem 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 projectnmem t save --from claude-code -m all# In Grok Build:nmem t save --from grok -m all
# Save for specific project pathnmem t save --from claude-code -p /path/to/project# In Grok Build:nmem t save --from grok -p /path/to/project

# Save current session for current projectnmem t save --from claude-code# In Grok Build:nmem t save --from grok
# Save with custom summarynmem 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 projectnmem t save --from claude-code -m all# In Grok Build:nmem t save --from grok -m all
# Save for specific project pathnmem 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 savedSummary: {summary}Messages: {count}Thread ID: claude-code-{session_id} or grok-{session_id}

✓ Thread savedSummary: {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.

Source and attribution

Source:nowledge-co/communityinnowledge-mem-claude-code-plugin/skills/save-threadat commit1f4d7eb

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal

Save Thread

Save Thread

When to Save

Tool Usage

Thread vs Memory

Response

Troubleshooting

Source and attribution

More from nowledge-co/community

Read Working Memory

Search Memory

Save Thread

Distill Memory

Search Memory

Save Thread

More in Productivity & Workflow

Morning Note

Dd Meeting Prep

Dd Checklist

Deal Tracker

Client Review

Morning Note