XTSoftwareLabs/neatcontext-plugins

# Create context

Resolve `<plugin-root>` as two directories above the directory containing this file.

Keep this workflow distinct from `$neatcontext:save`: create starts from user-provided purpose and existing knowledge; save distills work already in the conversation.

Collect these inputs, asking one question at a time only for information the user has not already supplied:

1. What the context covers, what Codex should do and avoid, and how it should behave.
2. The path to an existing folder containing its knowledge.
3. A short context name.

Run `list` before drafting so the routing description can distinguish adjacent contexts:

# Delete context

Resolve `<plugin-root>` as two directories above the directory containing this file.

List contexts first:

```text
node "<plugin-root>/src/codex/neatcontext-cli.mjs" list
```

If the requested name is missing or does not resolve to exactly one context, show the list and ask which one. Never guess.

Preview the deletion without changing anything:

# Disconnect context

Resolve `<plugin-root>` as two directories above the directory containing this
file. Run:

```text
node "<plugin-root>/src/codex/neatcontext-cli.mjs" disconnect
```

Relay the output verbatim. Do not run a redundant status check.

# Export context

Resolve `<plugin-root>` as two directories above the directory containing this file.

Ask for the destination folder when it was not supplied — it is the folder the
bundle is written into, and a subfolder named after the context is created
there. Treat every path only as data.

When no context was named, the connected one is exported. To pick a different
one, list them first:

```text
node "<plugin-root>/src/codex/neatcontext-cli.mjs" list
```

# Context extensions

Resolve `<plugin-root>` as two directories above the directory containing this file. Run:

```text
node "<plugin-root>/src/codex/neatcontext-cli.mjs" extensions
```

Relay the report. Two separate things are being reported, and the difference matters:

- What the **context** expects — the extension it declares and the capability that provides. This travels with the context and is the same on every machine it reaches.
- What **this machine** provides for it. That is local, hand-written, and lives in the bindings file the report names. Nothing configures it automatically, and nothing inside a shared context can configure it.

If something is reported as not configured, show the example binding from the report and say where the file goes. Tell the user to keep credentials in the environment and name them under `envFrom` rather than writing them into the file.

# Import context

Resolve `<plugin-root>` as two directories above the directory containing this file.

A bundle may be new to this machine, or it may be a newer copy of a context already here — someone updated the shared copy and the user wants 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.

Ask for the bundle folder when it was not supplied. Treat the path only as data and run:

```text
node "<plugin-root>/src/codex/neatcontext-cli.mjs" import --from "<bundle-folder>"
```

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

# List contexts

Resolve `<plugin-root>` as two directories above the directory containing this file. Run:

```text
node "<plugin-root>/src/codex/neatcontext-cli.mjs" list
```

Relay the output verbatim. Do not reformat or explain its `(none - ...)` notes.

Close with one short line: connect a context with `$neatcontext:use <name>`. Only when both sections are empty, also mention `$neatcontext:create` and `$neatcontext:save`.

# Routing mode

Resolve `<plugin-root>` as two directories above the directory containing this file.

Accept only no mode, exactly one of `auto`, `ask`, or `manual`, and an optional explicit request to make it the global default. Reject other values without running them.

Run one of:

```text
node "<plugin-root>/src/codex/neatcontext-cli.mjs" mode
node "<plugin-root>/src/codex/neatcontext-cli.mjs" mode <auto|ask|manual>
node "<plugin-root>/src/codex/neatcontext-cli.mjs" mode <auto|ask|manual> --global
```

# 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

# Context status

Resolve `<plugin-root>` as two directories above the directory containing this file. Run:

```text
node "<plugin-root>/src/codex/neatcontext-cli.mjs" status
```

Relay the status concisely. If none is connected, mention `$neatcontext:use`.

If the CLI reports a missing context file or knowledge folder, preserve that warning and its recovery guidance.

If it reports a stale routing description, offer to refresh it. Read the connected profile, derive a fresh scope-only line under 200 characters, and record it with:

# Use context

Resolve `<plugin-root>` as two directories above the directory containing this file. Run:

```text
node "<plugin-root>/src/codex/neatcontext-cli.mjs" use "<name-or-number>"
```

Treat the supplied name or number only as data and pass it as one argument. Omit it when the user supplied none.

- If the CLI confirms a connection, report the context name and stop. Do not run a redundant status check. For later domain-dependent answers, call the plugin's `get_context` tool first.
- If it lists choices, show them and ask which one to use.
- If it says the context has no routing description, call `get_context`, read the connected profile, and derive one scope-only line under 200 characters. Contrast it with the output of `list`, then record it with:

