Skip to content

docs: add client support status page - #738

Open
udaykakade25 wants to merge 1 commit into
alpic-ai:mainfrom
udaykakade25:docs/client-support-page
Open

docs: add client support status page#738
udaykakade25 wants to merge 1 commit into
alpic-ai:mainfrom
udaykakade25:docs/client-support-page

Conversation

@udaykakade25

@udaykakade25 udaykakade25 commented May 6, 2026

Copy link
Copy Markdown
Contributor

Closes #681

Additions

  • Add fundamentals/client-support.mdx with a per-client feature matrix (ChatGPT, Claude, Goose, VSCode), client-specific notes, and DevTools runtime coverage.
  • Register the page in docs.json under Fundamentals.

Note: Used Claude to make this docs PR.

Result

Link: live video

Greptile Summary

This PR adds a new fundamentals/client-support.mdx page and registers it in the navigation. The page consolidates per-client feature availability, runtime mapping, connection requirements, and client-specific setup notes in one place.

  • New documentation page with a feature matrix (✅/⚠️/❌) covering ChatGPT, Claude, Goose, and VSCode across all Skybridge hooks, plus a DevTools runtime coverage table and client-specific notes sections.
  • docs.json updated to add fundamentals/client-support as the third entry under the Fundamentals nav group.

Confidence Score: 4/5

Safe to merge — purely additive documentation with no code changes.

The content is accurate and consistent with the existing mcp-apps.mdx reference page. Two small clarity gaps exist: the ⚠️ symbol in the feature matrix has no inline legend (its meaning is only revealed further down the page), and Postman/MCPJam appear in the Client Overview table but are silently dropped from the feature matrix. Neither affects correctness, but both could confuse readers consulting the table in isolation.

docs/fundamentals/client-support.mdx — feature matrix legend and Postman/MCPJam coverage.

Prompt To Fix All With AI
Fix the following 2 code review issues. Work through them one at a time, proposing concise fixes.

---

### Issue 1 of 2
docs/fundamentals/client-support.mdx:28-29
The feature matrix uses ⚠️ without defining what it means at the point of reference. A reader scanning the table won't know whether ⚠️ means "partial support", "experimental", or "polyfilled" unless they scroll down to the Client-Specific Notes — or happen to have read `mcp-apps.mdx` first. Adding a one-line legend beneath the table header keeps the page self-contained.

```suggestion
✅ Supported · ⚠️ Polyfilled (works with limitations) · ❌ Not supported

| Hook / Feature | ChatGPT | Claude | Goose | VSCode |
|----------------|:-------:|:------:|:-----:|:------:|
```

### Issue 2 of 2
docs/fundamentals/client-support.mdx:28-43
**Postman and MCPJam absent from feature matrix**

The Client Overview table (lines 11–18) lists six clients including Postman and MCPJam, but the Feature Availability matrix only covers four (ChatGPT, Claude, Goose, VSCode). Since both Postman and MCPJam are listed as full MCP Apps clients their feature columns would be identical to Goose/VSCode, but their omission leaves readers uncertain. Either add their columns to the matrix or add a brief note explaining they share the same feature set as other MCP Apps clients.

Reviews (1): Last reviewed commit: "docs: add client support status page" | Re-trigger Greptile

Greptile also left 2 inline comments on this PR.

Add fundamentals/client-support.mdx with a per-client feature matrix
(ChatGPT, Claude, Goose, VSCode), client-specific notes, and DevTools
runtime coverage. Register the page in docs.json under Fundamentals.
Comment on lines +28 to +29
| Hook / Feature | ChatGPT | Claude | Goose | VSCode |
|----------------|:-------:|:------:|:-----:|:------:|

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 The feature matrix uses ⚠️ without defining what it means at the point of reference. A reader scanning the table won't know whether ⚠️ means "partial support", "experimental", or "polyfilled" unless they scroll down to the Client-Specific Notes — or happen to have read mcp-apps.mdx first. Adding a one-line legend beneath the table header keeps the page self-contained.

