cc-status

Diagnoses Codex configuration sync state and project task status.

1.0k|109|Updated Jan 4, 2026
One-click install
npx skills add https://github.com/doccker/cc-use-exp --skill cc-status
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cc-status
Source: https://github.com/doccker/cc-use-exp/tree/main/.codex/skills/cc-status
Command: npx skills add https://github.com/doccker/cc-use-exp --skill cc-status

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

When Codex CLI configurations drift between the project-level authoritative source and user-level deployed files, or when task persistence fails silently, it is hard to tell whether files were never synced, rules never took effect, or the session is stuck in a restricted sandbox. This Skill provides a structured diagnostic workflow that pinpoints the exact gap.

Core Features & Use Cases

  • Configuration Sync Audit: Compares project .codex/ sources against user-level ~/.codex/ and ~/.agents/skills/ deployments, checking managed blocks, manifests, and profile counts.
  • Rule Effectiveness Sampling: Uses codex execpolicy check to verify that allow/prompt/forbidden rules actually behave as expected on sample commands.
  • Task State Inspection: Reviews .codex/tasks/ for active tasks, conflicting in-progress markers, interrupted work, and missing new-feature persistence prerequisites.
  • Use Case: After running a sync script, ask for a status check to confirm that rules, instructions, skills, and profiles all landed correctly and that the current project can persist tasks.

Quick Start

Ask the AI to run a Codex status check on the current project to verify configuration sync and task state.

Frequently Asked Questions about cc-status

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

FAQPage Schema
How do I check if my Codex CLI configuration synced correctly?

Run a structured status check that compares the project .codex/ source against user-level ~/.codex/ and ~/.agents/skills/ deployments. It verifies managed blocks, manifest files, profile counts, and reports any quantity mismatches or missing items.

How to verify Codex execpolicy rules are actually working?

Use codex execpolicy check to sample-test commands against your rules. For example, docker ps should return allow, docker compose down should return prompt, and rm -rf tmp should return forbidden.

Why does Codex task persistence fail even when directories exist?

When .codex/tasks/ exists but writes still fail, the session is usually running in a restricted sandbox or workspace scope rather than the project root. The diagnostic distinguishes genuine missing directories from permission boundary interception.

What causes multiple tasks marked in-progress in Codex?

Multiple simultaneous in-progress tasks indicate task state drift in .codex/tasks/. The recommended fix is to converge the mainline and candidate tasks using the cc-task-state skill before continuing work.

When should I not use this Codex status check?

Do not use it for Claude or Gemini status diagnosis, formal code review, or changing project code implementation. It is scoped strictly to Codex configuration state and .codex task status inspection.