跳到正文
cccskills
免费在 GitHub 公开

cognee-switch-datasets

Switch this session to another Cognee dataset, or back to the previous one, so later saves and recalls use it. Takes a dataset name (created if new) or lists writable datasets to pick from; syncs this session first.

中文简介正在准备中。当前显示原文说明。

查看安装方法

包含的文件(1)

  • SKILL.md4.9 KB

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

Switch Datasets

Move this Claude Code session to a different Cognee dataset. A Cognee session never spans two datasets, so the switch retires the current session (after syncing it into the graph) and starts a new one on the chosen dataset.

Faster, with the hooks module loaded

Where Claude Code loads the plugin's hooks module (2.1.287+), the user can switch without a model turn: /cognee-dataset <name> from the prompt (/cognee-dataset alone lists the datasets), or the dataset name in the status row above the prompt, which is a picker (in a terminal, focus it with ctrl+x tab). If the user asks you to switch, run this skill as below; if they ask how to switch themselves, point them there.

Instructions

1. If the user named a dataset, switch directly

When $ARGUMENTS contains a dataset name, skip the picker:

python3 "${CLAUDE_PLUGIN_ROOT}/scripts/switch-dataset.py" "$ARGUMENTS" --json

2. Otherwise, list and let the user choose

python3 "${CLAUDE_PLUGIN_ROOT}/scripts/switch-dataset.py" --list --json

The JSON has current, datasets ([{name, id, writable, current}]), hidden_readonly (datasets you can read but not write — never offered) and filtered (true when write access was verified for every row).

Present the choice with AskUserQuestion (single select), listing the dataset names from datasets with the current one marked "(current)". The tool allows four options per question, so if there are more than four, put the first three plus a "More…" option and page on the next question. The user can always type a name via the built-in "Other" — a name that is not listed is created for them on switch. If filtered is false, say so in the question text ("write access could not be verified for these").

Then run the switch with the chosen name:

python3 "${CLAUDE_PLUGIN_ROOT}/scripts/switch-dataset.py" "<chosen name>" --json

3. Report the result

On success the JSON is {"switched": true, "dataset", "session_id", "previous": {"dataset", "session_id", "synced": true|false}}. Tell the user in one line which dataset and Cognee session are now active and that the previous session was synced. The status line updates within a couple of seconds. If "switched": false with "reason": "already_active", say the session is already on that dataset.

On failure the JSON is {"error", "code"}:

codemeaningwhat to do
2launch record not foundthe plugin did not initialise this session; run "${CLAUDE_PLUGIN_ROOT}/scripts/cognee-doctor.sh". If several Claude Code sessions share this directory, rerun with --session-key <host session id>
3syncing the current session failednothing was changed; show the error. Re-run with --force only if the user explicitly accepts that unsynced entries of the current session are retried at session end instead
4registering the new session failednothing was changed; the server rejected the registration — check the connection
5dataset not writablethe name is readable but owned by another principal; pick from --list

What the switch does

  1. Syncs the current session into its dataset (sync-session-to-graph.py --strict) — aborts if this fails.
  2. Ensures the target dataset exists for this principal.
  3. Registers a new Cognee session on the target dataset under a fresh connection handle, then releases the old handle (register-then-unregister, so a local agent-mode server never sees zero connections).
  4. Repoints this launch's record: every hook, the shell wrappers, the idle/exit watchers and the status line follow it.
  5. Retired sessions stay in the record's touched list; the session-end sync covers them again as a safety net.

Notes

  • A switch is not needed just to look in another dataset: a one-off graph search leaves the session where it is — "${CLAUDE_PLUGIN_ROOT}/scripts/cognee-search.sh" "<query>" 10 --graph --dataset-id <id> (see the cognee-search skill).

  • COGNEE_PLUGIN_DATASET only seeds the dataset at launch; a switch overrides it for the rest of the session and survives --resume.

  • Recall is scoped to the active dataset, so after a switch earlier context from the previous dataset is no longer injected — switch back to see it again.

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

codebase

免费

Use when indexing a code repository into Cognee's code graph or querying it (callers, impact analysis, paths, endpoints) from Codex.

中文简介正在准备中。当前显示原文说明。

topoteretes/cognee-integrations1012026年10月20日 更新

codebase

免费

Use when indexing a code repository into Cognee's code graph or querying it (callers, impact analysis, paths, endpoints) from Antigravity.

中文简介正在准备中。当前显示原文说明。

topoteretes/cognee-integrations1012026年10月20日 更新

Explain a repository's architecture (modules, routes, storage, services), find risky hotspots, draw a Mermaid diagram of the code graph, or review how far a change reaches, from Cognee's code graph.

中文简介正在准备中。当前显示原文说明。

topoteretes/cognee-integrations1012026年10月20日 更新

Index a repository (local path or git URL) into Cognee's code graph and answer exact structural queries with no LLM calls: callers, dependencies, impact of changing a symbol, call paths, endpoints, re-index changes.

中文简介正在准备中。当前显示原文说明。

topoteretes/cognee-integrations1012026年10月20日 更新

A digest of a week or more of the user's own coding-agent sessions (default 7 days): sessions per day and project, most-edited files and the lessons Cognee learned, written up as shipped, decided and still open.

中文简介正在准备中。当前显示原文说明。

topoteretes/cognee-integrations1012026年10月20日 更新

A multi-day digest of the user's own coding-agent sessions — sessions per day and project, most-edited files, and every lesson Cognee distilled into the knowledge graph in that window. Use only when the user explicitly asks for a weekly digest, a retro, a recap or report of their recent sessions, or asks for the `cognee-digest` skill by name. Not for questions about code or the current task.

中文简介正在准备中。当前显示原文说明。

topoteretes/cognee-integrations1012026年10月20日 更新

查看 topoteretes 的全部技能

报告此技能的问题