Summary
When using CodexMonitor, the Codex CLI / app-server can read project-scoped skills from:
<workspace>/.agents/skills/*/SKILL.md
…but CodexMonitor does not reliably surface these skills in the UI (e.g. $ autocomplete, skills list), especially after switching workspaces.
Expected
- Project skills under
<workspace>/.agents/skills are always discovered and listed.
$ autocomplete includes these project skills.
- Switching workspaces refreshes the skills list and it matches the active workspace.
- When discovery fails, show actionable diagnostics (source path + reason).
Actual
- Project skills sometimes do not appear.
- The list may be stale after switching workspaces.
Repro
- In a workspace, create:
./.agents/skills/<skill-name>/SKILL.md.
- Open CodexMonitor and connect that workspace.
- In the composer, type
$ and check autocomplete.
- Switch between workspaces and observe skills list inconsistency.
Why this matters
Project-scoped skills are a core workflow for per-project automation. When CodexMonitor fails to discover them reliably, users cannot access the intended skills and it becomes hard to diagnose.
Suggested direction
- Ensure
skills/list includes the default project skills path <workspace>/.agents/skills.
- Add non-breaking diagnostics fields (e.g.
sourcePaths, sourceErrors) so the UI can surface why a source was skipped.
- Ensure workspace switching triggers a proper refresh.
Summary
When using CodexMonitor, the Codex CLI / app-server can read project-scoped skills from:
<workspace>/.agents/skills/*/SKILL.md…but CodexMonitor does not reliably surface these skills in the UI (e.g.
$autocomplete, skills list), especially after switching workspaces.Expected
<workspace>/.agents/skillsare always discovered and listed.$autocomplete includes these project skills.Actual
Repro
./.agents/skills/<skill-name>/SKILL.md.$and check autocomplete.Why this matters
Project-scoped skills are a core workflow for per-project automation. When CodexMonitor fails to discover them reliably, users cannot access the intended skills and it becomes hard to diagnose.
Suggested direction
skills/listincludes the default project skills path<workspace>/.agents/skills.sourcePaths,sourceErrors) so the UI can surface why a source was skipped.