azoth-park

Suspend Codex sessions and preserve state via the park command.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/yiwei79/azoth --skill azoth-park
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: azoth-park
Source: https://github.com/yiwei79/azoth/tree/main/.agents/skills/azoth-park
Command: npx skills add https://github.com/yiwei79/azoth --skill azoth-park

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Explicit Codex entrypoint for Azoth's /park workflow. Use when the user wants to run /park in Codex via /skills or $azoth-park.

Codex uses skills as the custom command surface for Azoth workflows. In the Codex app, enabled skills may appear in the slash command list. In Codex CLI/IDE, use /skills or $azoth-park. This skill is the explicit Codex-native equivalent of typing /park.

Execution contract:

  • Read .claude/commands/park.md and follow it as the source of truth.
  • Treat the rest of the user's prompt after $azoth-park as $ARGUMENTS.
  • Preserve the command's stage structure, gate rules, evaluation rules, and referenced skills/agents.
  • Preserve the command's agent: orchestrator binding.
  • Respect the command's azoth_effect: write contract.
  • If the user typed literal /park in prompt text instead, apply the same workflow contract.

Command metadata:

  • Source path: .claude/commands/park.md
  • Description: Park the current session for later resumption

Quick Start

Invoke the park command to suspend the current Codex session for later resumption.

Frequently Asked Questions about azoth-park

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

FAQPage Schema
How do I pause a Codex session and resume it later?

You can park a Codex session by invoking the /park command or $azoth-park skill to suspend your active workflow. It reads the park.md command file and preserves session state for later resumption.

What does parking a workflow session actually do?

Parking a workflow session suspends the current Codex orchestrator state by saving the active context. This allows you to safely pause work and return later without losing the session's stage structure and progress.

Can I use the park command in Codex CLI and IDE environments?

Yes, the park command works across Codex CLI and IDE environments. You can invoke it via /skills or $azoth-park, and it will follow the same orchestrator binding and execution contract to suspend your session.

Do I need any dependencies to park and resume Codex sessions?

No external dependencies are required to park and resume Codex sessions. The skill operates independently by reading the local .claude/commands/park.md file as the source of truth for the suspension workflow.

What is the best way to suspend an active orchestrator workflow in Codex?

The best way to suspend an active orchestrator workflow in Codex is using the /park command. It explicitly respects the orchestrator binding and write contract to safely preserve the session state for later resumption.

Why does my parked session need to follow gate rules and evaluation rules?

Parked sessions follow gate rules and evaluation rules to ensure the preserved state remains structurally valid for resumption. This maintains the command's stage structure and orchestrator binding throughout the pause cycle.