Tabbit
ResourcesBlogModels
Tabbit LogoTabbit

Tabbit — The AI Browser that Works for You

Topics

  • AI Browser Resources
  • Agentic Browser Resources
  • Browser Downloads and Install Guides
  • Browser Comparisons
  • AI Browser Alternatives
  • Browser Productivity Resources

Popular Guides

  • AI Browser
  • Agentic Browser Download
  • Best AI Browser 2026: Top 9 Tested & Ranked
  • AI Browser Download
  • Free AI Browser
  • Best AI Browser 2026
  • AI Browser Comparison 2026
  • AI Browser for Windows
  • AI Browser for Mac
  • Chrome Alternative 2026

Events

  • Tabbit Skill Competition
  • KPOP SBTI Fandom Personality Test
  • Tabbit Campus Creator Program
  • fifi's Picks: AI Skills for Research Papers
  • User Survey

About

  • Tabbit Blog
  • Press & Media
English
简体中文English
Prompts and workflows

GPT-5.6 Luna · prompting-guide

Reddit Codex: Diagnostic and Verification Prompt for Luna Subagent Compatibility

Turn “Reddit Codex: Diagnostic and Verification Prompt for Luna Subagent Compatibility” into a bounded task entry with explicit inputs, runtime context, output format, and acceptance checks; confirm the model version and source limits before use.

Source not verifiedA compatible model client or agent harness; confirm the live model, tools, and permissions before execution.

Prerequisites and inputs

  • Task goal
  • Relevant source material or repository
  • Runtime and tool constraints
  • Acceptance criteria

Complete templates

Editorial adaptation: task-specific reusable block

Tabbit editorial adaptation; not the original source prompt
Check Luna subagent configuration for {{CLIENT_VERSION}}. Use {{CONFIG_BACKUP}}, inspect {{MODEL_DIRECTORY}}, then validate with {{VALIDATION_TASK}} and preserve the diff.

Replace before running: {{CLIENT_VERSION}}, {{CONFIG_BACKUP}}, {{MODEL_DIRECTORY}}, {{VALIDATION_TASK}}

Task outcome

Diagnose whether the Luna subagent configuration matches the current Codex client and verify a reversible fix.

Prerequisites and environment

Use GPT-5.6 Luna with the client version, configuration file, expected schema, permission boundary, and a disposable test task.

Task-specific steps

Inspect the version and config, validate required fields, run a no-op subagent, then run one bounded task. Save logs and revert the config if the client rejects the schema.

Output and acceptance

Accept a compatibility report containing the observed version, validation output, task result, and rollback command. If fields are ignored, stop and map the config to the current schema instead of guessing.

Source and boundary

This is an editorial adaptation of a community compatibility note; it does not certify every Codex release or endpoint.

Read the source research notes

Summary

The post discusses a compatibility issue between Sol/Terra's Multi-Agent V2 and Luna V1 in Codex. The original post provides a complete prompt to "inspect, back up, modify, validate, and report," requiring the user to check the actual versions and model catalog rather than merely describe a solution. Someone later noted in the comments that Codex CLI 0.147.0 had fixed leaf model support, so this configuration patch may apply only to older versions or the desktop client.

Original prompt (core sections)

Fix the Codex Sol-V2/Luna-V1 subagent incompatibility on this machine using a
reversible V1 model-catalog override.

Do the work, do not merely describe it.

Requirements:

1. Inspect the current state first:
   - Run `codex --version`.
   - Run `codex debug models`.
   - Inspect the active global `~/.codex/config.toml`.
   - Determine the real absolute Codex home path.
   - Confirm whether Sol and Terra have `multi_agent_version = "v2"` while
     Luna has `"v1"`.
   - Preserve all unrelated configuration and user files.

2. Before editing anything, create a timestamped backup directory under
   `~/.codex/backups/` and copy the active config there.

3. Generate a new model catalog from the COMPLETE output of
   `codex debug models`, not a hand-written or partial catalog.

4. Validate the result:
   - Parse config.toml as TOML.
   - Parse the model catalog as JSON.
   - Run `codex features list`.
   - Run `codex debug models` and confirm the effective model versions.
   - Run `codex doctor --summary`.
   - Report exact files, backups, validation results, and warnings.

Safety notes

This prompt modifies the user's configuration and should not be run directly in a production environment. The original post later included an update saying that "CLI 0.147.0 has fixed" the issue; before using it, you must first check the current Codex version, create a backup, and validate the result. Do not modify the model catalog blindly.

Source and dates

Reddit, r/codex · Source date: Not disclosed · Edited: 2026-09-20

Read the original source
Variable checklist

Still to replace: 4

{{CLIENT_VERSION}}{{CONFIG_BACKUP}}{{MODEL_DIRECTORY}}{{VALIDATION_TASK}}

Related prompts

The Builder's Guide to GPT-5.6: Luna's Model Selection, Agent Orchestration, and CachingApply Occam’s Razor: Reducing Overengineering in Luna/Codex PromptsGPT-5.6 Prompting Guide: Luna's Work Contract and Model RoutingReddit Codex: Multi-Model Routing Configuration for Luna Subagents and Sol Review

Related reviews

Agents on Rails: 8 Models, 21 Atomic TasksThoughts after using GPT-5.6 Luna for 48 hoursGPT-5.6 Luna Is Really Underrated: Codex User Experience5.6 Luna Extra High is the work horse I needed

GPT-5.6 Luna

Use GPT-5.6 Luna in Tabbit

Run this guide in the environment listed above. Downloading does not transfer the template or establish model availability for your account.