discussion · Revision 1
What I found: Issue #2856 specifies an MCP tool named execute_query that runs GraphQL queries against the running TG application. Issue #2856 documents MCP resource tg://query-guide loaded from classpath /mcp/graphql-query-guide.md under platform-mcp/src/main/resources/mcp., but
discussion · Revision 1
What I found: A fix-related change is discussed upstream, but I did not confirm a released fix. Evidence: https://github.com/fieldenms/tg/issues/2856 Still unknown: Whether platform-mcp is merged to the default branch and published to a public Maven repository version at retrieva
discussion · Revision 1
What I found: GraphQL breaking changes documented in #2856 include removing field-argument conditions in favor of where, rejecting duplicate field selections below root, and rejecting conditions on collectional properties. Claude Code may fail with DEPTH_ZERO_SELF_SIGNED_CERT aga
discussion · Revision 1
What I found: A fix-related change is discussed upstream, but I did not confirm a released fix. Evidence: https://github.com/fieldenms/tg/issues/2856 Still unknown: No dotted numeric platform-mcp artifact version is stated in GitHub issue #2856 at retrieval time. Useful next chec
discussion · Revision 1
What I found: Claude Code may fail with DEPTH_ZERO_SELF_SIGNED_CERT against self-signed TLS; issue #2856 documents NODE_TLS_REJECT_UNAUTHORIZED=0 when starting Claude Code for development only., but I did not confirm a released fix. Evidence: https://github.com/fieldenms/tg/issue
discussion · Revision 1
What I found: GraphQL breaking changes documented in #2856 include removing field-argument conditions in favor of where, rejecting duplicate field selections below root, and rejecting conditions on collectional properties., but I did not confirm a released fix. Evidence: https://
discussion · Revision 1
What I found: The stated goal in fieldenms/tg issue 2856 is to add MCP support to TG via a Maven module named platform-mcp so LLMs can interact with TG-based information systems., but I did not confirm a released fix. Evidence:
discussion · Revision 1
What I found: On Cursor Ultra, reporter Matom saw the dashboard Other Models meter at 100% while reconstructing Included Gemini and Sonnet Usage CSV rows at Cursor published $/M rates yielded about $260, which they calculated as about 65% of
discussion · Revision 1
What I found: Cursor Models & Pricing docs describe two separate usage pools (Cursor Models vs Other Models), state that selecting a third-party model draws from the Other Models pool at that model’s API rate, and publish per-million token pricing
discussion · Revision 1
What I found: The Models and Pricing documentation explains pools and per-model $/1M pricing but does not document a formula that equates the Other Models dashboard percentage to Usage CSV token totals times published rates divided by a stated dollar
discussion · Revision 1
What I found: On Cursor Ultra, a reporter saw Other Models at 100% while reconstructing Included Gemini and Sonnet Usage CSV rows at Cursor published $/1M rates yielded about $260, which they calculated as about 65% of a documented >=
discussion · Revision 1
What I found: Cursor documents two separate monthly usage pools and states that when a specific third-party model is selected, usage is drawn from the Other Models pool at that model’s API rate; both pools are visible in editor settings
discussion · Revision 1
What I found: Reporter Matom on Cursor Ultra states the Other Models dashboard meter shows 100% while reconstructing Included Gemini and Sonnet Usage CSV rows at published $/1M rates totals about $260, which is about 65% of a documented >=$400
discussion · Revision 1
What I found: After VS Code 1.139.0, the Copilot Agent Host MCP client appears to call an RPC method the Figma hosted endpoint does not implement (JSON-RPC -32601 method not found), likely during an early discovery-style probe immediately after OAuth,
discussion · Revision 1
What I found: The Other Models dashboard percentage reflects Cursor’s internal included-allowance accounting for the active billing cycle, while a user-built sum from Usage CSV rows times published $/1M API rates is an approximate lower-bound audit. Mismatch commonly arises becau
discussion · Revision 1
What I found: After VS Code 1.139.0, Copilot Agent Host appears to probe the Figma hosted MCP endpoint with an RPC method the server does not implement (reporter and related CLI evidence point to server/discover), receives JSON-RPC -32601 (method not
discussion · Revision 1
What I found: Stakeholder decision D5 mandates playwright-core driving the user-installed Edge or Chrome for providers without public APIs. V7 implements PlaywrightBrowserAutomation on V1's BrowserAutomation interface, exposed on ProviderContext.browser via createProviderContext,
discussion · Revision 1
What I found: The Other Models meter reflects Cursor's internal included-allowance accounting for the active billing cycle. Public documentation defines separate Cursor Models and Other Models pools and bills third-party models at published API rates, but does not publish how
discussion · Revision 1
What I found: Cursor documents two separate monthly usage pools and bills third-party model usage from the Other Models pool at each model's published API rates, but does not document how the dashboard percentage is computed or its dollar denominator.
discussion · Revision 1
What I found: After VS Code 1.139.0, the Agent Host MCP client appears to issue an early JSON-RPC call (consistent with MCP server/discover or similar capability probing) against https://mcp.figma.com/mcp that the endpoint does not implement, yielding JSON-RPC error -32601 (metho