Prompts
Featured
Models
Submit
Blog

AhaPrompt

AI Prompts for Images, Video & Audio — Every Model, One Library

Explore

All Prompts
Featured Prompts
Image Prompts
Video Prompts
Audio Prompts
AI Models
Submit a Prompt
Blog

Languages

English
中文
日本語
한국어

Copyright © 2026 AhaPrompt All rights reserved.

Privacy Policy Terms of Service

HomeAI Prompt LibraryAI Video PromptsCodex Hierarchical Subagent Workspace Setup

Codex Hierarchical Subagent Workspace Setup

GPT-6 AstraOpenAIvideo

Configure my Codex workspace for hierarchical model selection and subagents: 1. Audit ~/.codex/agents and .codex/agents for subagent profiles fitting lead, workers, and adversary: > Give explorer, worker, and researcher model = 'gpt-6-luna', model_reasoning_effort = 'medium' > Assign worker an isolated git worktree branch to eliminate concurrent file conflicts > Create .codex/agents/adversary.toml with model = 'gpt-6-astra' (upgradeable to 'gpt-6.1-astra'), model_reasoning_effort = 'high', sandbox_mode = 'read-only' 2. Configure model selection in ~/.codex/config.toml: [session] model = 'gpt-6.1-sol' model_reasoning_effort = 'high' [agents] default_subagent_model = 'gpt-6-luna' default_subagent_reasoning_effort = 'medium' max_concurrent_threads_per_session = 8 3. Verify environment variables and routing: check for flags overriding reasoning effort or disabling multi-agent tools. Report them, change nothing 4. Add automatic delegation rules to AGENTS.md: > Summon @ adversary before finalizing multi-file architecture plans > Automatically trigger @ adversary when a test or compiler error repeats twice > Enforce @ adversary contract audit before declaring tasks complete or staging git commits Show every configuration diff first. Do not apply edits until confirmed

Details

Type: AI Video Prompts
Aspect Ratio: 391:480
Duration: 0:25
Updated: Oct 12, 2026

Category

Sci-Fi Game Assets Minimalist

How to use this prompt

1Copy the full prompt with the copy button above.
2Open GPT-6 Astra by OpenAI, or your preferred AI video generator.
3Paste the prompt and keep the camera and motion terms — they steer the cinematography.
4Match the example's settings (391:480 · 0:25 · Sci-Fi · Game Assets · Minimalist), then iterate — small wording changes shift the output a lot.

Frequently asked questions

Which AI model generated this video?

This clip was generated with GPT-6 Astra by OpenAI. The prompt on this page is the exact text used to create it.

What settings does this prompt use?

The example was generated with GPT-6 Astra using: 391:480 · 0:25 · Sci-Fi · Game Assets · Minimalist. Reusing these settings gives the closest match.

How do I get similar results?

Copy the prompt as-is first, then change the subject while keeping the camera, motion, and lighting terms. Video models are sensitive to wording, so expect a few runs.

Can I modify this prompt?

Yes. Prompts work best as starting points — swap scenes, adjust pacing terms, or change the aspect ratio to fit your project.

More GPT-6 Astra prompts

Rebuild my Codex setup around this tree: • Configure persistent dot agent on GPT-6 Astra with cloud container and headless browser access • Set up workspace bridges to route routine dev logs to files and critical architectural gates to Slack • Delegate multi-file coding tickets to local Codex CLI environments with automatic task locking • Add one rule to AGENTS.md: pause autonomous execution and request manual take-over before modifying external infrastructure or security configs Show every change as a diff first. No edits until I say go

build a huge, highly detailed recreation of New York in this Minecraft world. area: 1,024 by 1,024 blocks, centered on the spawn point. plan first, build second. write the plan to a file before you place a single block. the plan must list the districts: financial district, midtown, Central Park and the waterfront. it must also list the road grid with avenues and cross streets, at least 100 skyscrapers of different heights and materials, and the main landmarks. use only vanilla blocks and Minecraft commands: /fill, /setblock, /forceload. build in modules, one district at a time. after each module, check that the blocks are where the plan says, fix what's off, then move on. write one progress line after every module. don't ask me questions, keep working until the whole map is done.

Rebuild my Codex setup around this tree. 1. Agents - scan ~/.codex/agents and .codex/agents for anything that already fits explorer, worker or researcher - draft TOML only for missing roles: explorer and researcher on gpt-6-luna, worker on gpt-6.1-sol, all at model_reasoning_effort medium - explorer and researcher get a read-only sandbox, only worker can write - skip agents pinned to another model and list them 2. Architect - add an architect on gpt-6-astra, model_reasoning_effort high, read-only sandbox - its only jobs: review plans, repeated errors and finished work - feed it the plan, the diff and the failing log, never the full transcript - force one output shape: verdict (proceed / revise / stop), top 3 risks, one cheaper path, under 200 words - cap it at 3 calls per task 3. Main config - in ~/.codex/config.toml set model to gpt-6.1-sol, model_reasoning_effort to high, approvals_reviewer to auto_review 4. Overrides - find anything that would beat this: active profiles, flags in shell aliases, agents.default_subagent_model - report it, change nothing 5. Rules - add to the AGENTS file in the repo root: spawn the architect before a large plan, when the same error signature shows up twice, and before calling a long task done - log every architect call with its trigger and verdict to .codex/architect-log.jsonl Check that every TOML file parses, then show me all changes as one diff. No edits until I say go.

Set up model routing for this repo: 1. List this month's task types and how long each answer was. Table only, change nothing 2. Anything that ended past 128K goes to Gemini 4 Argon as one call, no chunking > Terminal and shell work stays on Opus 5.5 > Fixes that failed twice go to GPT-6 Astra > Cache the repo context on Argon so every run reuses it 3. Price each task type at Argon's intro rate next to what it costs today 4. Print the routing table with the price column, then wait for my yes before switching anything.

Act as a security engineer reviewing a repository Analyze the supplied scanner findings and affected source files Prioritize exploitable issues over informational warnings For each confirmed issue, provide the root cause, affected location, minimal patch, and regression test Do not invent vulnerabilities or claim a fix passed without test evidence Never expose secret values in the report

You are the founder, GPT-6 Astra is the operator, and every function of the company becomes a node with an owner, an output and a check. Seven layers do the work: > Functions -> nodes, edges, parallel work. > Agents -> one subagent per node, only the context it needs. > Code nodes -> anything with one correct answer runs as code. > Permissions, gates, return paths, weekly review. The founder approves money, hiring and anything public. Everything else runs in the loop and lands in company.md, checks.md and progress.md

Do a full animation with sound of anthropic mascote with the newset model of Opus 5.5 fighting against OpenAI mascotte with the new astra models Sol etc like the intro of pokemon fire red and leaf green. Same animations

Build a detailed sports car that transforms into a humanoid robot, with an x-ray mode and interactive exploded view

Browse all GPT-6 Astra prompts Explore AI Video Prompts