[DOCS] Per-feature platform availability is not discoverable in docs
Documentation Type
Unclear/confusing documentation
Documentation Location
_No response_
Section/Topic
Making clear which features, commands, tools, settings, etc, apply to which platform and product
Current Documentation
_No response_
What's Wrong or Missing?
Docs that don't say which surface a feature applies to are documentation you can't trust without running an experiment, and the Claude Code docs currently don't say. Each surface — CLI, desktop, web, GitHub Actions, SDK — exposes a materially different feature set, but per-feature pages rarely indicate which surface they describe.
Three from a single recent session on the web:
/loopacknowledges a scheduled job but the scheduling primitives aren't present in the web environment, so nothing ever fires./goalworks, but its page (/en/goal) lists "non-interactive mode, desktop app, and Remote Control" under non-interactive runs and never mentions the web at all./btw's page (/en/interactive-mode#side-questions-with-%2Fbtw) describes overlay-based, non-blocking, ephemeral behavior, but on the web the/btwprefix is stripped, the message enters conversation history as a normal turn, and it can't be sent during execution at all.
The cost is one round of trial-and-error per feature read, which has been a sustained friction over the month I've been on the web.
Minimum fix: a per-feature "Available on" badge near each command/feature heading (e.g. CLI · Desktop · Web · GitHub Action · SDK).
Fuller version: a platform-selector dropdown that filters the whole docs site (Stripe, Tailwind, and MDN compatibility tables do versions of this).
---
(Filed here because /feedback from Claude Code on the web returned a 403 on multiple retries, on both the "trusted" and "full" network policies. That itself is in scope of this issue.)
Suggested Improvement
Minimum fix: a per-feature "Available on" badge near each command/feature heading (e.g. CLI · Desktop · Web · GitHub Action · SDK).
Fuller version: a platform-selector dropdown that filters the whole docs site (Stripe, Tailwind, and MDN compatibility tables do versions of this).
Impact
Medium - Makes feature difficult to understand
Additional Context
_No response_
This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