بنقرة واحدة
migrate
Migrate your main session context into the current thread
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
القائمة
Migrate your main session context into the current thread
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Register bot commands with Telegram so they appear in the command menu
Rebuild miniclaw and restart the background service
Interactive setup wizard for new miniclaw users who just forked the repo
Summarise recent conversations across all threads into auto memory (MEMORY.md + topic files)
Analyse chat history to update voice and typing style guide (voice.md in auto memory)
Create a semver release with changelog, git tag, and GitHub release
| name | migrate |
| description | Migrate your main session context into the current thread |
This skill copies the main (non-threaded) Claude session into the current thread so you retain full conversation context.
Read the MINICLAW_THREAD_ID environment variable.
If it is 0 or empty, tell the user:
This command only works inside a thread. Open a thread first, then send /migrate there.
Stop here.
Read the file ~/.miniclaw/data/sessions.json. This is a JSON object mapping session keys to Claude CLI session UUIDs.
Key format:
"<chatID>" — the main (non-threaded) session"<chatID>:<threadID>" — a thread-specific sessionLook up the main session using the plain MINICLAW_CHAT_ID value (no colon, no thread suffix).
If no main session exists, tell the user:
No main session found to migrate. There's nothing to copy.
Stop here.
Build the thread key: "<MINICLAW_CHAT_ID>:<MINICLAW_THREAD_ID>".
If a session already exists for this thread key, tell the user:
This thread already has a session. Migrating will replace it with the main session's context. Do you want to proceed?
Wait for confirmation before continuing. If the user declines, stop here.
Tell the user what will happen:
I'll copy the main session into this thread. The main session will remain intact so it can still be used in non-threaded mode.
Proceed?
Wait for the user to confirm.
~/.miniclaw/data/sessions.json again (fresh read in case it changed)sessions["<chatID>:<threadID>"] = sessions["<chatID>"]~/.miniclaw/data/sessions.jsonTell the user:
Done. This thread now has the same context as your main session. Your next message here will resume with full history.