Save this chat to RAMen
save_threadSave the current chat's state to continue in a fresh chat or another AI app without re-reading the full thread, cutting token use and keeping key details.
Instructions
Save where this conversation stands, so it can go on in a fresh chat or in another AI app (Claude, ChatGPT or any app with RAMen Memory) without re-reading this whole chat: every reply in a long chat re-reads all of it, which uses up tokens and usage limits. Use it when the user asks to save the chat or to continue it in a new chat or elsewhere, or when the chat has grown long. Be complete and specific: every name, number, date, time, price and reason, every change (with what it was before), and the latest version of anything you wrote together, word for word. Saving again under the same name adds to the thread and updates its values.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"thread": "<thread>",
"goal": "<goal>",
"now": "<now>",
"facts": "<facts>",
"decisions": "<decisions>",
"open": "<open>",
"drafts": "<drafts>"
},
"name": "save_thread"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| now | Yes | values that can change (dates, counts, budgets, choices, status): the current value, and the one before if it changed | |
| done | No | open items finished since the last save (their words) | |
| goal | Yes | what this work is for, in one sentence | |
| open | Yes | the open questions, to-dos and deadlines now (this list replaces the saved one) | |
| facts | Yes | everything else that holds: names, places, times, prices, numbers, people's roles, constraints, preferences; one specific, self-contained sentence each | |
| drafts | Yes | every piece written together (emails, messages, lists, plans, wording), each in its latest version, word for word; do not leave drafts out to save space: they are what a new chat cannot rebuild | |
| thread | Yes | a short name for this work, for example 'wedding planning' | |
| project | No | the project the user puts this work in, if they name one, for example 'wedding' | |
| decisions | Yes | each decision, why, and what was turned down | |
| checkpoint | No | true for a save you make on your own about every 15 messages in a long chat (the user's "Save long chats as they go" setting decides; RAMen answers 'Not saved' when it is off) |