A persistent coding terminal for OpenClaw. It creates a tmux session per project:

-code-session

This makes terminal-first AI coding (Codex CLI / Claude Code / any CLI tool) reliable and mobile/SSH friendly:

• detach/reattach without losing output
• keep shell state across turns
• keep long-running tasks alive (dev server, watch mode, etc.)

OpenClaw natural-language routing

When user intent is "use natural language to drive Codex CLI in this repo", route through this skill first.

Intelligent auto-trigger:

• Routing toggle: openclaw.config.dev.autoCodeRouting (default false).
• If enabled, route coding workflow messages via:

• The route script applies:

Multi-project routing:

• One message can include multiple project tasks split by newline / ； / ;
• Supported patterns:

• Execution is serial per project:

• Invalid/unknown project tasks are reported as failed without blocking other tasks.

Trigger shortcuts (recommended):

• If user message starts with codex , treat the remaining text as instruction.
• Execute:

• Then report with:

Preferred execution pattern in chat-driven runs:

• start.sh (or implicit auto-create from send.sh)
• codex-exec.sh "" for Codex-driven work
• status.sh / summary.sh for concise progress reporting

If user says "检查项目/继续会话/跑测试并总结", use this skill scripts instead of asking user to type long shell commands.

Core model (must follow)

start → send → read → decide

1) Start/ensure session:

• {baseDir}/bin/persistent-code-terminal-start.sh

2) Send ONE command:

• {baseDir}/bin/persistent-code-terminal-send.sh ""

3) Read output:

• {baseDir}/bin/persistent-code-terminal-read.sh

4) Check state quickly (optional):

• {baseDir}/bin/persistent-code-terminal-status.sh
• {baseDir}/bin/persistent-code-terminal-summary.sh --lines 120
• {baseDir}/bin/persistent-code-terminal-doctor.sh
• {baseDir}/bin/persistent-code-terminal-list.sh (list *-code-session)
• {baseDir}/bin/persistent-code-terminal-switch.sh --project

State file:

• .pct-state.json (current project directory)
• Fields: projectDir, session, lastCommand, lastExitCode, phase, updatedAt

Structured output:

• {baseDir}/bin/persistent-code-terminal-read.sh --json
• {baseDir}/bin/persistent-code-terminal-summary.sh --json
• {baseDir}/bin/persistent-code-terminal-auto.sh --json

Codex-first workflow (one-shot)

If Codex CLI is installed as codex, prefer:

• {baseDir}/bin/persistent-code-terminal-codex-exec.sh ""
• Default behavior uses:

• You can pass additional flags before the instruction:

• Set PCT_CODEX_NO_DEFAULT_FLAGS=1 to disable default flags.

Example:

• {baseDir}/bin/persistent-code-terminal-codex-exec.sh "Implement feature X. Ensure build and tests pass. Commit and push to current branch. Do NOT force push."

Safety

• Never git push --force unless user explicitly requests.
• Keep secrets out of terminal output.
• Prefer feature branches; avoid direct pushes to main/master unless explicitly requested.
• For network/privileged actions (for example git push), follow active Codex approval/sandbox policy.