[BUG] - #62606
Preflight Checklist
- [x] I have searched existing issues and this hasn't been reported yet
- [x] This is a single bug report (please file separate reports for different bugs)
- [x] I am using the latest version of Claude Code
What's Wrong?
Issue 1 (REC-15): fwd-core plugin skills do not materialize in the cloud runtime
What we configured. In the worker repo, .claude/settings.json declares the marketplace and enables the plugin:
json
{
"extraKnownMarketplaces": {
"fwd-marketplace": { "source": { "source": "github", "repo": "jwalls11/fwd-marketplace" } }
},
"enabledPlugins": { "fwd-core@fwd-marketplace": true }
}
The plugin validates locally (claude plugin validate exits 0) and its skills load and run correctly in the Cowork runtime.
Expected. In a cloud/web Claude Code session on that repo, the fwd-core skills (e.g. fwd-start-here, boil-the-ocean, fwd-file-updater) should be available/invokable, since the plugin is enabled.
Actual. The skills do not materialize. The plugin shows as enabled, but no fwd-core skill resolves or runs in the cloud session. Confirmed across two separate worker sessions, including a clean fresh session. This appears to match the behavior tracked internally as bug #32606.
Impact. Our operating method (how a worker writes to a Google file safely, how it orients on first run, our completionist mode) is delivered through these skills. Because they don't load in cloud, workers waste turns attempting skills that fail, and we've had to re-encode the critical procedures as Google Docs the worker reads at runtime ("skills-as-docs") — a workaround, not a fix. This does not scale to a fleet.
Ask. Make enabledPlugins in a repo's .claude/settings.json actually materialize the marketplace plugin's skills in the cloud/web runtime, at parity with Cowork. If there's a different supported mechanism for loading a private GitHub-hosted marketplace plugin's skills in cloud, please point us to it.
What Should Happen?
Issue 1 (REC-15): fwd-core plugin skills do not materialize in the cloud runtime
What we configured. In the worker repo, .claude/settings.json declares the marketplace and enables the plugin:
json
{
"extraKnownMarketplaces": {
"fwd-marketplace": { "source": { "source": "github", "repo": "jwalls11/fwd-marketplace" } }
},
"enabledPlugins": { "fwd-core@fwd-marketplace": true }
}
The plugin validates locally (claude plugin validate exits 0) and its skills load and run correctly in the Cowork runtime.
Expected. In a cloud/web Claude Code session on that repo, the fwd-core skills (e.g. fwd-start-here, boil-the-ocean, fwd-file-updater) should be available/invokable, since the plugin is enabled.
Actual. The skills do not materialize. The plugin shows as enabled, but no fwd-core skill resolves or runs in the cloud session. Confirmed across two separate worker sessions, including a clean fresh session. This appears to match the behavior tracked internally as bug #32606.
Impact. Our operating method (how a worker writes to a Google file safely, how it orients on first run, our completionist mode) is delivered through these skills. Because they don't load in cloud, workers waste turns attempting skills that fail, and we've had to re-encode the critical procedures as Google Docs the worker reads at runtime ("skills-as-docs") — a workaround, not a fix. This does not scale to a fleet.
Ask. Make enabledPlugins in a repo's .claude/settings.json actually materialize the marketplace plugin's skills in the cloud/web runtime, at parity with Cowork. If there's a different supported mechanism for loading a private GitHub-hosted marketplace plugin's skills in cloud, please point us to it.
Error Messages/Logs
Steps to Reproduce
Issue 1 (REC-15): fwd-core plugin skills do not materialize in the cloud runtime
What we configured. In the worker repo, .claude/settings.json declares the marketplace and enables the plugin:
json
{
"extraKnownMarketplaces": {
"fwd-marketplace": { "source": { "source": "github", "repo": "jwalls11/fwd-marketplace" } }
},
"enabledPlugins": { "fwd-core@fwd-marketplace": true }
}
The plugin validates locally (claude plugin validate exits 0) and its skills load and run correctly in the Cowork runtime.
Expected. In a cloud/web Claude Code session on that repo, the fwd-core skills (e.g. fwd-start-here, boil-the-ocean, fwd-file-updater) should be available/invokable, since the plugin is enabled.
Actual. The skills do not materialize. The plugin shows as enabled, but no fwd-core skill resolves or runs in the cloud session. Confirmed across two separate worker sessions, including a clean fresh session. This appears to match the behavior tracked internally as bug #32606.
Impact. Our operating method (how a worker writes to a Google file safely, how it orients on first run, our completionist mode) is delivered through these skills. Because they don't load in cloud, workers waste turns attempting skills that fail, and we've had to re-encode the critical procedures as Google Docs the worker reads at runtime ("skills-as-docs") — a workaround, not a fix. This does not scale to a fleet.
Ask. Make enabledPlugins in a repo's .claude/settings.json actually materialize the marketplace plugin's skills in the cloud/web runtime, at parity with Cowork. If there's a different supported mechanism for loading a private GitHub-hosted marketplace plugin's skills in cloud, please point us to it.
Claude Model
None
Is this a regression?
No, this never worked
Last Working Version
_No response_
Claude Code Version
2.1.216
Platform
Anthropic API
Operating System
Windows
Terminal/Shell
Other
Additional Information
Issue 1 (REC-15): fwd-core plugin skills do not materialize in the cloud runtime
What we configured. In the worker repo, .claude/settings.json declares the marketplace and enables the plugin:
json
{
"extraKnownMarketplaces": {
"fwd-marketplace": { "source": { "source": "github", "repo": "jwalls11/fwd-marketplace" } }
},
"enabledPlugins": { "fwd-core@fwd-marketplace": true }
}
The plugin validates locally (claude plugin validate exits 0) and its skills load and run correctly in the Cowork runtime.
Expected. In a cloud/web Claude Code session on that repo, the fwd-core skills (e.g. fwd-start-here, boil-the-ocean, fwd-file-updater) should be available/invokable, since the plugin is enabled.
Actual. The skills do not materialize. The plugin shows as enabled, but no fwd-core skill resolves or runs in the cloud session. Confirmed across two separate worker sessions, including a clean fresh session. This appears to match the behavior tracked internally as bug #32606.
Impact. Our operating method (how a worker writes to a Google file safely, how it orients on first run, our completionist mode) is delivered through these skills. Because they don't load in cloud, workers waste turns attempting skills that fail, and we've had to re-encode the critical procedures as Google Docs the worker reads at runtime ("skills-as-docs") — a workaround, not a fix. This does not scale to a fleet.
Ask. Make enabledPlugins in a repo's .claude/settings.json actually materialize the marketplace plugin's skills in the cloud/web runtime, at parity with Cowork. If there's a different supported mechanism for loading a private GitHub-hosted marketplace plugin's skills in cloud, please point us to it.