Skip to content

[Bug]: Repo-local Codex skills do not appear in T3 Code $ skill picker #3040

@laceyp99

Description

@laceyp99

Before submitting

  • I searched existing issues and did not find a duplicate.
  • I included enough detail to reproduce or investigate the problem.

Area

apps/server

Steps to reproduce

  1. Install/update Codex CLI and verify it is current:
codex --version
  1. Create a repository-local Codex skill under a project:
<repo>/
  .agents/
    skills/
      add-model-support/
        SKILL.md
        agents/
          openai.yaml  
  1. Use valid SKILL.md frontmatter:
---
name: add-model-support
description: Add support for a newly announced model from an existing provider.
---
  1. Verify Codex sees the repo-local skill when launched from the repo:
codex -C <repo-path> debug prompt-input "test" | rg "add-model-support"
  1. Open the same repository in T3 Code, type $ in the composer, and look for add-model-support.
  2. Fully quit T3 Code, delete the Codex provider cache, and reopen T3 Code:
Remove-Item "$env:USERPROFILE\.t3\caches\codex.json"
  1. Type $ again and observe that the skill is still missing.
  2. Confirm the rebuilt T3 Code cache does not include the repo-local skill:
rg "add-model-support" "$env:USERPROFILE\.t3\caches\codex.json"

Expected behavior

When opening the repo in T3 Code, repo-local Codex skills under .agents/skills should appear in the $ skill picker, the same way they do in Codex.

In this case, $add-model-support should be available when working in the LoopGPT repository.

Actual behavior

The skill does not appear in T3 Code’s $ picker.

T3 Code appears to load global/plugin Codex skills from its Codex cache, but not the repo-local .agents/skills entry.

Impact

Minor bug or occasional failure

Version or commit

T3 Code Alpha: v0.0.27.0

Environment

Windows 11 Core, 64-bit, Windows desktop app (T3 Code Alpha), npm installed codex-cli 0.139.0

Logs or stack traces

Screenshots, recordings, or supporting files

No response

Workaround

Just prompt the agent to find and read the skill instead of manually invoking it. Not ideal for consistency in performance though.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething is broken or behaving incorrectly.needs-triageIssue needs maintainer review and initial categorization.

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions