Safe Long-Run Mode (GPT-5.4 Only)

---

name: safe-long-run-mode-gpt54

description: Operate long-running tasks safely when the environment is optimized for GPT-5.4 as the primary and often only model. Use when the user wants a low-cost, high-throughput long-run workflow, plans to keep everything on GPT-5.4, or asks how to run long coding, research, build, documentation, Azure, or multi-agent tasks safely without relying on Claude.

---

# Safe Long-Run Mode (GPT-5.4 Only)

Use this skill when GPT-5.4 is the default operating model for both orchestration and delegated work.

Core rule

Use GPT-5.4 for long work by making tasks cheap, segmented, and resumable. Since the model layer is cost-efficient, the real risks are provider throttling, session interruption, and lack of checkpoints.

When to use this mode

Use it when:

Operating procedure

1. Route to GPT-5.4 by default

Use GPT-5.4 for:

Do not escalate to another model unless the user asks or the task clearly requires premium polish/judgment.

2. Split work aggressively

Break long tasks into explicit phases and write down the next step before moving on.

Preferred phases:

1. inspect

2. plan

3. execute

4. validate

5. report

3. Save progress continuously

Always leave artifacts that make recovery easy:

4. Use subagents as workers

For large or parallel tasks, use subagents to keep the main thread clean.

Delegate when:

5. Treat external APIs as the true bottleneck

In GPT-5.4-only mode, model cost is not the main concern. External limits are.

Be careful with:

Use batching, backoff, and fewer larger writes.

6. Make every task resumable

If interrupted, resume from artifacts instead of recreating work. Always know:

Ideal GPT-5.4-only use cases

What to tell the user

Explain that GPT-5.4-only safe mode works because:

Failure handling

If interrupted:

1. summarize completed work

2. cite the saved files

3. state the resume point

4. continue from the last checkpoint

References