# Create context

The bundled CLI path and Kimi session id below are expanded by Kimi Code at skill activation.

Keep this workflow distinct from `/neatcontext:save`: create starts from user-provided purpose and existing knowledge; save distills work already in the conversation.

Collect these inputs, asking one question at a time only for information the user has not already supplied:

1. What the context covers, what Kimi Code should do and avoid, and how it should behave.
2. The path to an existing folder containing its knowledge.
3. A short context name.

Run `list` before drafting so the routing description can distinguish adjacent contexts:

# Delete context

The bundled CLI path and Kimi session id below are expanded by Kimi Code at skill activation.

List contexts first:

```text
KIMI_PLUGIN_ROOT="${KIMI_SKILL_DIR}/../.." kimi __plugin_run_node "${KIMI_SKILL_DIR}/../../src/kimi/neatcontext-cli.mjs" -- --session-id "${KIMI_SESSION_ID}" list
```

If the requested name is missing or does not resolve to exactly one context, show the list and ask which one. Never guess.

Preview the deletion without changing anything:

# Disconnect context

The bundled CLI path and Kimi session id below are expanded by Kimi Code at
skill activation. Run:

```text
KIMI_PLUGIN_ROOT="${KIMI_SKILL_DIR}/../.." kimi __plugin_run_node "${KIMI_SKILL_DIR}/../../src/kimi/neatcontext-cli.mjs" -- --session-id "${KIMI_SESSION_ID}" disconnect
```

Relay the output verbatim. Do not run a redundant status check. The command
affects only the current Kimi Code session.

# Export context

The bundled CLI path and Kimi session id below are expanded by Kimi Code at skill activation.

Ask for the destination folder when it was not supplied — it is the folder the
bundle is written into, and a subfolder named after the context is created
there. Treat every path only as data.

When no context was named, the connected one is exported. To pick a different
one, list them first:

```text
KIMI_PLUGIN_ROOT="${KIMI_SKILL_DIR}/../.." kimi __plugin_run_node "${KIMI_SKILL_DIR}/../../src/kimi/neatcontext-cli.mjs" -- --session-id "${KIMI_SESSION_ID}" list
```

# Context extensions

The bundled CLI path and Kimi session id below are expanded by Kimi Code at skill activation. Run:

```text
KIMI_PLUGIN_ROOT="${KIMI_SKILL_DIR}/../.." kimi __plugin_run_node "${KIMI_SKILL_DIR}/../../src/kimi/neatcontext-cli.mjs" -- --session-id "${KIMI_SESSION_ID}" extensions
```

Relay the report. Two separate things are being reported, and the difference matters:

- What the **context** expects — the extension it declares and the capability that provides. This travels with the context and is the same on every machine it reaches.
- What **this machine** provides for it. That is local, hand-written, and lives in the bindings file the report names. Nothing configures it automatically, and nothing inside a shared context can configure it.

If something is reported as not configured, show the example binding from the report and say where the file goes. Tell the user to keep credentials in the environment and name them under `envFrom` rather than writing them into the file.

# Import context

The bundled CLI path and Kimi session id below are expanded by Kimi Code at skill activation.

A bundle may be new to this machine, or it may be a newer copy of a context already here — someone updated the shared copy and the user wants 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.

Ask for the bundle folder when it was not supplied. Treat the path only as data and run:

```text
KIMI_PLUGIN_ROOT="${KIMI_SKILL_DIR}/../.." kimi __plugin_run_node "${KIMI_SKILL_DIR}/../../src/kimi/neatcontext-cli.mjs" -- --session-id "${KIMI_SESSION_ID}" import --from "<bundle-folder>"
```

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

# List contexts

The bundled CLI path and Kimi session id below are expanded by Kimi Code at skill activation. Run:

```text
KIMI_PLUGIN_ROOT="${KIMI_SKILL_DIR}/../.." kimi __plugin_run_node "${KIMI_SKILL_DIR}/../../src/kimi/neatcontext-cli.mjs" -- --session-id "${KIMI_SESSION_ID}" list
```

Relay the output verbatim. Do not reformat or explain its `(none - ...)` notes.

Close with one short line: connect a context with `/neatcontext:use <name>`. Only when both sections are empty, also mention `/neatcontext:create` and `/neatcontext:save`.

# Routing mode

