fix(codex): discover project skills from workspace by t3-code[bot] · Pull Request #5335 · pingdotgg/t3code

t3-code · 2026-08-04T13:55:22Z

summary

discover codex skills against the active project or thread worktree
feed workspace-scoped skills into $ autocomplete
keep the global fallback while excluding repo skills discovered from the server launch directory
resolve workspace paths server-side instead of accepting arbitrary client paths

reproduction

launch t3 code outside the target repository
open a project containing .agents/skills/<name>/SKILL.md
select codex and type $
the project skill is now listed

tests

pnpm --filter t3 typecheck
pnpm --filter @t3tools/contracts typecheck
pnpm --filter @t3tools/client-runtime typecheck
pnpm --filter @t3tools/web typecheck
pnpm --dir apps/server exec vp test run src/server.test.ts -t "server.listProviderSkills"
pnpm --dir apps/server exec vp test run src/provider/Layers/ProviderRegistry.test.ts -t "cwd-scoped skill discovery"
pnpm lint
pnpm fmt:check

Note

Medium Risk
New WS RPC and Codex subprocess probes on composer interaction add latency and failure modes; cwd is server-resolved from project/thread shells rather than client paths, which limits path injection risk.

Overview
Fixes Codex $ autocomplete when T3 Code is launched outside the target repo by loading skills for the active project or thread worktree instead of only from the server’s launch directory.

Adds server.listProviderSkills (read scope): the server maps projectId / optional threadId to workspaceRoot or worktreePath, then calls provider listSkills(cwd). Codex runs a scoped skills/list probe against that cwd (10s timeout, fallback to cached global skills on failure). Full provider refresh still drops repo-scoped skills from the global snapshot so launch-dir repo skills don’t pollute the default list.

The web composer fetches skills via useProviderSkills when the skill menu is open, with short-lived caching for smoother UX; other providers without listSkills keep using snapshot skills.

