Sign up
View stargazersSign up

Droid ACP Registry skills are missing from the `$` picker#27108

opened13d agobyEeddietex

What happened

When I select Claude models through Droid via the ACP Registry, T3 Code's $ picker says no skills were found. The Codex provider shows the shared skills. Droid advertises those skills as unprefixed ACP commands.

Diagnosis

The local server reported version 0.1.4-nightly.20261028.3841. In that version, normalizeAcpRegistryCommands classifies an ACP command as a skill only when its name starts with $; all other advertised commands are put in slashCommands. The web $ picker searches provider skills. The ACP provider docs say unprefixed commands appear under the provider section of /, while $-prefixed commands appear in the $ skill menu.

This explains the mismatch: Droid advertises these entries without the $ prefix, so T3 exposes them as provider slash commands rather than skills in the $ picker. This looks like an ACP/Droid classification integration gap, not missing skill files.

Source:

Steps to reproduce

  1. Add Droid through the ACP Registry on a local T3 Code server.
  2. Select a Claude model through Droid in a session.
  3. Open the $ picker.
  4. Observe that it reports no skills, even though Droid advertises unprefixed commands such as council and code-review. The Codex provider lists the shared skills.

Version

0.1.4-nightly.20261028.3841 (local server; serverVersion)

Environment

macOS 25.4.0 (arm64), Node v26.12.1; local T3 Code server; ACP Registry Droid. Client surface: unknown. Triage CLI: 0.1.5 (npx t3 triage).

Evidence

shell
1A cache snapshot read on 2026-10-29 at 19:25 UTC showed instance acpRegistry_droid, driver acpRegistry, 68 slashCommands, and 0 skills. A later cache refresh showed the provider disabled and both lists empty; no configuration or cache changes were made during triage.

#4109 reports an ACP provider cache with empty skills after a skills-reload crash; the cause differs. #5622 concerns native Claude plugin/user-level skill discovery; the provider path differs.

Fix applied or workaround

No configuration changes were made. The provider's advertised commands should be available under the Provider section of the / menu.

Filed by

GPT-6 Codex via T3 triage