nc://long-conversations

Long Conversations: handoff briefs that carry a session's state past its context limit, so a fresh session continues where the last one stopped. A Nodecode rewrite of cspears32/hermes-long-conversations by cspears32.

Before a session runs out of context, the model writes a brief: the topic, what is in progress, the decisions already settled, the files in play, the assumptions, the open questions, the dead ends not to try again, and the next step. A brief is a JSON file in a folder you name, so it outlives the process that wrote it. When the next session makes its first model request, it reads the brief once and starts knowing where the work stood.

Four tools — handoff_save, handoff_list, handoff_load, handoff_prune — and /long-conversations, which lists the briefs, shows one, prunes the old ones, or starts one from a topic. Nothing leaves the machine, and there is no key.

Get it

Tell the agent "add the long-conversations cell", or run nodecode add nc://long-conversations.

Set it up

One required setting: the folder the briefs are kept in.

{
  "long-conversations": {
    "data_dir": "~/.nodecode/long-conversations/",  // the folder; one brief a JSON file
    "keep_days": 14,                      // older briefs are pruned at start
    "pending": true                       // hand a saved brief to the next session
  }
}

data_dir has no default on purpose: the briefs describe your work, kept where you say. Without it the cell refuses at start and names the member. The section is in /settings too.

Use it

Ask for it plainly; the model writes the brief:

We are near the end of the context — write a handoff brief.

Then, in a new session:

Read the last handoff brief and carry on.

From the keyboard, /long-conversations shows the briefs with the ones you can open; /long-conversations show ID reads one, /long-conversations latest the newest, /long-conversations prune deletes the old ones, and /long-conversations save TOPIC keeps a brief for the model to fill in.

A brief deliberately stays small: a topic, a few lists, a next step. Detail belongs in the files the brief names, not in the brief. It arrives in the new session as data from the session before — what was decided and what failed — not as instructions from you.