^{Reviewed by Cursor Bugbot for commit 6df2036. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Discover project skills from workspace via `server.listProviderSkills` RPC

Adds a new server.listProviderSkills websocket RPC that resolves skills scoped to the active workspace root or worktree path, with auth requiring OrchestrationReadScope.
Implements listSkills(cwd) on the Codex provider driver in CodexDriver.ts, which spawns a short-lived app-server probe with a 10s timeout and falls back to snapshot skills on failure.
Refactors CodexProvider.ts to extract openCodexAppServerProbe as a reusable utility; snapshot skills now exclude repo-scoped entries.
The web ChatComposer fetches live provider skills via the new RPC when the skill trigger is active, caching results by environment/instance/project/thread and falling back to snapshot skills filtered to non-repo scope.
Risk: the 10s child-process timeout per listSkills call may add latency if the Codex app-server is slow to start.

^{Macroscope summarized 6df2036.}

macroscopeapp

One finding on error-log hygiene in the new Codex skill-discovery fallback. Everything else (subpath namespace imports, Effect.fn service methods, whole-channel Effect.catch, contract schemas, added focused tests) matches the conventions.

^{Posted via Macroscope — Effect Service Conventions}

macroscopeapp · 2026-08-04T13:57:37Z

+ Effect.catch((error) =>
+ Effect.logWarning("Codex workspace skill discovery failed; using global skills.", {
+ cwd,
+ error: String(error),


String(error) puts arbitrary error text into the log payload — the failure channel here includes CodexAppServerSpawnError, whose message carries the resolved binary/app-server command and underlying spawn output. Consider logging a normalized tag instead (the pattern used by the other provider layers, e.g. errorTag/causeErrorTag from @t3tools/shared/observability), keeping the real error only as cause.
- error: String(error),+ errorTag: errorTag(error),
Requires adding import { errorTag } from "@t3tools/shared/observability";.
^{Posted via Macroscope — Effect Service Conventions}

cursor

Cursor Bugbot has reviewed your changes using high effort and found 2 potential issues.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

Want fixes drafted automatically? Bugbot Autofix can create code changes for findings. A team admin can enable Autofix in the Cursor dashboard.

^{Reviewed by Cursor Bugbot for commit 6df2036. Configure here.}

cursor · 2026-08-04T14:05:02Z

 const isComposerMenuLoading =
- composerTriggerKind === "path" && pathTriggerQuery.length > 0 && workspaceEntries.isPending;
+ (composerTriggerKind === "path" && pathTriggerQuery.length > 0 && workspaceEntries.isPending) ||
+ (composerTriggerKind === "skill" && providerSkills.isPending && composerMenuItems.length === 0);


Incomplete skill menu looks final
Medium Severity
The skill autocomplete menu ($) incorrectly shows only global skills as complete while project/repo-specific skills are still loading. This happens because the loading indicator is suppressed when fallback global skills are present, masking the pending state of the skill query.
^{Reviewed by Cursor Bugbot for commit 6df2036. Configure here.}

cursor · 2026-08-04T14:05:02Z

- skills: parseCodexSkillsListResponse(skillsResponse, input.cwd),
+ skills: parseCodexSkillsListResponse(skillsResponse, input.cwd).filter(
+ (skill) => skill.scope !== "repo",
+ ),


Repo skill chips lost in timeline
Medium Severity
Repo-scoped skills are stripped from the Codex provider snapshot, but the message timeline still renders skill chips only from that snapshot. $repo tokens in history therefore stop turning into skill chips because timeline rendering was not switched to workspace-scoped skill discovery.
Additional Locations (1)
apps/web/src/components/ChatView.tsx#L5829-L5830
^{Reviewed by Cursor Bugbot for commit 6df2036. Configure here.}

macroscopeapp · 2026-08-04T14:06:26Z

Approvability

Verdict: Needs human review

This PR introduces a new feature for workspace-scoped skill discovery with new RPC endpoints and frontend integration. Additionally, there are unresolved review comments identifying potential bugs in loading state handling and timeline skill chip rendering that should be addressed.

^{You can customize Macroscope's approvability policy. Learn more.}

archiekd · 2026-08-04T17:36:17Z

Does this work for claude project level skills as well?

felix-exon · 2026-08-19T09:05:36Z

waiting for this as well :P

t3-code · 2026-08-04T13:55:22Z

summary

discover codex skills against the active project or thread worktree
feed workspace-scoped skills into $ autocomplete
keep the global fallback while excluding repo skills discovered from the server launch directory
resolve workspace paths server-side instead of accepting arbitrary client paths

reproduction

launch t3 code outside the target repository
open a project containing .agents/skills/<name>/SKILL.md
select codex and type $
the project skill is now listed

tests

pnpm --filter t3 typecheck
pnpm --filter @t3tools/contracts typecheck
pnpm --filter @t3tools/client-runtime typecheck
pnpm --filter @t3tools/web typecheck
pnpm --dir apps/server exec vp test run src/server.test.ts -t "server.listProviderSkills"
pnpm --dir apps/server exec vp test run src/provider/Layers/ProviderRegistry.test.ts -t "cwd-scoped skill discovery"
pnpm lint
pnpm fmt:check

Note

Medium Risk
New WS RPC and Codex subprocess probes on composer interaction add latency and failure modes; cwd is server-resolved from project/thread shells rather than client paths, which limits path injection risk.

Overview
Fixes Codex $ autocomplete when T3 Code is launched outside the target repo by loading skills for the active project or thread worktree instead of only from the server’s launch directory.

Adds server.listProviderSkills (read scope): the server maps projectId / optional threadId to workspaceRoot or worktreePath, then calls provider listSkills(cwd). Codex runs a scoped skills/list probe against that cwd (10s timeout, fallback to cached global skills on failure). Full provider refresh still drops repo-scoped skills from the global snapshot so launch-dir repo skills don’t pollute the default list.

The web composer fetches skills via useProviderSkills when the skill menu is open, with short-lived caching for smoother UX; other providers without listSkills keep using snapshot skills.

^{Reviewed by Cursor Bugbot for commit 6df2036. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Discover project skills from workspace via `server.listProviderSkills` RPC

Adds a new server.listProviderSkills websocket RPC that resolves skills scoped to the active workspace root or worktree path, with auth requiring OrchestrationReadScope.
Implements listSkills(cwd) on the Codex provider driver in CodexDriver.ts, which spawns a short-lived app-server probe with a 10s timeout and falls back to snapshot skills on failure.
Refactors CodexProvider.ts to extract openCodexAppServerProbe as a reusable utility; snapshot skills now exclude repo-scoped entries.
The web ChatComposer fetches live provider skills via the new RPC when the skill trigger is active, caching results by environment/instance/project/thread and falling back to snapshot skills filtered to non-repo scope.
Risk: the 10s child-process timeout per listSkills call may add latency if the Codex app-server is slow to start.

^{Macroscope summarized 6df2036.}

macroscopeapp

One finding on error-log hygiene in the new Codex skill-discovery fallback. Everything else (subpath namespace imports, Effect.fn service methods, whole-channel Effect.catch, contract schemas, added focused tests) matches the conventions.

^{Posted via Macroscope — Effect Service Conventions}

macroscopeapp · 2026-08-04T13:57:37Z

+ Effect.catch((error) =>
+ Effect.logWarning("Codex workspace skill discovery failed; using global skills.", {
+ cwd,
+ error: String(error),


String(error) puts arbitrary error text into the log payload — the failure channel here includes CodexAppServerSpawnError, whose message carries the resolved binary/app-server command and underlying spawn output. Consider logging a normalized tag instead (the pattern used by the other provider layers, e.g. errorTag/causeErrorTag from @t3tools/shared/observability), keeping the real error only as cause.
- error: String(error),+ errorTag: errorTag(error),
Requires adding import { errorTag } from "@t3tools/shared/observability";.
^{Posted via Macroscope — Effect Service Conventions}

cursor

Cursor Bugbot has reviewed your changes using high effort and found 2 potential issues.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

Want fixes drafted automatically? Bugbot Autofix can create code changes for findings. A team admin can enable Autofix in the Cursor dashboard.

^{Reviewed by Cursor Bugbot for commit 6df2036. Configure here.}

cursor · 2026-08-04T14:05:02Z

 const isComposerMenuLoading =
- composerTriggerKind === "path" && pathTriggerQuery.length > 0 && workspaceEntries.isPending;
+ (composerTriggerKind === "path" && pathTriggerQuery.length > 0 && workspaceEntries.isPending) ||
+ (composerTriggerKind === "skill" && providerSkills.isPending && composerMenuItems.length === 0);


Incomplete skill menu looks final
Medium Severity
The skill autocomplete menu ($) incorrectly shows only global skills as complete while project/repo-specific skills are still loading. This happens because the loading indicator is suppressed when fallback global skills are present, masking the pending state of the skill query.
^{Reviewed by Cursor Bugbot for commit 6df2036. Configure here.}

cursor · 2026-08-04T14:05:02Z

- skills: parseCodexSkillsListResponse(skillsResponse, input.cwd),
+ skills: parseCodexSkillsListResponse(skillsResponse, input.cwd).filter(
+ (skill) => skill.scope !== "repo",
+ ),


Repo skill chips lost in timeline
Medium Severity
Repo-scoped skills are stripped from the Codex provider snapshot, but the message timeline still renders skill chips only from that snapshot. $repo tokens in history therefore stop turning into skill chips because timeline rendering was not switched to workspace-scoped skill discovery.
Additional Locations (1)
apps/web/src/components/ChatView.tsx#L5829-L5830
^{Reviewed by Cursor Bugbot for commit 6df2036. Configure here.}

macroscopeapp · 2026-08-04T14:06:26Z

Approvability

Verdict: Needs human review

This PR introduces a new feature for workspace-scoped skill discovery with new RPC endpoints and frontend integration. Additionally, there are unresolved review comments identifying potential bugs in loading state handling and timeline skill chip rendering that should be addressed.

^{You can customize Macroscope's approvability policy. Learn more.}

archiekd · 2026-08-04T17:36:17Z

Does this work for claude project level skills as well?

felix-exon · 2026-08-19T09:05:36Z

waiting for this as well :P

t3-code · 2026-08-04T13:55:22Z

summary

discover codex skills against the active project or thread worktree
feed workspace-scoped skills into $ autocomplete
keep the global fallback while excluding repo skills discovered from the server launch directory
resolve workspace paths server-side instead of accepting arbitrary client paths

reproduction

launch t3 code outside the target repository
open a project containing .agents/skills/<name>/SKILL.md
select codex and type $
the project skill is now listed

tests

pnpm --filter t3 typecheck
pnpm --filter @t3tools/contracts typecheck
pnpm --filter @t3tools/client-runtime typecheck
pnpm --filter @t3tools/web typecheck
pnpm --dir apps/server exec vp test run src/server.test.ts -t "server.listProviderSkills"
pnpm --dir apps/server exec vp test run src/provider/Layers/ProviderRegistry.test.ts -t "cwd-scoped skill discovery"
pnpm lint
pnpm fmt:check

Note

Medium Risk
New WS RPC and Codex subprocess probes on composer interaction add latency and failure modes; cwd is server-resolved from project/thread shells rather than client paths, which limits path injection risk.

Overview
Fixes Codex $ autocomplete when T3 Code is launched outside the target repo by loading skills for the active project or thread worktree instead of only from the server’s launch directory.

Adds server.listProviderSkills (read scope): the server maps projectId / optional threadId to workspaceRoot or worktreePath, then calls provider listSkills(cwd). Codex runs a scoped skills/list probe against that cwd (10s timeout, fallback to cached global skills on failure). Full provider refresh still drops repo-scoped skills from the global snapshot so launch-dir repo skills don’t pollute the default list.

The web composer fetches skills via useProviderSkills when the skill menu is open, with short-lived caching for smoother UX; other providers without listSkills keep using snapshot skills.

^{Reviewed by Cursor Bugbot for commit 6df2036. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Discover project skills from workspace via `server.listProviderSkills` RPC

Adds a new server.listProviderSkills websocket RPC that resolves skills scoped to the active workspace root or worktree path, with auth requiring OrchestrationReadScope.
Implements listSkills(cwd) on the Codex provider driver in CodexDriver.ts, which spawns a short-lived app-server probe with a 10s timeout and falls back to snapshot skills on failure.
Refactors CodexProvider.ts to extract openCodexAppServerProbe as a reusable utility; snapshot skills now exclude repo-scoped entries.
The web ChatComposer fetches live provider skills via the new RPC when the skill trigger is active, caching results by environment/instance/project/thread and falling back to snapshot skills filtered to non-repo scope.
Risk: the 10s child-process timeout per listSkills call may add latency if the Codex app-server is slow to start.

^{Macroscope summarized 6df2036.}

macroscopeapp

One finding on error-log hygiene in the new Codex skill-discovery fallback. Everything else (subpath namespace imports, Effect.fn service methods, whole-channel Effect.catch, contract schemas, added focused tests) matches the conventions.

^{Posted via Macroscope — Effect Service Conventions}

macroscopeapp · 2026-08-04T13:57:37Z

+ Effect.catch((error) =>
+ Effect.logWarning("Codex workspace skill discovery failed; using global skills.", {
+ cwd,
+ error: String(error),


String(error) puts arbitrary error text into the log payload — the failure channel here includes CodexAppServerSpawnError, whose message carries the resolved binary/app-server command and underlying spawn output. Consider logging a normalized tag instead (the pattern used by the other provider layers, e.g. errorTag/causeErrorTag from @t3tools/shared/observability), keeping the real error only as cause.
- error: String(error),+ errorTag: errorTag(error),
Requires adding import { errorTag } from "@t3tools/shared/observability";.
^{Posted via Macroscope — Effect Service Conventions}

cursor

Cursor Bugbot has reviewed your changes using high effort and found 2 potential issues.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

Want fixes drafted automatically? Bugbot Autofix can create code changes for findings. A team admin can enable Autofix in the Cursor dashboard.

^{Reviewed by Cursor Bugbot for commit 6df2036. Configure here.}

cursor · 2026-08-04T14:05:02Z

 const isComposerMenuLoading =
- composerTriggerKind === "path" && pathTriggerQuery.length > 0 && workspaceEntries.isPending;
+ (composerTriggerKind === "path" && pathTriggerQuery.length > 0 && workspaceEntries.isPending) ||
+ (composerTriggerKind === "skill" && providerSkills.isPending && composerMenuItems.length === 0);


Incomplete skill menu looks final
Medium Severity
The skill autocomplete menu ($) incorrectly shows only global skills as complete while project/repo-specific skills are still loading. This happens because the loading indicator is suppressed when fallback global skills are present, masking the pending state of the skill query.
^{Reviewed by Cursor Bugbot for commit 6df2036. Configure here.}

cursor · 2026-08-04T14:05:02Z

- skills: parseCodexSkillsListResponse(skillsResponse, input.cwd),
+ skills: parseCodexSkillsListResponse(skillsResponse, input.cwd).filter(
+ (skill) => skill.scope !== "repo",
+ ),


Repo skill chips lost in timeline
Medium Severity
Repo-scoped skills are stripped from the Codex provider snapshot, but the message timeline still renders skill chips only from that snapshot. $repo tokens in history therefore stop turning into skill chips because timeline rendering was not switched to workspace-scoped skill discovery.
Additional Locations (1)
apps/web/src/components/ChatView.tsx#L5829-L5830
^{Reviewed by Cursor Bugbot for commit 6df2036. Configure here.}

macroscopeapp · 2026-08-04T14:06:26Z

Approvability

Verdict: Needs human review

This PR introduces a new feature for workspace-scoped skill discovery with new RPC endpoints and frontend integration. Additionally, there are unresolved review comments identifying potential bugs in loading state handling and timeline skill chip rendering that should be addressed.

^{You can customize Macroscope's approvability policy. Learn more.}

archiekd · 2026-08-04T17:36:17Z

Does this work for claude project level skills as well?

felix-exon · 2026-08-19T09:05:36Z

waiting for this as well :P

t3-code · 2026-08-04T13:55:22Z

summary

discover codex skills against the active project or thread worktree
feed workspace-scoped skills into $ autocomplete
keep the global fallback while excluding repo skills discovered from the server launch directory
resolve workspace paths server-side instead of accepting arbitrary client paths

reproduction

launch t3 code outside the target repository
open a project containing .agents/skills/<name>/SKILL.md
select codex and type $
the project skill is now listed

tests

pnpm --filter t3 typecheck
pnpm --filter @t3tools/contracts typecheck
pnpm --filter @t3tools/client-runtime typecheck
pnpm --filter @t3tools/web typecheck
pnpm --dir apps/server exec vp test run src/server.test.ts -t "server.listProviderSkills"
pnpm --dir apps/server exec vp test run src/provider/Layers/ProviderRegistry.test.ts -t "cwd-scoped skill discovery"
pnpm lint
pnpm fmt:check

Note

Medium Risk
New WS RPC and Codex subprocess probes on composer interaction add latency and failure modes; cwd is server-resolved from project/thread shells rather than client paths, which limits path injection risk.

Overview
Fixes Codex $ autocomplete when T3 Code is launched outside the target repo by loading skills for the active project or thread worktree instead of only from the server’s launch directory.

Adds server.listProviderSkills (read scope): the server maps projectId / optional threadId to workspaceRoot or worktreePath, then calls provider listSkills(cwd). Codex runs a scoped skills/list probe against that cwd (10s timeout, fallback to cached global skills on failure). Full provider refresh still drops repo-scoped skills from the global snapshot so launch-dir repo skills don’t pollute the default list.

The web composer fetches skills via useProviderSkills when the skill menu is open, with short-lived caching for smoother UX; other providers without listSkills keep using snapshot skills.

^{Reviewed by Cursor Bugbot for commit 6df2036. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Discover project skills from workspace via `server.listProviderSkills` RPC

Adds a new server.listProviderSkills websocket RPC that resolves skills scoped to the active workspace root or worktree path, with auth requiring OrchestrationReadScope.
Implements listSkills(cwd) on the Codex provider driver in CodexDriver.ts, which spawns a short-lived app-server probe with a 10s timeout and falls back to snapshot skills on failure.
Refactors CodexProvider.ts to extract openCodexAppServerProbe as a reusable utility; snapshot skills now exclude repo-scoped entries.
The web ChatComposer fetches live provider skills via the new RPC when the skill trigger is active, caching results by environment/instance/project/thread and falling back to snapshot skills filtered to non-repo scope.
Risk: the 10s child-process timeout per listSkills call may add latency if the Codex app-server is slow to start.

^{Macroscope summarized 6df2036.}

macroscopeapp

One finding on error-log hygiene in the new Codex skill-discovery fallback. Everything else (subpath namespace imports, Effect.fn service methods, whole-channel Effect.catch, contract schemas, added focused tests) matches the conventions.

^{Posted via Macroscope — Effect Service Conventions}

macroscopeapp · 2026-08-04T13:57:37Z

+ Effect.catch((error) =>
+ Effect.logWarning("Codex workspace skill discovery failed; using global skills.", {
+ cwd,
+ error: String(error),


String(error) puts arbitrary error text into the log payload — the failure channel here includes CodexAppServerSpawnError, whose message carries the resolved binary/app-server command and underlying spawn output. Consider logging a normalized tag instead (the pattern used by the other provider layers, e.g. errorTag/causeErrorTag from @t3tools/shared/observability), keeping the real error only as cause.
- error: String(error),+ errorTag: errorTag(error),
Requires adding import { errorTag } from "@t3tools/shared/observability";.
^{Posted via Macroscope — Effect Service Conventions}

cursor

Cursor Bugbot has reviewed your changes using high effort and found 2 potential issues.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

Want fixes drafted automatically? Bugbot Autofix can create code changes for findings. A team admin can enable Autofix in the Cursor dashboard.

^{Reviewed by Cursor Bugbot for commit 6df2036. Configure here.}

cursor · 2026-08-04T14:05:02Z

 const isComposerMenuLoading =
- composerTriggerKind === "path" && pathTriggerQuery.length > 0 && workspaceEntries.isPending;
+ (composerTriggerKind === "path" && pathTriggerQuery.length > 0 && workspaceEntries.isPending) ||
+ (composerTriggerKind === "skill" && providerSkills.isPending && composerMenuItems.length === 0);


Incomplete skill menu looks final
Medium Severity
The skill autocomplete menu ($) incorrectly shows only global skills as complete while project/repo-specific skills are still loading. This happens because the loading indicator is suppressed when fallback global skills are present, masking the pending state of the skill query.
^{Reviewed by Cursor Bugbot for commit 6df2036. Configure here.}

cursor · 2026-08-04T14:05:02Z

- skills: parseCodexSkillsListResponse(skillsResponse, input.cwd),
+ skills: parseCodexSkillsListResponse(skillsResponse, input.cwd).filter(
+ (skill) => skill.scope !== "repo",
+ ),


Repo skill chips lost in timeline
Medium Severity
Repo-scoped skills are stripped from the Codex provider snapshot, but the message timeline still renders skill chips only from that snapshot. $repo tokens in history therefore stop turning into skill chips because timeline rendering was not switched to workspace-scoped skill discovery.
Additional Locations (1)
apps/web/src/components/ChatView.tsx#L5829-L5830
^{Reviewed by Cursor Bugbot for commit 6df2036. Configure here.}

macroscopeapp · 2026-08-04T14:06:26Z

Approvability

Verdict: Needs human review

This PR introduces a new feature for workspace-scoped skill discovery with new RPC endpoints and frontend integration. Additionally, there are unresolved review comments identifying potential bugs in loading state handling and timeline skill chip rendering that should be addressed.

^{You can customize Macroscope's approvability policy. Learn more.}

archiekd · 2026-08-04T17:36:17Z

Does this work for claude project level skills as well?

felix-exon · 2026-08-19T09:05:36Z

waiting for this as well :P

t3-code · 2026-08-04T13:55:22Z

summary

discover codex skills against the active project or thread worktree
feed workspace-scoped skills into $ autocomplete
keep the global fallback while excluding repo skills discovered from the server launch directory
resolve workspace paths server-side instead of accepting arbitrary client paths

reproduction

launch t3 code outside the target repository
open a project containing .agents/skills/<name>/SKILL.md
select codex and type $
the project skill is now listed

tests

pnpm --filter t3 typecheck
pnpm --filter @t3tools/contracts typecheck
pnpm --filter @t3tools/client-runtime typecheck
pnpm --filter @t3tools/web typecheck
pnpm --dir apps/server exec vp test run src/server.test.ts -t "server.listProviderSkills"
pnpm --dir apps/server exec vp test run src/provider/Layers/ProviderRegistry.test.ts -t "cwd-scoped skill discovery"
pnpm lint
pnpm fmt:check

Note

Medium Risk
New WS RPC and Codex subprocess probes on composer interaction add latency and failure modes; cwd is server-resolved from project/thread shells rather than client paths, which limits path injection risk.

Overview
Fixes Codex $ autocomplete when T3 Code is launched outside the target repo by loading skills for the active project or thread worktree instead of only from the server’s launch directory.

Adds server.listProviderSkills (read scope): the server maps projectId / optional threadId to workspaceRoot or worktreePath, then calls provider listSkills(cwd). Codex runs a scoped skills/list probe against that cwd (10s timeout, fallback to cached global skills on failure). Full provider refresh still drops repo-scoped skills from the global snapshot so launch-dir repo skills don’t pollute the default list.

The web composer fetches skills via useProviderSkills when the skill menu is open, with short-lived caching for smoother UX; other providers without listSkills keep using snapshot skills.

^{Reviewed by Cursor Bugbot for commit 6df2036. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Discover project skills from workspace via `server.listProviderSkills` RPC

Adds a new server.listProviderSkills websocket RPC that resolves skills scoped to the active workspace root or worktree path, with auth requiring OrchestrationReadScope.
Implements listSkills(cwd) on the Codex provider driver in CodexDriver.ts, which spawns a short-lived app-server probe with a 10s timeout and falls back to snapshot skills on failure.
Refactors CodexProvider.ts to extract openCodexAppServerProbe as a reusable utility; snapshot skills now exclude repo-scoped entries.
The web ChatComposer fetches live provider skills via the new RPC when the skill trigger is active, caching results by environment/instance/project/thread and falling back to snapshot skills filtered to non-repo scope.
Risk: the 10s child-process timeout per listSkills call may add latency if the Codex app-server is slow to start.

^{Macroscope summarized 6df2036.}

macroscopeapp

One finding on error-log hygiene in the new Codex skill-discovery fallback. Everything else (subpath namespace imports, Effect.fn service methods, whole-channel Effect.catch, contract schemas, added focused tests) matches the conventions.

^{Posted via Macroscope — Effect Service Conventions}

macroscopeapp · 2026-08-04T13:57:37Z

+ Effect.catch((error) =>
+ Effect.logWarning("Codex workspace skill discovery failed; using global skills.", {
+ cwd,
+ error: String(error),


String(error) puts arbitrary error text into the log payload — the failure channel here includes CodexAppServerSpawnError, whose message carries the resolved binary/app-server command and underlying spawn output. Consider logging a normalized tag instead (the pattern used by the other provider layers, e.g. errorTag/causeErrorTag from @t3tools/shared/observability), keeping the real error only as cause.
- error: String(error),+ errorTag: errorTag(error),
Requires adding import { errorTag } from "@t3tools/shared/observability";.
^{Posted via Macroscope — Effect Service Conventions}

cursor

Cursor Bugbot has reviewed your changes using high effort and found 2 potential issues.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

Want fixes drafted automatically? Bugbot Autofix can create code changes for findings. A team admin can enable Autofix in the Cursor dashboard.

^{Reviewed by Cursor Bugbot for commit 6df2036. Configure here.}

cursor · 2026-08-04T14:05:02Z

 const isComposerMenuLoading =
- composerTriggerKind === "path" && pathTriggerQuery.length > 0 && workspaceEntries.isPending;
+ (composerTriggerKind === "path" && pathTriggerQuery.length > 0 && workspaceEntries.isPending) ||
+ (composerTriggerKind === "skill" && providerSkills.isPending && composerMenuItems.length === 0);


Incomplete skill menu looks final
Medium Severity
The skill autocomplete menu ($) incorrectly shows only global skills as complete while project/repo-specific skills are still loading. This happens because the loading indicator is suppressed when fallback global skills are present, masking the pending state of the skill query.
^{Reviewed by Cursor Bugbot for commit 6df2036. Configure here.}

cursor · 2026-08-04T14:05:02Z

- skills: parseCodexSkillsListResponse(skillsResponse, input.cwd),
+ skills: parseCodexSkillsListResponse(skillsResponse, input.cwd).filter(
+ (skill) => skill.scope !== "repo",
+ ),


Repo skill chips lost in timeline
Medium Severity
Repo-scoped skills are stripped from the Codex provider snapshot, but the message timeline still renders skill chips only from that snapshot. $repo tokens in history therefore stop turning into skill chips because timeline rendering was not switched to workspace-scoped skill discovery.
Additional Locations (1)
apps/web/src/components/ChatView.tsx#L5829-L5830
^{Reviewed by Cursor Bugbot for commit 6df2036. Configure here.}

macroscopeapp · 2026-08-04T14:06:26Z

Approvability

Verdict: Needs human review

This PR introduces a new feature for workspace-scoped skill discovery with new RPC endpoints and frontend integration. Additionally, there are unresolved review comments identifying potential bugs in loading state handling and timeline skill chip rendering that should be addressed.

^{You can customize Macroscope's approvability policy. Learn more.}

archiekd · 2026-08-04T17:36:17Z

Does this work for claude project level skills as well?

felix-exon · 2026-08-19T09:05:36Z

waiting for this as well :P

t3-code · 2026-08-04T13:55:22Z

summary

discover codex skills against the active project or thread worktree
feed workspace-scoped skills into $ autocomplete
keep the global fallback while excluding repo skills discovered from the server launch directory
resolve workspace paths server-side instead of accepting arbitrary client paths

reproduction

launch t3 code outside the target repository
open a project containing .agents/skills/<name>/SKILL.md
select codex and type $
the project skill is now listed

tests

pnpm --filter t3 typecheck
pnpm --filter @t3tools/contracts typecheck
pnpm --filter @t3tools/client-runtime typecheck
pnpm --filter @t3tools/web typecheck
pnpm --dir apps/server exec vp test run src/server.test.ts -t "server.listProviderSkills"
pnpm --dir apps/server exec vp test run src/provider/Layers/ProviderRegistry.test.ts -t "cwd-scoped skill discovery"
pnpm lint
pnpm fmt:check

Note

Medium Risk
New WS RPC and Codex subprocess probes on composer interaction add latency and failure modes; cwd is server-resolved from project/thread shells rather than client paths, which limits path injection risk.

Overview
Fixes Codex $ autocomplete when T3 Code is launched outside the target repo by loading skills for the active project or thread worktree instead of only from the server’s launch directory.

Adds server.listProviderSkills (read scope): the server maps projectId / optional threadId to workspaceRoot or worktreePath, then calls provider listSkills(cwd). Codex runs a scoped skills/list probe against that cwd (10s timeout, fallback to cached global skills on failure). Full provider refresh still drops repo-scoped skills from the global snapshot so launch-dir repo skills don’t pollute the default list.

The web composer fetches skills via useProviderSkills when the skill menu is open, with short-lived caching for smoother UX; other providers without listSkills keep using snapshot skills.

^{Reviewed by Cursor Bugbot for commit 6df2036. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Discover project skills from workspace via `server.listProviderSkills` RPC

Adds a new server.listProviderSkills websocket RPC that resolves skills scoped to the active workspace root or worktree path, with auth requiring OrchestrationReadScope.
Implements listSkills(cwd) on the Codex provider driver in CodexDriver.ts, which spawns a short-lived app-server probe with a 10s timeout and falls back to snapshot skills on failure.
Refactors CodexProvider.ts to extract openCodexAppServerProbe as a reusable utility; snapshot skills now exclude repo-scoped entries.
The web ChatComposer fetches live provider skills via the new RPC when the skill trigger is active, caching results by environment/instance/project/thread and falling back to snapshot skills filtered to non-repo scope.
Risk: the 10s child-process timeout per listSkills call may add latency if the Codex app-server is slow to start.

^{Macroscope summarized 6df2036.}

macroscopeapp

One finding on error-log hygiene in the new Codex skill-discovery fallback. Everything else (subpath namespace imports, Effect.fn service methods, whole-channel Effect.catch, contract schemas, added focused tests) matches the conventions.

^{Posted via Macroscope — Effect Service Conventions}

macroscopeapp · 2026-08-04T13:57:37Z

+ Effect.catch((error) =>
+ Effect.logWarning("Codex workspace skill discovery failed; using global skills.", {
+ cwd,
+ error: String(error),


String(error) puts arbitrary error text into the log payload — the failure channel here includes CodexAppServerSpawnError, whose message carries the resolved binary/app-server command and underlying spawn output. Consider logging a normalized tag instead (the pattern used by the other provider layers, e.g. errorTag/causeErrorTag from @t3tools/shared/observability), keeping the real error only as cause.
- error: String(error),+ errorTag: errorTag(error),
Requires adding import { errorTag } from "@t3tools/shared/observability";.
^{Posted via Macroscope — Effect Service Conventions}

cursor

Cursor Bugbot has reviewed your changes using high effort and found 2 potential issues.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

Want fixes drafted automatically? Bugbot Autofix can create code changes for findings. A team admin can enable Autofix in the Cursor dashboard.

^{Reviewed by Cursor Bugbot for commit 6df2036. Configure here.}

cursor · 2026-08-04T14:05:02Z

 const isComposerMenuLoading =
- composerTriggerKind === "path" && pathTriggerQuery.length > 0 && workspaceEntries.isPending;
+ (composerTriggerKind === "path" && pathTriggerQuery.length > 0 && workspaceEntries.isPending) ||
+ (composerTriggerKind === "skill" && providerSkills.isPending && composerMenuItems.length === 0);


Incomplete skill menu looks final
Medium Severity
The skill autocomplete menu ($) incorrectly shows only global skills as complete while project/repo-specific skills are still loading. This happens because the loading indicator is suppressed when fallback global skills are present, masking the pending state of the skill query.
^{Reviewed by Cursor Bugbot for commit 6df2036. Configure here.}

cursor · 2026-08-04T14:05:02Z

- skills: parseCodexSkillsListResponse(skillsResponse, input.cwd),
+ skills: parseCodexSkillsListResponse(skillsResponse, input.cwd).filter(
+ (skill) => skill.scope !== "repo",
+ ),


Repo skill chips lost in timeline
Medium Severity
Repo-scoped skills are stripped from the Codex provider snapshot, but the message timeline still renders skill chips only from that snapshot. $repo tokens in history therefore stop turning into skill chips because timeline rendering was not switched to workspace-scoped skill discovery.
Additional Locations (1)
apps/web/src/components/ChatView.tsx#L5829-L5830
^{Reviewed by Cursor Bugbot for commit 6df2036. Configure here.}

macroscopeapp · 2026-08-04T14:06:26Z

Approvability

Verdict: Needs human review

This PR introduces a new feature for workspace-scoped skill discovery with new RPC endpoints and frontend integration. Additionally, there are unresolved review comments identifying potential bugs in loading state handling and timeline skill chip rendering that should be addressed.

^{You can customize Macroscope's approvability policy. Learn more.}

archiekd · 2026-08-04T17:36:17Z

Does this work for claude project level skills as well?

felix-exon · 2026-08-19T09:05:36Z

waiting for this as well :P

t3-code · 2026-08-04T13:55:22Z

summary

discover codex skills against the active project or thread worktree
feed workspace-scoped skills into $ autocomplete
keep the global fallback while excluding repo skills discovered from the server launch directory
resolve workspace paths server-side instead of accepting arbitrary client paths

reproduction

launch t3 code outside the target repository
open a project containing .agents/skills/<name>/SKILL.md
select codex and type $
the project skill is now listed

tests

pnpm --filter t3 typecheck
pnpm --filter @t3tools/contracts typecheck
pnpm --filter @t3tools/client-runtime typecheck
pnpm --filter @t3tools/web typecheck
pnpm --dir apps/server exec vp test run src/server.test.ts -t "server.listProviderSkills"
pnpm --dir apps/server exec vp test run src/provider/Layers/ProviderRegistry.test.ts -t "cwd-scoped skill discovery"
pnpm lint
pnpm fmt:check

Note

Medium Risk
New WS RPC and Codex subprocess probes on composer interaction add latency and failure modes; cwd is server-resolved from project/thread shells rather than client paths, which limits path injection risk.

Overview
Fixes Codex $ autocomplete when T3 Code is launched outside the target repo by loading skills for the active project or thread worktree instead of only from the server’s launch directory.

Adds server.listProviderSkills (read scope): the server maps projectId / optional threadId to workspaceRoot or worktreePath, then calls provider listSkills(cwd). Codex runs a scoped skills/list probe against that cwd (10s timeout, fallback to cached global skills on failure). Full provider refresh still drops repo-scoped skills from the global snapshot so launch-dir repo skills don’t pollute the default list.

The web composer fetches skills via useProviderSkills when the skill menu is open, with short-lived caching for smoother UX; other providers without listSkills keep using snapshot skills.

^{Reviewed by Cursor Bugbot for commit 6df2036. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Discover project skills from workspace via `server.listProviderSkills` RPC

Adds a new server.listProviderSkills websocket RPC that resolves skills scoped to the active workspace root or worktree path, with auth requiring OrchestrationReadScope.
Implements listSkills(cwd) on the Codex provider driver in CodexDriver.ts, which spawns a short-lived app-server probe with a 10s timeout and falls back to snapshot skills on failure.
Refactors CodexProvider.ts to extract openCodexAppServerProbe as a reusable utility; snapshot skills now exclude repo-scoped entries.
The web ChatComposer fetches live provider skills via the new RPC when the skill trigger is active, caching results by environment/instance/project/thread and falling back to snapshot skills filtered to non-repo scope.
Risk: the 10s child-process timeout per listSkills call may add latency if the Codex app-server is slow to start.

^{Macroscope summarized 6df2036.}

macroscopeapp

One finding on error-log hygiene in the new Codex skill-discovery fallback. Everything else (subpath namespace imports, Effect.fn service methods, whole-channel Effect.catch, contract schemas, added focused tests) matches the conventions.

^{Posted via Macroscope — Effect Service Conventions}

macroscopeapp · 2026-08-04T13:57:37Z

+ Effect.catch((error) =>
+ Effect.logWarning("Codex workspace skill discovery failed; using global skills.", {
+ cwd,
+ error: String(error),


String(error) puts arbitrary error text into the log payload — the failure channel here includes CodexAppServerSpawnError, whose message carries the resolved binary/app-server command and underlying spawn output. Consider logging a normalized tag instead (the pattern used by the other provider layers, e.g. errorTag/causeErrorTag from @t3tools/shared/observability), keeping the real error only as cause.
- error: String(error),+ errorTag: errorTag(error),
Requires adding import { errorTag } from "@t3tools/shared/observability";.
^{Posted via Macroscope — Effect Service Conventions}

cursor

Cursor Bugbot has reviewed your changes using high effort and found 2 potential issues.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

Want fixes drafted automatically? Bugbot Autofix can create code changes for findings. A team admin can enable Autofix in the Cursor dashboard.

^{Reviewed by Cursor Bugbot for commit 6df2036. Configure here.}

cursor · 2026-08-04T14:05:02Z

 const isComposerMenuLoading =
- composerTriggerKind === "path" && pathTriggerQuery.length > 0 && workspaceEntries.isPending;
+ (composerTriggerKind === "path" && pathTriggerQuery.length > 0 && workspaceEntries.isPending) ||
+ (composerTriggerKind === "skill" && providerSkills.isPending && composerMenuItems.length === 0);


Incomplete skill menu looks final
Medium Severity
The skill autocomplete menu ($) incorrectly shows only global skills as complete while project/repo-specific skills are still loading. This happens because the loading indicator is suppressed when fallback global skills are present, masking the pending state of the skill query.
^{Reviewed by Cursor Bugbot for commit 6df2036. Configure here.}

cursor · 2026-08-04T14:05:02Z

- skills: parseCodexSkillsListResponse(skillsResponse, input.cwd),
+ skills: parseCodexSkillsListResponse(skillsResponse, input.cwd).filter(
+ (skill) => skill.scope !== "repo",
+ ),


Repo skill chips lost in timeline
Medium Severity
Repo-scoped skills are stripped from the Codex provider snapshot, but the message timeline still renders skill chips only from that snapshot. $repo tokens in history therefore stop turning into skill chips because timeline rendering was not switched to workspace-scoped skill discovery.
Additional Locations (1)
apps/web/src/components/ChatView.tsx#L5829-L5830
^{Reviewed by Cursor Bugbot for commit 6df2036. Configure here.}

macroscopeapp · 2026-08-04T14:06:26Z

Approvability

Verdict: Needs human review

This PR introduces a new feature for workspace-scoped skill discovery with new RPC endpoints and frontend integration. Additionally, there are unresolved review comments identifying potential bugs in loading state handling and timeline skill chip rendering that should be addressed.

^{You can customize Macroscope's approvability policy. Learn more.}

archiekd · 2026-08-04T17:36:17Z

Does this work for claude project level skills as well?

felix-exon · 2026-08-19T09:05:36Z

waiting for this as well :P

t3-code · 2026-08-04T13:55:22Z

summary

discover codex skills against the active project or thread worktree
feed workspace-scoped skills into $ autocomplete
keep the global fallback while excluding repo skills discovered from the server launch directory
resolve workspace paths server-side instead of accepting arbitrary client paths

reproduction

launch t3 code outside the target repository
open a project containing .agents/skills/<name>/SKILL.md
select codex and type $
the project skill is now listed

tests

pnpm --filter t3 typecheck
pnpm --filter @t3tools/contracts typecheck
pnpm --filter @t3tools/client-runtime typecheck
pnpm --filter @t3tools/web typecheck
pnpm --dir apps/server exec vp test run src/server.test.ts -t "server.listProviderSkills"
pnpm --dir apps/server exec vp test run src/provider/Layers/ProviderRegistry.test.ts -t "cwd-scoped skill discovery"
pnpm lint
pnpm fmt:check

Note

Medium Risk
New WS RPC and Codex subprocess probes on composer interaction add latency and failure modes; cwd is server-resolved from project/thread shells rather than client paths, which limits path injection risk.

Overview
Fixes Codex $ autocomplete when T3 Code is launched outside the target repo by loading skills for the active project or thread worktree instead of only from the server’s launch directory.

Adds server.listProviderSkills (read scope): the server maps projectId / optional threadId to workspaceRoot or worktreePath, then calls provider listSkills(cwd). Codex runs a scoped skills/list probe against that cwd (10s timeout, fallback to cached global skills on failure). Full provider refresh still drops repo-scoped skills from the global snapshot so launch-dir repo skills don’t pollute the default list.

The web composer fetches skills via useProviderSkills when the skill menu is open, with short-lived caching for smoother UX; other providers without listSkills keep using snapshot skills.

^{Reviewed by Cursor Bugbot for commit 6df2036. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Discover project skills from workspace via `server.listProviderSkills` RPC

Adds a new server.listProviderSkills websocket RPC that resolves skills scoped to the active workspace root or worktree path, with auth requiring OrchestrationReadScope.
Implements listSkills(cwd) on the Codex provider driver in CodexDriver.ts, which spawns a short-lived app-server probe with a 10s timeout and falls back to snapshot skills on failure.
Refactors CodexProvider.ts to extract openCodexAppServerProbe as a reusable utility; snapshot skills now exclude repo-scoped entries.
The web ChatComposer fetches live provider skills via the new RPC when the skill trigger is active, caching results by environment/instance/project/thread and falling back to snapshot skills filtered to non-repo scope.
Risk: the 10s child-process timeout per listSkills call may add latency if the Codex app-server is slow to start.

^{Macroscope summarized 6df2036.}

macroscopeapp

One finding on error-log hygiene in the new Codex skill-discovery fallback. Everything else (subpath namespace imports, Effect.fn service methods, whole-channel Effect.catch, contract schemas, added focused tests) matches the conventions.

^{Posted via Macroscope — Effect Service Conventions}

macroscopeapp · 2026-08-04T13:57:37Z

+ Effect.catch((error) =>
+ Effect.logWarning("Codex workspace skill discovery failed; using global skills.", {
+ cwd,
+ error: String(error),


String(error) puts arbitrary error text into the log payload — the failure channel here includes CodexAppServerSpawnError, whose message carries the resolved binary/app-server command and underlying spawn output. Consider logging a normalized tag instead (the pattern used by the other provider layers, e.g. errorTag/causeErrorTag from @t3tools/shared/observability), keeping the real error only as cause.
- error: String(error),+ errorTag: errorTag(error),
Requires adding import { errorTag } from "@t3tools/shared/observability";.
^{Posted via Macroscope — Effect Service Conventions}

cursor

Cursor Bugbot has reviewed your changes using high effort and found 2 potential issues.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

Want fixes drafted automatically? Bugbot Autofix can create code changes for findings. A team admin can enable Autofix in the Cursor dashboard.

^{Reviewed by Cursor Bugbot for commit 6df2036. Configure here.}

cursor · 2026-08-04T14:05:02Z

 const isComposerMenuLoading =
- composerTriggerKind === "path" && pathTriggerQuery.length > 0 && workspaceEntries.isPending;
+ (composerTriggerKind === "path" && pathTriggerQuery.length > 0 && workspaceEntries.isPending) ||
+ (composerTriggerKind === "skill" && providerSkills.isPending && composerMenuItems.length === 0);


Incomplete skill menu looks final
Medium Severity
The skill autocomplete menu ($) incorrectly shows only global skills as complete while project/repo-specific skills are still loading. This happens because the loading indicator is suppressed when fallback global skills are present, masking the pending state of the skill query.
^{Reviewed by Cursor Bugbot for commit 6df2036. Configure here.}

cursor · 2026-08-04T14:05:02Z

- skills: parseCodexSkillsListResponse(skillsResponse, input.cwd),
+ skills: parseCodexSkillsListResponse(skillsResponse, input.cwd).filter(
+ (skill) => skill.scope !== "repo",
+ ),


Repo skill chips lost in timeline
Medium Severity
Repo-scoped skills are stripped from the Codex provider snapshot, but the message timeline still renders skill chips only from that snapshot. $repo tokens in history therefore stop turning into skill chips because timeline rendering was not switched to workspace-scoped skill discovery.
Additional Locations (1)
apps/web/src/components/ChatView.tsx#L5829-L5830
^{Reviewed by Cursor Bugbot for commit 6df2036. Configure here.}

macroscopeapp · 2026-08-04T14:06:26Z

Approvability

Verdict: Needs human review

This PR introduces a new feature for workspace-scoped skill discovery with new RPC endpoints and frontend integration. Additionally, there are unresolved review comments identifying potential bugs in loading state handling and timeline skill chip rendering that should be addressed.

^{You can customize Macroscope's approvability policy. Learn more.}

archiekd · 2026-08-04T17:36:17Z

Does this work for claude project level skills as well?

felix-exon · 2026-08-19T09:05:36Z

waiting for this as well :P

fix: discover project skills from workspace
6df2036

github-actionsBot added vouch:trusted PR author is trusted by repo permissions or the VOUCHED list. size:L 100-499 changed lines (additions + deletions). labels Aug 4, 2026

macroscopeappBot reviewed Aug 4, 2026
View reviewed changes

cursorBot reviewed Aug 4, 2026
View reviewed changes

nemesiscodex mentioned this pull request Aug 5, 2026
[Bug]: Cursor/OpenCode skill discovery returns zero skills despite skills existing on disk (Claude/Codex discover them fine) #2736
Open
2 tasks

kamafozilov mentioned this pull request Aug 11, 2026
[Bug]: Explicit Codex $skill invocation does not attach user-invoked skills #6095
Open
2 tasks

jln13x mentioned this pull request Aug 17, 2026
feat(codex): add project skills and queue-first steering jln13x/t3code#28
Merged

This was referenced Aug 23, 2026
Fix/project scoped provider skills #6661
Closed
fix: the $ skill picker now lists the active project's skills #6450
Closed
fix(codex): show project-local skills in composer #7717
Closed

fix: discover project skills from workspace
6df2036

github-actionsBot added vouch:trusted PR author is trusted by repo permissions or the VOUCHED list. size:L 100-499 changed lines (additions + deletions). labels Aug 4, 2026

macroscopeappBot reviewed Aug 4, 2026
View reviewed changes

cursorBot reviewed Aug 4, 2026
View reviewed changes

nemesiscodex mentioned this pull request Aug 5, 2026
[Bug]: Cursor/OpenCode skill discovery returns zero skills despite skills existing on disk (Claude/Codex discover them fine) #2736
Open
2 tasks

kamafozilov mentioned this pull request Aug 11, 2026
[Bug]: Explicit Codex $skill invocation does not attach user-invoked skills #6095
Open
2 tasks

jln13x mentioned this pull request Aug 17, 2026
feat(codex): add project skills and queue-first steering jln13x/t3code#28
Merged

This was referenced Aug 23, 2026
Fix/project scoped provider skills #6661
Closed
fix: the $ skill picker now lists the active project's skills #6450
Closed
fix(codex): show project-local skills in composer #7717
Closed

fix: discover project skills from workspace
6df2036

github-actionsBot added vouch:trusted PR author is trusted by repo permissions or the VOUCHED list. size:L 100-499 changed lines (additions + deletions). labels Aug 4, 2026

macroscopeappBot reviewed Aug 4, 2026
View reviewed changes

cursorBot reviewed Aug 4, 2026
View reviewed changes

nemesiscodex mentioned this pull request Aug 5, 2026
[Bug]: Cursor/OpenCode skill discovery returns zero skills despite skills existing on disk (Claude/Codex discover them fine) #2736
Open
2 tasks

kamafozilov mentioned this pull request Aug 11, 2026
[Bug]: Explicit Codex $skill invocation does not attach user-invoked skills #6095
Open
2 tasks

jln13x mentioned this pull request Aug 17, 2026
feat(codex): add project skills and queue-first steering jln13x/t3code#28
Merged

This was referenced Aug 23, 2026
Fix/project scoped provider skills #6661
Closed
fix: the $ skill picker now lists the active project's skills #6450
Closed
fix(codex): show project-local skills in composer #7717
Closed

fix: discover project skills from workspace
6df2036

github-actionsBot added vouch:trusted PR author is trusted by repo permissions or the VOUCHED list. size:L 100-499 changed lines (additions + deletions). labels Aug 4, 2026

macroscopeappBot reviewed Aug 4, 2026
View reviewed changes

cursorBot reviewed Aug 4, 2026
View reviewed changes

nemesiscodex mentioned this pull request Aug 5, 2026
[Bug]: Cursor/OpenCode skill discovery returns zero skills despite skills existing on disk (Claude/Codex discover them fine) #2736
Open
2 tasks

kamafozilov mentioned this pull request Aug 11, 2026
[Bug]: Explicit Codex $skill invocation does not attach user-invoked skills #6095
Open
2 tasks

jln13x mentioned this pull request Aug 17, 2026
feat(codex): add project skills and queue-first steering jln13x/t3code#28
Merged

This was referenced Aug 23, 2026
Fix/project scoped provider skills #6661
Closed
fix: the $ skill picker now lists the active project's skills #6450
Closed
fix(codex): show project-local skills in composer #7717
Closed

fix: discover project skills from workspace
6df2036

github-actionsBot added vouch:trusted PR author is trusted by repo permissions or the VOUCHED list. size:L 100-499 changed lines (additions + deletions). labels Aug 4, 2026

macroscopeappBot reviewed Aug 4, 2026
View reviewed changes

cursorBot reviewed Aug 4, 2026
View reviewed changes

nemesiscodex mentioned this pull request Aug 5, 2026
[Bug]: Cursor/OpenCode skill discovery returns zero skills despite skills existing on disk (Claude/Codex discover them fine) #2736
Open
2 tasks

kamafozilov mentioned this pull request Aug 11, 2026
[Bug]: Explicit Codex $skill invocation does not attach user-invoked skills #6095
Open
2 tasks

jln13x mentioned this pull request Aug 17, 2026
feat(codex): add project skills and queue-first steering jln13x/t3code#28
Merged

This was referenced Aug 23, 2026
Fix/project scoped provider skills #6661
Closed
fix: the $ skill picker now lists the active project's skills #6450
Closed
fix(codex): show project-local skills in composer #7717
Closed

fix: discover project skills from workspace
6df2036

github-actionsBot added vouch:trusted PR author is trusted by repo permissions or the VOUCHED list. size:L 100-499 changed lines (additions + deletions). labels Aug 4, 2026

macroscopeappBot reviewed Aug 4, 2026
View reviewed changes

cursorBot reviewed Aug 4, 2026
View reviewed changes

nemesiscodex mentioned this pull request Aug 5, 2026
[Bug]: Cursor/OpenCode skill discovery returns zero skills despite skills existing on disk (Claude/Codex discover them fine) #2736
Open
2 tasks

kamafozilov mentioned this pull request Aug 11, 2026
[Bug]: Explicit Codex $skill invocation does not attach user-invoked skills #6095
Open
2 tasks

jln13x mentioned this pull request Aug 17, 2026
feat(codex): add project skills and queue-first steering jln13x/t3code#28
Merged

This was referenced Aug 23, 2026
Fix/project scoped provider skills #6661
Closed
fix: the $ skill picker now lists the active project's skills #6450
Closed
fix(codex): show project-local skills in composer #7717
Closed

fix: discover project skills from workspace
6df2036

github-actionsBot added vouch:trusted PR author is trusted by repo permissions or the VOUCHED list. size:L 100-499 changed lines (additions + deletions). labels Aug 4, 2026

macroscopeappBot reviewed Aug 4, 2026
View reviewed changes

cursorBot reviewed Aug 4, 2026
View reviewed changes

nemesiscodex mentioned this pull request Aug 5, 2026
[Bug]: Cursor/OpenCode skill discovery returns zero skills despite skills existing on disk (Claude/Codex discover them fine) #2736
Open
2 tasks

kamafozilov mentioned this pull request Aug 11, 2026
[Bug]: Explicit Codex $skill invocation does not attach user-invoked skills #6095
Open
2 tasks

jln13x mentioned this pull request Aug 17, 2026
feat(codex): add project skills and queue-first steering jln13x/t3code#28
Merged

This was referenced Aug 23, 2026
Fix/project scoped provider skills #6661
Closed
fix: the $ skill picker now lists the active project's skills #6450
Closed
fix(codex): show project-local skills in composer #7717
Closed

fix: discover project skills from workspace
6df2036

github-actionsBot added vouch:trusted PR author is trusted by repo permissions or the VOUCHED list. size:L 100-499 changed lines (additions + deletions). labels Aug 4, 2026

macroscopeappBot reviewed Aug 4, 2026
View reviewed changes

cursorBot reviewed Aug 4, 2026
View reviewed changes

nemesiscodex mentioned this pull request Aug 5, 2026
[Bug]: Cursor/OpenCode skill discovery returns zero skills despite skills existing on disk (Claude/Codex discover them fine) #2736
Open
2 tasks

kamafozilov mentioned this pull request Aug 11, 2026
[Bug]: Explicit Codex $skill invocation does not attach user-invoked skills #6095
Open
2 tasks

jln13x mentioned this pull request Aug 17, 2026
feat(codex): add project skills and queue-first steering jln13x/t3code#28
Merged

This was referenced Aug 23, 2026
Fix/project scoped provider skills #6661
Closed
fix: the $ skill picker now lists the active project's skills #6450
Closed
fix(codex): show project-local skills in composer #7717
Closed

Uh oh!

Conversation

t3-codeBot commented Aug 4, 2026• edited by macroscopeapp BotLoading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

summary

reproduction

tests

Discover project skills from workspace via server.listProviderSkills RPC

Uh oh!

macroscopeappBot left a comment

Choose a reason for hiding this comment

Uh oh!

macroscopeappBotAug 4, 2026

Choose a reason for hiding this comment

Uh oh!

cursorBot left a comment

Choose a reason for hiding this comment

Uh oh!

cursorBotAug 4, 2026

Choose a reason for hiding this comment

Incomplete skill menu looks final

Uh oh!

cursorBotAug 4, 2026

Choose a reason for hiding this comment

Repo skill chips lost in timeline

Uh oh!

macroscopeappBot commented Aug 4, 2026

Approvability

Uh oh!

archiekd commented Aug 4, 2026

Uh oh!

felix-exon commented Aug 19, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Uh oh!

Conversation

t3-codeBot commented Aug 4, 2026• edited by macroscopeapp BotLoading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

summary

reproduction

tests

Discover project skills from workspace via server.listProviderSkills RPC

Uh oh!

macroscopeappBot left a comment

Choose a reason for hiding this comment

Uh oh!

macroscopeappBotAug 4, 2026

Choose a reason for hiding this comment

Uh oh!

cursorBot left a comment

Choose a reason for hiding this comment

Uh oh!

cursorBotAug 4, 2026

Choose a reason for hiding this comment

Incomplete skill menu looks final

Uh oh!

cursorBotAug 4, 2026

Choose a reason for hiding this comment

Repo skill chips lost in timeline

Uh oh!

macroscopeappBot commented Aug 4, 2026

Approvability

Uh oh!

archiekd commented Aug 4, 2026

Uh oh!

felix-exon commented Aug 19, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

t3-codeBot commented Aug 4, 2026•
edited by macroscopeapp Bot
Loading

Discover project skills from workspace via `server.listProviderSkills` RPC

t3-codeBot commented Aug 4, 2026•
edited by macroscopeapp Bot
Loading

Discover project skills from workspace via `server.listProviderSkills` RPC

t3-codeBot commented Aug 4, 2026•
edited by macroscopeapp Bot
Loading

Discover project skills from workspace via `server.listProviderSkills` RPC

t3-codeBot commented Aug 4, 2026•
edited by macroscopeapp Bot
Loading

Discover project skills from workspace via `server.listProviderSkills` RPC