video-workbench/AGENTS.md

Video Workbench Agent Rules

Text Encoding

All local project documents are UTF-8 unless a file explicitly declares another encoding.

When reading Markdown, JSON, YAML, text, handoff, prompt, or discussion files from PowerShell, use explicit UTF-8 by default:

Get-Content -LiteralPath <path> -Encoding UTF8
Select-String -Path <path> -Pattern <pattern> -Encoding UTF8

When writing text files, preserve UTF-8. Do not rely on PowerShell encoding defaults for Chinese Markdown.

CCPE Interface

The default external CCPE entrypoint is:

C:\Users\wangq\Documents\Codex\ccpe-system\Interface.md

For CCPE setup or invocation work, read that file first, then follow it to:

C:\Users\wangq\Documents\Codex\ccpe-system\runtimes\hybrid\ccpe-agent-consumer-setup.md

Do not hardcode old Agent, Lite, Skill, Runtime, or protocol paths as default CCPE entrypoints. Read narrower CCPE artifacts only when the consumer setup contract, a project-local registry, or the active task requires them.

Formal CCPE participant output requires a project-local registry, an invocation packet, a real participant carrier, and returned output saved only after the participant returns. Main-session roleplay is not formal CCPE output.

Image Prompt Workflow

All image-generation prompts in this repository must be produced through the gpt-image-2 Skill workflow. Do not draft final image prompts directly from memory or from a derived project skeleton alone.

Before writing any project-bound image prompt, run the Skill mode check and follow the resulting mode:

node C:\Users\wangq\.agents\skills\gpt-image-2\scripts\check-mode.js --json

• Mode A: use the Skill's Garden generation/edit scripts and save prompt/image traces under garden-gpt-image-2/.
• Mode B: use the Skill as a prompt-engineering workflow, save the rendered prompt, then pass it to the host image tool only after user approval.
• Mode C / Advisor: use the Skill as a high-quality prompt advisor, save the rendered prompt, and do not claim an image was generated.

Current default success path for project-bound image generation:

1. Generate the final prompt/spec with the gpt-image-2 Skill Advisor workflow.
2. When image references are needed, load the real reference image into the conversation context before generation.
3. Use the host image_gen tool with the loaded reference image assigned an explicit role such as Image 1.

Use this successful channel now and for future work. Do not switch normal Video Workbench image generation to API/Garden paths unless the user explicitly changes this policy.

For every project-bound image prompt document:

• Read the relevant gpt-image-2 Skill template or reference file before drafting.
• Record the Skill mode, template/reference path, and source files actually read.
• Treat accepted intake/ files and user-provided references as primary sources; use derived files such as visual-system.md, execution-plan.md, or slides/slides.md only as execution control summaries.
• If a prompt was drafted without the Skill workflow, label it as a non-generation-ready draft and rebuild it through the Skill before any image generation.
• When a local image outside the workspace is used, label its role explicitly as identity reference, edit target, or supporting reference, and do not proceed if the file cannot be read or approved.
• For near / identity-heavy shots, prefer a relevant crop reference. For distant / landscape-led shots, prefer the accepted anchor board or project-approved distant reference. Do not repeatedly re-ask whether references can work; the verified route is Skill Advisor prompt plus loaded reference image plus host image_gen.

Project-bound image generation must remain approval-gated: save the prompt/spec first, wait for user approval, then execute generation only when explicitly requested. A task-level user instruction that records the running mode and slide scope counts as explicit generation approval for that task scope. If the task mode is prompt only, do not generate images.

Slide Task Workflow

For long slide / video production work, use the local slide task orchestration workflow:

docs/workflows/slide-task-orchestration.md
docs/workflows/slide-task-templates.md

Runtime Vocabulary / Default Carrier

Use these terms as the default implementation contract for Video Workbench slide tasks. Do not re-investigate old session artifacts or broad runtime mechanism docs just to infer this mapping.

