gitwtfhub

wtf is gpt-5-6-relay?

forward-future/gpt-5-6-relay — explained in plain English

Analysis updated 2026-05-18

156Audience · developerComplexity · 2/5LicenseSetup · easy

TL;DR

A Codex skill that routes one task through separate Sol, Terra, and Luna child threads, each matched to a model and reasoning effort suited to planning, implementation, or release.

Mindmap

mindmap
  root((repo))
    What it does
      Routes task by phase
      Uses child threads
      Tracks handoffs visibly
    Tech stack
      Codex
      Agent skill format
      Markdown
    Use cases
      Multi-model routing
      Visible thread history
      Final deployment report
    Audience
      Codex users
      Agent workflow builders

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

Why would anyone build with this?

REASON 1

Route a coding task through separate planning, implementation, review, and release phases automatically.

REASON 2

Keep a full visible history of which model handled which part of a task instead of one opaque conversation.

REASON 3

Assign cheaper, faster models to mechanical checks and reserve stronger models for ambiguous architecture work.

REASON 4

Get a final report listing exact thread IDs, models used, and deployment evidence for a completed task.

What's in the stack?

CodexMarkdownAgent Skill

How it stacks up

forward-future/gpt-5-6-relayalexeygrigorev/build-your-own-search-enginecaddyserver/replace-response
Stars156156156
LanguageJupyter NotebookGo
Last pushed2025-12-152025-06-18
MaintenanceQuietStale
Setup difficultyeasyeasymoderate
Complexity2/52/52/5
Audiencedeveloperdeveloperops devops

Figures from each repo's GitHub metadata at analysis time.

How do you spin it up?

Difficulty · easy Time to first run · 5min

Requires a Codex host that exposes thread-management tools with explicit model and reasoning-effort controls.

You can use, modify, and distribute this code freely, including commercially, as long as you keep the copyright notice.

Wtf does this do

GPT-5.6 Relay is a Codex skill that routes a single task through three separate model-specific child threads instead of handling everything in one conversation. Each phase of the work gets handed to whichever model and reasoning effort setting fits it best, while keeping the full thread history visible and passing concrete handoffs between phases rather than hiding the process. The default flow starts with a coordinator model called Sol, which handles planning, architecture decisions, and hard diagnosis at a high reasoning effort. Work then typically moves to a model called Terra for implementation, tests, and bounded debugging, then back to Sol for review, and finally to a third model called Luna for reconnaissance, mechanical checks, and release execution. The exact path is not fixed: small mechanical tasks might use only Luna, while genuinely ambiguous architecture work can stay with Sol for longer. Deployment is always treated as its own separate phase handled by Luna, following a project's own deployment rules. Each child thread in the relay is scoped to one role, one deliverable, and one checkable gate, and a thread that depends on another's output will not start until that output actually exists. If something needs correcting, the fix happens in the same child thread rather than spinning up a new one, and only one thread is allowed to write to a project checkout at any given time. At the end, the skill reports back with the actual thread IDs, which models and effort levels were used, what artifacts were produced, and what checks and deployment evidence back up the result. To use it, someone copies the skill folder into a project that supports Codex project skills and invokes it directly with a task description. It depends on the host application exposing tools for creating and reading threads and sending messages with specific model and effort settings, if those tools are not available, the skill reports the route it would have taken instead of pretending the routing happened. It is released under the MIT license.

Yoink these prompts

Prompt 1
Install this gpt-5-6-relay skill into my Codex project and invoke it with a sample task.
Prompt 2
Explain when a task would route through Sol only versus going all the way through Terra and Luna.
Prompt 3
What reasoning effort levels does each of Sol, Terra, and Luna support in this relay?
Prompt 4
Walk me through what the final report from a relay run includes.

Frequently asked questions

wtf is gpt-5-6-relay?

A Codex skill that routes one task through separate Sol, Terra, and Luna child threads, each matched to a model and reasoning effort suited to planning, implementation, or release.

What license does gpt-5-6-relay use?

You can use, modify, and distribute this code freely, including commercially, as long as you keep the copyright notice.

How hard is gpt-5-6-relay to set up?

Setup difficulty is rated easy, with roughly 5min to a first successful run.

Who is gpt-5-6-relay for?

Mainly developer.

View the repo → Decode another repo

This repo across BitVibe Labs

Don't trust strangers blindly. Verify against the repo.