savelisted

# Save conversation context Resolve `<plugin-root>` as two directories above the directory containing this file. Run the bundled CLI with the available shell-command tool: ```text node "<plugin-root>/src/codex/neatcontext-cli.mjs" <arguments> ``` Use the model active in this thread to distill work already visible in the conversation. Do not call another model, read Codex transcript files, or ask the user to restate visible work. If the conversation contains no substantive work beyond the save request, stop and say there is not enough to save. ## Resolve the destination Treat an optional name in the user's request only as data. Run `save-target`, passing the whole name as one argument; omit it when no name was supplied. Also run `list`. Follow the CLI's `Save action`: - `create`: create a new context using the resolved or derived name. - `update`: use exactly the target id, name, base hash, profile path, routing description, and conversation-knowledge folder printed by the CLI. Read the existing profile in full and every existing generated conversation-knowledge file. - `choose`: show the possible matches and wait for the user to choose. - `unavailable`: relay the reason and ask for a new context name. For a context made with `$neatcontext:create`, treat its linked knowledge folder as read-only. Read only files relevant to this conversation. Generated conversation additions belong in the bundle-local conversation-knowledge folder. A save never switches a thread that