User term	Meaning	Default carrier
子会话 / session	A user-visible separate Codex session for brief / orchestration work, started from a clean prompt rather than inherited orchestration history.	codex_app.create_thread to create, codex_app.send_message_to_thread to continue, codex_app.read_thread to inspect.
继续前子会话	Continue the already recorded visible child session instead of creating a new one.	Send the next instruction to the recorded threadId.
Agent / SubAgent	An internal one-shot worker owned by the child session; it should not appear as a separate user-visible Codex session.	multi_agent_v1.spawn_agent(agent_type="worker"); one worker handles exactly one slide.
无 review	Review is disabled for the named scope.	Do not write sNN-vN-review.md; record only packet / return / ledger / task-log evidence.

Do not use codex_app.fork_thread as the default carrier for production child sessions. Forking copies completed orchestration history from the parent thread and can contaminate the child session's context. Use fork_thread only when the user explicitly wants an inherited-context branch.

If the default tools are not already exposed in a new session, use tool_search to expose create_thread, send_message_to_thread, read_thread, and spawn_agent by name, then proceed with this contract.

Default preflight for a slide/session run:

• confirm the target visible session id or create exactly one new clean visible session with create_thread;
• scan the target slide folder for the next unused sNN-vN-* version;
• set Overwrite allowed: no;
• record whether review is disabled or enabled;
• require the child session to launch internal one-shot SubAgents for slide work.

Production orchestration defaults:

• The main session dispatches, waits, reads the child session's short handoff, and continues. It should not audit prompt / return / ledger / image details when the child session reports complete with completion_gate: pass.
• Choose the wait schedule by package size: 1 slide sleeps 10 minutes before first status check, then polls every 1 minute up to 15 minutes total; 2 slides sleep 20 minutes before first status check, then poll every 1 minute up to 30 minutes total; 3 slides sleep 30 minutes before first status check, then poll every 1 minute up to 45 minutes total. Split packages larger than 3 slides unless a task plan explicitly defines a custom wait schedule.
• Parent-facing heartbeat/status updates during routine waiting default to every 5 minutes or material state changes. This is separate from the child-session status-check schedule and must not trigger extra thread inspection.
• The child session must run the mandatory completeness gate before returning: append-only version, no overwrite, expected files present, review present or absent as instructed, one owning worker per slide/version, references loaded or blocked, and compact handoff written.
• Instruction / visual review is optional. Run it only when the task asks for review; 无 review means no sNN-vN-review.md.
• A slide Agent / SubAgent is one-shot. It receives one packet, handles one slide/version, writes one return, then becomes terminal / closed. Do not continue or reuse a closed Agent; repairs, retries, and next slides require a new Agent.

Re-investigate runtime mechanics only when a tool is unavailable or errors, when an Agent becomes a user-visible session, when duplicate workers target the same slide/version, when target files collide, or when the user explicitly asks to revise the mechanism.

Rules:

• Use projects/<project>/tasks/<task-id>/ for local orchestration records.
• The main session talks with the user and defines worker profile, running mode, slide scope, and review expectations.
• Child sessions write per-slide briefs and may handle at most 3 slides by default.
• A slide agent handles exactly 1 slide per invocation.
• The default worker profile for current MV / video work is video-slide-production.
• Reserved future profile ppt-page-production may use docs/cases/, but must be designed when the first real PPT task needs it.
• visual-system/ is the production authority for slide work.
• Style continuity must use visual-system/style/style-prompt-master.md.
• Character continuity must use visual-system/characters/character-reference-registry.md and active character image references.
• Visible character identity cannot be generated from text-only prompts when identity matters.
• Slide prompts must use the gpt-image-2 Skill Advisor / host-native workflow.
• New slide-task execution must append the next unused sNN-vN-* version and must not overwrite existing slide artifacts unless the user explicitly authorizes an overwrite repair for named files.
• Review defaults to local-only. Do not call Minimax MCP or other external vision/review services unless the user explicitly authorizes that task.