Repository navigation
Support local Codex custom prompts and $skills in the composer #737
Description
Problem
T3 Code is Codex-first, but the composer currently misses two local Codex CLI affordances that are part of the normal prompt-entry workflow:
- local custom prompts from
~/.codex/prompts/*.md - local
$skillsinvocation with autocomplete and exact skill binding
Today, typing / only shows built-in commands, and typing $ does not surface local Codex skills.
Expected behavior
Match Codex CLI behavior closely for local prompts and local skills:
/should include local custom prompts as/prompts:<name>/codeshould be able to match/prompts:code-simplifier- selecting a custom prompt should insert
/prompts:<name>into the composer - sending
/prompts:<name> ...should expand the prompt locally before dispatch $should open a local Codex skills menu- selecting a skill should insert
$<name>into the composer - duplicate skill names should stay distinct in the menu using their path / scope
- selected skills should be sent to Codex as explicit structured skill items, not only raw text
Enter/Tabshould accept the highlighted menu item without sending the message
Why this should exist
These are not new product directions so much as Codex compatibility gaps in the primary Codex workflow.
Without them, T3 Code is missing a meaningful part of the day-to-day Codex CLI input model for users who rely on:
- reusable local prompts
- reusable local skills
- duplicate-skill disambiguation
Proposed delivery
To keep review scope small, I plan to split this into two focused PRs:
- local custom prompt discovery, autocomplete, and send-time expansion
- local
$skillsautocomplete and structured skill dispatch
Notes
- Scope is local Codex prompts and local Codex skills only
- No new provider work is involved
- I can add Codex CLI reference screenshots and before/after UI captures in follow-up comments if that is helpful for review
Reacted by Cameron Molen, Kainoa Newton, Paul Bouzian, Christopher Mayershofer, Brandon, Andrei, Marcos Vinícius Mafei Machado, Andy Yao, Rodrigo Rocha, Kayden Humphries and 5 more
Activity
notkainoa commentedon Mar 9, 2026
Also pulling skills from the global
.agents/skillsfolder would be nicepaul-bouzian commentedon Mar 9, 2026
definitly adding this to the PRs
jameswasher commentedon Mar 31, 2026
Adding a concrete repo-scoped repro for this.
I tested this with a custom Codex skill in a real project.
Paths tested:
.codex/skills/<skill-name>/SKILL.md.agents/skills/<skill-name>/SKILL.mdSkill metadata:
name:in frontmatter$skill syntaxWhat I observed in T3 Code:
/does not show the custom skill$does not show the custom skill.codex/skillsor.agents/skillsControl case:
SKILL.mdExpectation:
$<skill-name>should bind the local skillHappy to provide a minimal sample
SKILL.mdif useful, but this repro should already be enough to validate discovery/composer behavior.juliusmarminge commentedon Apr 11, 2026
skills ui added.
will think on prompts
respectTheCode commentedon Jun 10, 2026
Does this work with codex? I only see App and System skills. No User or Repo skills show up in the composer. Codex in T3 does find and use repo skills if asked though.