How do I install the Ghostex Move Codex Session skill?

Run npx skillmds@latest add maddada/ghostex-move-codex-session in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Ghostex Move Codex Session safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Ghostex Move Codex Session?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Ghostex Move Codex Session free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Ghostex Move Codex Session?

maddada (@maddada) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Ghostex Move Codex Session by maddada

Name: Ghostex Move Codex Session
Author: maddada

Ghostex Move Codex Session

Explain how to fork an existing Codex CLI session into another folder by using `/status` to get the session id and `codex fork --yolo -C TARGET_FOLDER SESSION_ID`. Use when a user asks to move the current Codex session, change the Codex working directory, fork a Codex conversation into a different project folder, or continue a Codex thread under another workspace root as a separate session.

maddada 9b56bb4 2 files · 2.7 KB Updated Sep 17, 2026

File contents

ghostex-move-codex-session

Explain the supported Codex CLI workflow in simple numbered steps.

Steps

Ask the user to run this inside the current Codex session:
```
/status
```
Tell the user to copy the session id shown by /status.
Tell the user to open a shell and fork that session in the target folder:
```
codex fork --yolo -C ~/dev/hackathon <SESSION_ID>
```

Replace ~/dev/hackathon with the requested folder when the user gave a different target.

Tell the user that --yolo is the Codex alias for bypassing approvals and sandboxing. If they do not want full access, remove --yolo.

Fallback

If the user does not want to copy the id, suggest the recent-session fallback:

codex fork --all --last --yolo -C ~/dev/hackathon

Explain that --all matters because Codex normally filters fork candidates by the current working directory.

Rules

Keep the answer short and procedural.
Prefer codex fork --yolo -C <folder-path> <SESSION_ID> as the primary command.
Mention that this creates a separate forked Codex session under the new working root.
Mention that users can remove --yolo if they do not want full-access mode.
Do not claim the active running TUI can be moved in place unless current Codex docs expose a real command for that.
If the user asks for the exact command only, give only the command and one sentence.

---name: ghostex-move-codex-sessiondescription: Explain how to fork an existing Codex CLI session into another folder by using `/status` to get the session id and `codex fork --yolo -C TARGET_FOLDER SESSION_ID`. Use when a user asks to move the current Codex session, change the Codex working directory, fork a Codex conversation into a different project folder, or continue a Codex thread under another workspace root as a separate session.---# ghostex-move-codex-sessionExplain the supported Codex CLI workflow in simple numbered steps.## Steps1. Ask the user to run this inside the current Codex session: ```text /status ```2. Tell the user to copy the session id shown by `/status`.3. Tell the user to open a shell and fork that session in the target folder: ```bash codex fork --yolo -C ~/dev/hackathon <SESSION_ID> ```Replace `~/dev/hackathon` with the requested folder when the user gave a different target.Tell the user that `--yolo` is the Codex alias for bypassing approvals and sandboxing. If they do not want full access, remove `--yolo`.## FallbackIf the user does not want to copy the id, suggest the recent-session fallback:```bashcodex fork --all --last --yolo -C ~/dev/hackathon```Explain that `--all` matters because Codex normally filters fork candidates by the current working directory.## Rules- Keep the answer short and procedural.- Prefer `codex fork --yolo -C <folder-path> <SESSION_ID>` as the primary command.- Mention that this creates a separate forked Codex session under the new working root.- Mention that users can remove `--yolo` if they do not want full-access mode.- Do not claim the active running TUI can be moved in place unless current Codex docs expose a real command for that.- If the user asks for the exact command only, give only the command and one sentence.

Frequently asked questions