Upstream range analyzed: 40a0454..01e4a1e (as of 2026-05-27).\n\nFork base considered: origin/main at ef5d599b6.\n\nCommits in range:\n- fdd0a07 feat: Respect tool visibility toggle in Agent tab (#2268)\n- cc7d78e Model picker: tabs for Free models vs Your providers (#2279)\n- 34be565 implement OpenAI in-app URL setter (#2281)\n- 01e4a1e [codex] fix hosted mixed protocol tools (#2285)\n\nAssessment:\n- #2268 is broad and cross-cuts chat ingestion/orchestration plus client threading plus web/mcp routes. High regression risk and likely backend-contract sensitivity.\n- #2285 appears valuable for mixed protocol stability, but touches hosted auth/web routes and server state semantics. Needs careful local-only adaptation to avoid upstream service assumptions.\n- #2281 adds SDK/runtime and sandbox behavior and may be useful for app embedding parity; medium scope.\n- #2279 is model-picker UX segmentation and likely product/branding-adjacent; low priority for fork goals.\n\nRecommended narrow next step (no bulk sync):\n1) Inspect and potentially port only #2285 client/server protocol-selection guards under local constraints (no upstream MCPJam backend dependency).\n2) If needed for app embedding parity, port #2281 in a second isolated patch.\n3) Defer #2268 until scoped decomposition identifies a minimal safe subset.\n\nFiles to inspect first:\n- mcpjam-inspector/client/src/hooks/use-aggregated-tools.ts\n- mcpjam-inspector/client/src/hooks/use-chat-session.ts\n- mcpjam-inspector/client/src/hooks/use-server-state.ts\n- mcpjam-inspector/server/routes/web/chat-v2.ts\n- mcpjam-inspector/server/routes/web/auth.ts\n\nNo code imported in this triage pass.
Upstream range analyzed: 40a0454..01e4a1e (as of 2026-05-27).\n\nFork base considered: origin/main at ef5d599b6.\n\nCommits in range:\n- fdd0a07 feat: Respect tool visibility toggle in Agent tab (#2268)\n- cc7d78e Model picker: tabs for Free models vs Your providers (#2279)\n- 34be565 implement OpenAI in-app URL setter (#2281)\n- 01e4a1e [codex] fix hosted mixed protocol tools (#2285)\n\nAssessment:\n- #2268 is broad and cross-cuts chat ingestion/orchestration plus client threading plus web/mcp routes. High regression risk and likely backend-contract sensitivity.\n- #2285 appears valuable for mixed protocol stability, but touches hosted auth/web routes and server state semantics. Needs careful local-only adaptation to avoid upstream service assumptions.\n- #2281 adds SDK/runtime and sandbox behavior and may be useful for app embedding parity; medium scope.\n- #2279 is model-picker UX segmentation and likely product/branding-adjacent; low priority for fork goals.\n\nRecommended narrow next step (no bulk sync):\n1) Inspect and potentially port only #2285 client/server protocol-selection guards under local constraints (no upstream MCPJam backend dependency).\n2) If needed for app embedding parity, port #2281 in a second isolated patch.\n3) Defer #2268 until scoped decomposition identifies a minimal safe subset.\n\nFiles to inspect first:\n- mcpjam-inspector/client/src/hooks/use-aggregated-tools.ts\n- mcpjam-inspector/client/src/hooks/use-chat-session.ts\n- mcpjam-inspector/client/src/hooks/use-server-state.ts\n- mcpjam-inspector/server/routes/web/chat-v2.ts\n- mcpjam-inspector/server/routes/web/auth.ts\n\nNo code imported in this triage pass.