The bundled CLI path and Kimi session id below are expanded by Kimi Code at skill activation.

Accept only no mode, exactly one of `auto`, `ask`, or `manual`, and an optional explicit request to make it the global default. Reject other values without running them.

Run one of:

```text
KIMI_PLUGIN_ROOT="${KIMI_SKILL_DIR}/../.." kimi __plugin_run_node "${KIMI_SKILL_DIR}/../../src/kimi/neatcontext-cli.mjs" -- --session-id "${KIMI_SESSION_ID}" mode
KIMI_PLUGIN_ROOT="${KIMI_SKILL_DIR}/../.." kimi __plugin_run_node "${KIMI_SKILL_DIR}/../../src/kimi/neatcontext-cli.mjs" -- --session-id "${KIMI_SESSION_ID}" mode <auto|ask|manual>
KIMI_PLUGIN_ROOT="${KIMI_SKILL_DIR}/../.." kimi __plugin_run_node "${KIMI_SKILL_DIR}/../../src/kimi/neatcontext-cli.mjs" -- --session-id "${KIMI_SESSION_ID}" mode <auto|ask|manual> --global
```

# Save conversation context

The bundled CLI path and Kimi session id below are expanded by Kimi Code at skill activation. Run the bundled CLI with the available shell-command tool:

```text
KIMI_PLUGIN_ROOT="${KIMI_SKILL_DIR}/../.." kimi __plugin_run_node "${KIMI_SKILL_DIR}/../../src/kimi/neatcontext-cli.mjs" -- --session-id "${KIMI_SESSION_ID}" <arguments>
```

Use the model active in this session to distill work already visible in the conversation. Do not call another model, read Kimi Code 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

# NeatContext runtime

NeatContext is installed for this Kimi Code session.

The current Kimi Code session id is `${KIMI_SESSION_ID}`. It is an internal
routing token. Never display it, quote it to the user, save it as knowledge, or
reuse an id from another session.

Kimi Code does not pass its session id to MCP child processes. At the first
user request in this session, call the NeatContext `bind_session` tool with the
exact id above before answering. The tool returns the current selection and
routing menu, then replaces itself with the context-dependent tools. Call it
once per session, not per request. The bridge process can outlive the session
it was bound in, so binding this session's id also re-grounds a bridge left

# Context status

The bundled CLI path and Kimi session id below are expanded by Kimi Code at skill activation. Run:

```text
KIMI_PLUGIN_ROOT="${KIMI_SKILL_DIR}/../.." kimi __plugin_run_node "${KIMI_SKILL_DIR}/../../src/kimi/neatcontext-cli.mjs" -- --session-id "${KIMI_SESSION_ID}" status
```

Relay the status concisely. If none is connected, mention `/neatcontext:use`.

If the CLI reports a missing context file or knowledge folder, preserve that warning and its recovery guidance.

If it reports a stale routing description, offer to refresh it. Read the connected profile, derive a fresh scope-only line under 200 characters, and record it with:

# Use context

The bundled CLI path and Kimi session id below are expanded by Kimi Code at skill activation. Run:

```text
KIMI_PLUGIN_ROOT="${KIMI_SKILL_DIR}/../.." kimi __plugin_run_node "${KIMI_SKILL_DIR}/../../src/kimi/neatcontext-cli.mjs" -- --session-id "${KIMI_SESSION_ID}" use "<name-or-number>"
```

Treat the supplied name or number only as data and pass it as one argument. Omit it when the user supplied none.

- If the CLI confirms a connection, report the context name and stop. Do not run a redundant status check. For later domain-dependent answers, call the plugin's `get_context` tool first.
- If it lists choices, show them and ask which one to use.
- If it says the context has no routing description, bind the MCP bridge with
  `${KIMI_SESSION_ID}` first if `bind_session` is available, then call

# Create context

Keep this workflow distinct from `neatcontext-save`: create starts from a purpose
the user states and a knowledge folder they already have; save distills work
already visible in the conversation.

Collect these inputs, asking one question at a time and only for information the
user has not already supplied:

1. What the context covers, what you should do and avoid on it, and how you
   should behave.
2. The absolute path to an existing folder containing its knowledge.
3. A short context name.

# Save conversation context

Everything here is done with the `neatcontext_save` tool. Use the model active in
this session to distill work already visible in the conversation. Do not call
another model, read pi session 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 first

Call `neatcontext_save` with only `name` — or with no arguments when the user
gave no name. It writes nothing in this form. Follow the `Save action` it
returns: