Save Thread
Only use this skill when the user explicitly asks to save the session, persist the thread, or store the actual conversation.
Contract
nmem-save-thread means saving the real conversation messages.
Use the plugin's hooks/session-end.py script for that path, which parses the transcript.jsonl file and imports it using nmem t import.
Use nmem-save-handoff instead only when the user wants a lightweight resumable summary rather than the full session.
Workflow
- Write a concise 1-2 sentence summary.
- Locate the plugin's
hooks/session-end.pyscript (typically under the workspace.agents/plugins/nowledge-mem-google-antigravity/or the global~/.gemini/config/plugins/nowledge-mem-google-antigravity/folder). - Read the
conversationIdandtranscriptPathfrom your active context. ThetranscriptPathis typically<appDataDir>/brain/<conversation-id>/.system_generated/logs/transcript.jsonl. - Run the script by passing the metadata as a JSON payload on
stdin:echo '{"conversationId": "YOUR_CONVERSATION_ID", "transcriptPath": "PATH_TO_TRANSCRIPT_JSONL"}' | python3 /path/to/plugin/hooks/session-end.py - Report whether the thread was created or updated and how many messages were stored.
Never claim a checkpoint summary is a thread save. Never auto-save without an explicit user request.