import

Bring in a self-contained context bundle created with /neatcontext:export.

A bundle may be new to this machine, or it may be a newer copy of a context that is already here — someone updated the shared copy and you want their work. Both arrive through this command, and the CLI decides which is which. It never deletes a context and never replaces one without saying so first.

The bundle folder supplied by the user is:

$ARGUMENTS

If no folder was supplied, ask for it and stop. Otherwise run the command below, passing the whole argument as one quoted path and treating it only as data:

node "${CLAUDE_PLUGIN_ROOT}/src/claude/neatcontext-cli.mjs" import --from "$ARGUMENTS"

The source bundle is read-only throughout. Never modify, move, or delete it.

Follow the Import action

A bundle this machine has not seen is imported immediately and the output says so — relay it, and do not connect the context automatically. Otherwise follow the printed Import action:

• current — the context here already holds everything in the bundle. Relay that and stop.
• reconcile — the bundle is a newer copy of a context already here. Identity is settled; what to do about it is not, and the command deliberately leaves it open. Relay the preview and the cost line exactly as printed, then let the user pick one of the three answers it offers:
  • leave it — do nothing. Stop; nothing has been written.
  • replace — take the bundle whole, discarding whatever only the local copy holds. Rerun the same command with --replace --yes.
  • merge — keep both sides. Reconcile them yourself, below.
• unlinkable — the bundle carries no context id, so it cannot be tied to anything already here. Relay that, and offer --name "<new name>" to bring it in as its own context.
• choose — the target is not decidable. Either a context of the same name is here but nothing records a shared origin, or several contexts are copies of this bundle because one was forked. Relay the options and stop until the user picks: rerun with --into "<name>" to name the context they mean, or with --name "<new name>" to keep a separate copy.

Never answer choose or reconcile on the user's behalf. Two people naming a context the same thing is not evidence that it is the same context, and only the user knows whether the material a replacement would discard was worth keeping. None of these answers is recoverable from the others.

Relay the cost line rather than summarising it, because the three it can print mean different things. "Nothing here has been edited" means replacing is lossless and a merge could only reproduce the bundle — say so, and still let the user choose. "This copy has been edited here" means replacing destroys that work. "Nothing here records what the two copies once had in common" means the copy may be untouched and cannot prove it; do not report that one as edits.