Suggested change
| Hook / Feature | ChatGPT | Claude | Goose | VSCode |
|----------------|:-------:|:------:|:-----:|:------:|
✅ Supported · ⚠️ Polyfilled (works with limitations) · ❌ Not supported
| Hook / Feature | ChatGPT | Claude | Goose | VSCode |
|----------------|:-------:|:------:|:-----:|:------:|
Prompt To Fix With AI
This is a comment left during a code review.
Path: docs/fundamentals/client-support.mdx
Line: 28-29

Comment:
The feature matrix uses ⚠️ without defining what it means at the point of reference. A reader scanning the table won't know whether ⚠️ means "partial support", "experimental", or "polyfilled" unless they scroll down to the Client-Specific Notes — or happen to have read `mcp-apps.mdx` first. Adding a one-line legend beneath the table header keeps the page self-contained.

```suggestion
✅ Supported · ⚠️ Polyfilled (works with limitations) · ❌ Not supported

| Hook / Feature | ChatGPT | Claude | Goose | VSCode |
|----------------|:-------:|:------:|:-----:|:------:|
```

How can I resolve this? If you propose a fix, please make it concise.

Comment on lines +28 to +43
| Hook / Feature | ChatGPT | Claude | Goose | VSCode |
|----------------|:-------:|:------:|:-----:|:------:|
| [useToolInfo](/api-reference/use-tool-info) | ✅ | ✅ | ✅ | ✅ |
| [useCallTool](/api-reference/use-call-tool) | ✅ | ✅ | ✅ | ✅ |
| [useSendFollowUpMessage](/api-reference/use-send-follow-up-message) | ✅ | ✅ | ✅ | ✅ |
| [useOpenExternal](/api-reference/use-open-external) | ✅ | ✅ | ✅ | ✅ |
| [useLayout](/api-reference/use-layout) | ✅ | ✅ | ✅ | ✅ |
| [useUser](/api-reference/use-user) | ✅ | ✅ | ✅ | ✅ |
| [useDisplayMode](/api-reference/use-display-mode) | ✅ | ✅ | ✅ | ✅ |
| [useViewState](/api-reference/use-view-state) | ✅ | ⚠️ | ⚠️ | ⚠️ |
| [data-llm](/api-reference/data-llm) | ✅ | ⚠️ | ⚠️ | ⚠️ |
| [useRequestModal](/api-reference/use-request-modal) | ✅ | ⚠️ | ⚠️ | ⚠️ |
| [useFiles](/api-reference/use-files) | ✅ | ❌ | ❌ | ❌ |
| [useSetOpenInAppUrl](/api-reference/use-set-open-in-app-url) | ✅ | ❌ | ❌ | ❌ |
| [useAppsSdkContext](/api-reference/use-apps-sdk-context) | ✅ | ❌ | ❌ | ❌ |
| [useMcpAppContext](/api-reference/use-mcp-app-context) | ❌ | ✅ | ✅ | ✅ |

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Postman and MCPJam absent from feature matrix

The Client Overview table (lines 11–18) lists six clients including Postman and MCPJam, but the Feature Availability matrix only covers four (ChatGPT, Claude, Goose, VSCode). Since both Postman and MCPJam are listed as full MCP Apps clients their feature columns would be identical to Goose/VSCode, but their omission leaves readers uncertain. Either add their columns to the matrix or add a brief note explaining they share the same feature set as other MCP Apps clients.

Prompt To Fix With AI
This is a comment left during a code review.
Path: docs/fundamentals/client-support.mdx
Line: 28-43

Comment:
**Postman and MCPJam absent from feature matrix**

The Client Overview table (lines 11–18) lists six clients including Postman and MCPJam, but the Feature Availability matrix only covers four (ChatGPT, Claude, Goose, VSCode). Since both Postman and MCPJam are listed as full MCP Apps clients their feature columns would be identical to Goose/VSCode, but their omission leaves readers uncertain. Either add their columns to the matrix or add a brief note explaining they share the same feature set as other MCP Apps clients.

How can I resolve this? If you propose a fix, please make it concise.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Documentation — Multi-clients support status page

1 participant