subcodex

Create and resume named Codex sessions with a Bash CLI.

5|Updated Jan 8, 2026
One-click install
npx skills add https://github.com/zippoxer/claude-skills --skill subcodex
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: subcodex
Source: https://github.com/zippoxer/claude-skills/tree/main/skills/subcodex
Command: npx skills add https://github.com/zippoxer/claude-skills --skill subcodex

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Managing Codex sessions manually is error prone and breaks context; subcodex provides named, persistent sessions so you can resume work across conversations.

Core Features & Use Cases

  • Create new named Codex sessions and persist conversations across chats.
  • Resume ongoing sessions with prompts and track progress, including status, PID, and duration.
  • Review and collaborate with Codex for complex coding tasks, design iterations, and code reviews with persistent history.

Quick Start

Create a new session by running subcodex new my-session 'Describe the task'.

Frequently Asked Questions about subcodex

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I save and resume Codex sessions across multiple prompts?

You can save and resume Codex sessions by creating a named session with a CLI subcommand. This persists the conversation state and context, allowing you to resume long-running coding tasks or iterative discussions across multiple prompts without losing history.

What is the best way to manage context for long-running AI code reviews?

The best way to manage context for AI code reviews is using a session management tool that persists conversation history. This approach stores the review state and integrates with Codex tooling, enabling you to resume complex iterative discussions without context loss.

Does a CLI workflow tool track the status and duration of active coding sessions?

Yes, a CLI workflow tool can track the status and duration of active coding sessions. It monitors session state, including the current status, process ID, and duration, so you can track progress on long-running tasks and reviews.

Can I import existing conversations into a new persistent Codex session?

Yes, you can import existing conversations into a new persistent Codex session. The CLI includes an import subcommand that integrates prior context, allowing you to seamlessly resume work on complex coding tasks or design iterations.

Why does my Codex session lose context when I close the terminal?

Your Codex session loses context because standard terminal sessions are not persistent by default. Without a session management tool to store the conversation state, closing the terminal breaks the context and history required for iterative discussions.