[pull] main from CopilotKit:main#289
Merged
Merged
Conversation
…Kit/skills
- Remove 6 old auto-generated lifecycle skills (0-to-working-chat,
debug-and-troubleshoot, go-to-production, scale-to-multi-agent,
spa-without-runtime, v1-to-v2-migration)
- Add 8 canonical skills verbatim from github.com/CopilotKit/skills:
copilotkit-setup, copilotkit-develop, copilotkit-agui,
copilotkit-integrations, copilotkit-debug, copilotkit-upgrade,
copilotkit-contribute, copilotkit-self-update
- Update copilotkit-self-update install command to reference CopilotKit/CopilotKit
- Add .claude-plugin/{plugin,marketplace}.json and .mcp.json (repo URL and
version updated to match monorepo: CopilotKit/CopilotKit, v1.57.3)
- Exempt copilotkit-* slugs from sync orphan detection in sync-plugin-skills.ts;
runtime/react-core/a2ui-renderer remain synced from packages/*/skills as before
…zation, and exception-safe clearing
Extract incoming x-* headers from LangGraph's runtime config and republish
them via the forwarded-headers ContextVar so the httpx hook can attach
them to outbound provider requests. Apply documented precedence
(context > configurable, wrapper-dict > raw x-*) by processing sources
in order with first-write-wins and lowercasing keys at insertion so
mixed-case headers do not silently overwrite each other downstream.
Always clear the ContextVar on early exits so stale headers from a prior
request never leak into the next: explicit set_forwarded_headers({}) on
the RuntimeError no-active-runnable path and on the generic exception
fallback. The happy path already overwrites the ContextVar
unconditionally, even with an empty dict.
The change also installs the httpx event hook once per chat-model client
via a module-level set keyed by id(client), so models reused across
requests pick up fresh per-request headers without re-hooking.
…ence Add integration and edge-case coverage for the new _extract_forwarded_headers_from_config flow: wrapper-dict and raw x-* sources, context > configurable precedence, mixed-case key normalization, RuntimeError early-return clears stale ContextVar, exception path clears stale ContextVar, None and empty-config fallbacks, and a sync/async parity check that both call paths run the extraction.
…ython integrations Pin copilotkit==0.1.90 across the three CopilotKit-aware Python integrations (langgraph-python, strands, langgraph-fastapi) so the forwarded-header extraction from this PR is the version that runs in showcase. Bump ag-ui-langgraph to >=0.0.35 with the [fastapi] extra in langgraph-fastapi because copilotkit 0.1.90 requires it transitively; the previous ==0.0.34 pin would cause pip install to hard-fail.
…pose
Add LANGGRAPH_HTTP={"configurable_headers":{"include":["x-*"]}} to the
shared x-integration-defaults anchor so every LangGraph-based showcase
service tells langgraph-api to include x-* headers in the runtime
config. Without this env var, langgraph-api 0.7+ strips x-* headers
before the agent sees them, breaking D6 context routing end-to-end even
when the SDK side is correct.
Re-bump on top of main's new 102 baseline (PR #4985 absorbed the pre-existing 9-FAIL drift). Our PR adds 4 intentional version-pin divergences from Dojo (copilotkit 0.1.87 -> 0.1.90 in three Python integrations, ag-ui-langgraph from ==0.0.34 to >=0.0.35 in langgraph-fastapi), bringing the total to 106. The ag-ui-langgraph and copilotkit catch-up will reduce this back down once both release pipelines complete and Dojo reference examples pick up the new versions.
…nents inlineSnippets() runs after stripLeadingImports() removes the MDX's import lines, so its regex scan can't tell whether a `<Component />` reference is a snippet lookup or a real React component rendered via the docsComponents registry. Every imported component triggered a false-positive "[docs-render] snippet missing for component X" warning. Capture the set of imported component names BEFORE stripping, then short-circuit the warning when the regex hits one of those names. Catches NewLookAndFeelPreview, AgentCoreCommandTabs, CodePanel, CodeShowcase, Frame, IframeSwitcher, ImageAndCode, LinkToCopilotCloud, and StartProviders (the full current set imported into snippet MDX files under src/content/snippets/), plus any future additions automatically. The runtime render path is unchanged: the docsComponents registry in mdx-registry.tsx still resolves these names at render time.
…ebar
The Built-in Agent sidebar still rendered the deprecated tutorials section
("Tutorial: AI Todo App", "Tutorial: AI Textarea" with step pages) even
after PR #4987 added 301 redirects for /{fw}/tutorials/:path* paths.
The redirects fired on click, but the entries should never have appeared.
Root cause: integrations/built-in-agent/meta.json declared a
"---Tutorials---" section header followed by a "...tutorials" spread.
BIA runs in docs_mode "authored" which routes through buildFrameworkOnlyNav;
that path preserves section headers and recurses through spreads. The
spread descended into integrations/built-in-agent/tutorials/ and
enumerated the AI Todo App and AI Textarea subfolders into the sidebar.
Other frameworks were already safe: buildFrameworkOverridesNav (used by
generated-mode frameworks like langgraph, mastra, google-adk) explicitly
strips section nodes from per-framework override nav.
Fix: remove the "---Tutorials---" section header and "...tutorials"
spread from BIA's parent meta.json. Nothing now references the
tutorials folder from BIA's nav, so the spread handler never recurses
into it and the entries disappear. Two-line minimal change.
Tutorial source MDX under content/docs/integrations/built-in-agent/tutorials/
stays in place (PDX-100 owns the rewrite). The redirect catalog in
lib/seo-redirects.ts is untouched.
Refs PDX-205.
…x warnings
Two follow-on fixes to the same docs-render snippet pipeline.
1. ComponentExamples SSR error. The shared copilot-ui.mdx snippet
imports ComponentExamples from @/snippets/component-examples.mdx
and renders it. When copilot-ui.mdx is recursively inlined into a
parent MDX (e.g. crewai-flows/quickstart.mdx via <CopilotUI />),
stripLeadingImports removes the import line, then the regex hits
<ComponentExamples /> with no matching SNIPPET_MAP entry. The
inliner leaves the bare JSX in the output and at MDX render time
next-mdx-remote throws "Expected component ComponentExamples to be
defined". Add the snippet to SNIPPET_MAP so the recursive inliner
resolves it the same way it resolves CopilotUI.
The gatherImportedComponentNames shortcut from the same PR only
captures imports in the OUTER MDX, not in recursively inlined
snippet bodies — a deeper structural limitation worth fixing later
but not load-bearing here. The SNIPPET_MAP entry resolves both the
SSR error AND the false-positive warning in one line.
2. Icon-library bare references logging spurious warnings. Lucide
Square-prefixed icons (SquareTerminal, SquareChartGantt) and
react-icons fa / si / pi families appear bare in many MDX files —
no import, resolved at render time via the registry's emoji stubs.
The existing endsWith("Icon") filter doesn't catch these. Add a
PascalCase-prefix check next to it.
Strictly additive; runtime render path unchanged.
Surface hitl-in-chat, hitl-in-app, and gen-ui-interrupt in the dojo's hand-curated Featured list so they are visible at the top of the sidebar for every integration that supports them (LGP, ADK, etc.). Unsupported demos are silently skipped per the existing filter logic. Resolves OSS-138 Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Add EXTRA_FEATURED_BY_INTEGRATION map so hitl-in-chat, hitl-in-app, and gen-ui-interrupt only appear in Featured for langgraph-python, langgraph-typescript, langgraph-fastapi, and google-adk. All other integrations see the original 9-item Featured list unchanged. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
…on (#4980) ## Summary - Adds per-integration `EXTRA_FEATURED_BY_INTEGRATION` map to the dojo shell - `hitl-in-chat`, `hitl-in-app`, and `gen-ui-interrupt` appear in Featured **only** for LangGraph Python, LangGraph TypeScript, LangGraph FastAPI, and Google ADK - All other integrations see the original 9-item Featured list — zero behavioral change - Unsupported demos (e.g. `gen-ui-interrupt` on ADK) are silently skipped per existing filter logic Resolves OSS-138 ## Test plan - [x] Built-in Agent: 9 Featured items (original list, no HITL) — no change from before - [x] LangGraph Python: 12 Featured items (original 9 + 3 HITL extras) - [x] Google ADK: 11 Featured items (original 9 + 2 HITL; `gen-ui-interrupt` correctly skipped as `not_supported`) - [ ] Review order/placement with Atai before merging 🤖 Generated with [Claude Code](https://claude.com/claude-code)
#4972) ## Summary - Replaces the 6 old auto-generated lifecycle skills in root `skills/` (`0-to-working-chat`, `debug-and-troubleshoot`, `go-to-production`, `scale-to-multi-agent`, `spa-without-runtime`, `v1-to-v2-migration`) with the correct canonical skills from `github.com/CopilotKit/skills` — the old ones were generated by `@tanstack/intent`, never reviewed, incorrect - `skills/runtime`, `skills/react-core`, `skills/a2ui-renderer` remain — still synced from `packages/*/skills/` as before - Adds `.claude-plugin/plugin.json`, `.claude-plugin/marketplace.json`, and `.mcp.json` (wires the `copilotkit-docs` MCP server) - Updates `sync-plugin-skills.ts` to exempt `copilotkit-*` slugs from orphan detection so the sync check does not flag them ## Skills added | Slug | Purpose | |------|---------| | `copilotkit-setup` | Add CopilotKit to a project | | `copilotkit-develop` | Build AI features with v2 hooks/components | | `copilotkit-agui` | AG-UI protocol and custom backends | | `copilotkit-integrations` | Wire LangGraph, CrewAI, Mastra, PydanticAI, ADK, etc. | | `copilotkit-debug` | Diagnose runtime/agent/streaming issues | | `copilotkit-upgrade` | v1 → v2 migration | | `copilotkit-contribute` | Contribute to the OSS monorepo | | `copilotkit-self-update` | Refresh installed skills | ## Test plan - [ ] Install plugin locally: `cc plugins install /path/to/CopilotKit` — verify 8 skills appear - [ ] Verify `copilotkit-docs` MCP server auto-configures via `.mcp.json` - [ ] Confirm `pnpm run check:plugin-skills` still passes - [ ] Archive `github.com/CopilotKit/skills` after merge
…ebar (#4994) ## Summary Tutorial entries appeared in the sidebar nav on every Built-in Agent docs page (e.g. `/built-in-agent/quickstart`) despite the section being deprecated. Clicks worked because the redirect catalog 301s `/{fw}/tutorials/:path*` to `/{fw}/quickstart`, but the entries should not be visible at all. ## Root cause BIA runs in `docs_mode: "authored"`, which routes through `buildFrameworkOnlyNav` → `buildNavTree`. That code path keeps section headers and recurses through `"...folder"` spreads (unlike the generated-mode path used by langgraph/mastra/google-adk, which strips section headers via `buildFrameworkOverridesNav`). BIA's `integrations/built-in-agent/meta.json` declared `"---Tutorials---"` + `"...tutorials"`, so the spread descended into the tutorials folder and enumerated its subfolders into the sidebar. ## Fix Remove the two lines from BIA's parent `meta.json`: ```diff "---Premium Features---", "...premium", -"---Tutorials---", -"...tutorials", "---Troubleshooting---", "...troubleshooting" ``` Source MDX is preserved. ## Test plan - [x] JSON validity confirmed via `node -e 'JSON.parse(...)'`. - [ ] Post-deploy: confirm no `Tutorial:` entries in `/built-in-agent/quickstart` sidebar HTML. - [ ] Post-deploy: confirm `/built-in-agent/tutorials/ai-todo-app/step-2-setup-copilotkit` still 301s to `/built-in-agent/quickstart`.
…tExamples render (#4992) ## Summary Three changes to `src/lib/docs-render.tsx` that together eliminate the `[docs-render] snippet missing for component X` log noise on prod AND fix a hard SSR error on `/quickstart` caused by a missing `ComponentExamples` registration. ## Changes **1. Suppress warnings for components the MDX imports** (existing scope of this PR). `inlineSnippets()` runs after `stripLeadingImports()` removes the MDX's `import` lines, so the regex can't tell a `<PascalCase />` reference apart from a real React component imported into the file. Every imported component triggered a false-positive `snippet missing` warning. The page still rendered correctly via `docsComponents`; only the log was wrong. Capture imports before stripping, then short-circuit the warning when the regex hits one of those names. **2. Add `ComponentExamples` to `SNIPPET_MAP`** (new). `copilot-ui.mdx` imports `ComponentExamples` from `@/snippets/component-examples.mdx` and renders it. When `copilot-ui.mdx` is recursively inlined into a parent MDX (e.g. via `<CopilotUI />`), the import line is stripped and the inliner finds no `SNIPPET_MAP` entry for `ComponentExamples`. The bare JSX survives the inliner and `next-mdx-remote` throws `Expected component ComponentExamples to be defined` at SSR. The error is caught in a partial-render error boundary so the page returns 200, but a chunk of content is missing from the rendered output. Add `ComponentExamples: "component-examples.mdx"` to `SNIPPET_MAP` so the recursive inliner resolves it the same way it resolves `CopilotUI`. One line, fixes both the SSR error and the cosmetic warning. (Note: the `gatherImportedComponentNames` shortcut from change 1 doesn't help here because it captures imports from the OUTER MDX, not from recursively-inlined snippet bodies. That deeper structural limitation can be addressed later; the `SNIPPET_MAP` entry resolves the immediate failure.) **3. Skip icon-prefix bare references** (new). Lucide `Square*` icons (`SquareTerminal`, `SquareChartGantt`) and `react-icons` `Fa*` / `Si*` / `Pi*` families are bare-referenced in many MDX files — no explicit import, resolved at render time via the registry's emoji stubs in `docsComponents`. The existing `endsWith("Icon")` filter doesn't catch these PascalCase + library-prefix shapes. Add a regex check next to it: `/^(Fa|Si|Pi|Square)[A-Z]/`. ## Components covered after changes 1-3 The import-aware filter catches every `import { X } from "..."` reference (current set: AgentCoreCommandTabs, CodePanel, CodeShowcase, Frame, IframeSwitcher, ImageAndCode, LinkToCopilotCloud, NewLookAndFeelPreview, StartProviders). The icon-prefix filter catches `FaArrowUp`, `FaWrench`, `SquareTerminal`, `SquareChartGantt`, and future icon-library additions matching the prefix shape. `ComponentExamples` is registered in `SNIPPET_MAP` so the inliner resolves it instead of warning. Remaining bare references that don't match any of the above (e.g. `CloudCopilotKit`) still warn — these are runtime React components registered in `docsComponents` but not imported in the MDX. The right cleanup for those is to add explicit `import { CloudCopilotKit } from "..."` lines in the MDX, which the import-aware filter then catches automatically. Out of scope for this PR. ## Adjacent observation (not fixed) While diagnosing change 2, found that the underlying `new-look-and-feel.tsx` component file referenced by `troubleshooting/migrate-to-1.8.2.mdx` doesn't exist on disk. The MDX registry stubs the name with `<div>{children}</div>`, so the preview area in that page renders empty. This PR doesn't address the empty-preview behavior; the snippet-missing log noise is purely cosmetic. ## Test plan - [x] Diff is additive only; runtime render path unchanged. - [ ] Local: build shell-docs, hit `/built-in-agent/quickstart` + `/crewai-crews/quickstart` + `/built-in-agent/agentic-protocols/mcp` + `/built-in-agent/shared-state/predictive-state-updates` + `/built-in-agent/troubleshooting/migrate-to-1.8.2`. Confirm zero `[docs-render] snippet missing` and zero `Expected component ComponentExamples to be defined` warnings in the dev server log. - [ ] Local: confirm the ComponentExamples Tabs block actually renders on `/crewai-crews/quickstart` (was silently missing pre-fix). - [ ] Post-deploy: re-check Railway logs for the warning + error class over a sample of page loads.
…4984) ## Summary Wires per-request x-* headers through the CopilotKit Python middleware so LangGraph-based agents receive the original request's forwarded headers (D6 "everything works" prerequisite). Four logical pieces: 1. **sdk-python forwarded-header extraction** — `_extract_forwarded_headers_from_config()` reads x-* headers from LangGraph's runtime config (both wrapper-dict `copilotkit_forwarded_headers` and raw x-* keys), applies documented precedence (context > configurable, wrapper > raw), lowercases keys at insertion to make precedence deterministic across mixed-case headers, and always clears the ContextVar on early-exit paths so stale headers from a prior request cannot leak. 2. **sdk-python tests** — 47 new/modified test cases covering wrapper-dict and raw extraction, context > configurable precedence, mixed-case normalization, RuntimeError early-return clearing, exception-path clearing, None/empty-config fallbacks, sync/async parity. 3. **Showcase Python pins** — pins `copilotkit==0.1.90` across langgraph-python, strands, and langgraph-fastapi so the version that runs in showcase matches the version that contains this fix. Bumps `ag-ui-langgraph[fastapi]>=0.0.35` in langgraph-fastapi because copilotkit 0.1.90 requires it transitively (the previous `==0.0.34` pin would cause `pip install` to hard-fail). 4. **Showcase docker-compose** — adds `LANGGRAPH_HTTP={"configurable_headers":{"include":["x-*"]}}` to the shared `x-integration-defaults` anchor so langgraph-api includes x-* headers in the runtime config; without this, langgraph-api 0.7+ strips x-* headers before the agent ever sees them. ## Companion PR Depends on the matching ag-ui PR that adds per-request header forwarding across 5 integration adapters (langgraph, mastra, vercel-ai-sdk, langchain, claude-agent-sdk). After ag-ui releases, bump the `@ag-ui/langgraph` pin in `packages/sdk-js/package.json` in a follow-up. ## CR loop - Round 1: surfaced 12 findings (4 ag-ui clusters + 6 CopilotKit clusters) across 14 reviewers. - Round 2 fix: docker-compose LANGGRAPH_HTTP YAML merge bug, sdk-python wrapper-dict precedence, exception-path ContextVar leak, RuntimeError-path leak, langgraph-fastapi version conflict. - Round 2 confirmation: 14 reviewers, surfaced 4 new Bucket (a) findings on CopilotKit side. - Round 3 fix: lowercase-at-insertion + always-clear ContextVar on both early-exit paths + ag-ui-langgraph[fastapi] bump. - Round 3 confirmation: 7 reviewers, all NO_BUCKET_A_FINDINGS. - Pre-push-quality: green (ruff, 47+87 pytests, build, docker-compose config). ## Test plan - [ ] CI green - [ ] Showcase D6 LangGraph integration receives x-aimock-context header end-to-end with x-AIMock-Strict propagation - [ ] No regressions in other Python integrations (strands, langgraph-fastapi) - [ ] Docker compose still boots all integrations with the new shared LANGGRAPH_HTTP env 🤖 Generated with [Claude Code](https://claude.com/claude-code)
Cuts copilotkit 0.1.91 with forwarded-header extraction landed in #4984 (_extract_forwarded_headers_from_config + lowercase-at-insertion precedence + exception-safe ContextVar clearing).
## Summary Bumps `sdk-python/pyproject.toml` from 0.1.90 → 0.1.91 so the forwarded-header extraction added in #4984 ships to PyPI consumers. Showcase Python integrations will pick this up via the follow-up pin-bump PR. ## What's in 0.1.91 From #4984: - `_extract_forwarded_headers_from_config()` extracts x-* headers from LangGraph's RunnableConfig - Lowercase-at-insertion key normalization for deterministic precedence - Exception-safe ContextVar clearing on RuntimeError and generic Exception paths ## Publishing PyPI publish is manual — runs locally via `poetry publish` after merge. Once #4996 lands, this will become automated.
Picks up _extract_forwarded_headers_from_config from PR #4984, now shipped as copilotkit 0.1.91 on PyPI. Three Python integrations move forward together: langgraph-python, strands, langgraph-fastapi. Updates validate-pins ratchet hash (count stays 106, FAIL set shifted because showcase pins now diverge from Dojo on 0.1.91 vs 0.1.87). Showcase auto-redeploys to Railway on merge via showcase_build.yml (path filter showcase/**).
.reference-content p { margin-bottom: 1rem } is unlayered CSS and
always beats the layered prose-no-margin utility from fumadocs-ui,
causing visible extra space at the bottom of info callout boxes.
Mirror prose-no-margin's intent at (0,2,1) specificity in globals.css
so the first/last-child margin resets actually apply.
Also bump NODE_OPTIONS in the lefthook test-and-check-packages hook
to 8 GB — @copilotkit/core:build bundles many deps inline with
rolldown and exhausts the default 4 GB V8 heap, causing a native
binding crash on every pre-commit run.
) ## Summary Bumps `copilotkit==0.1.90` → `copilotkit==0.1.91` in three showcase Python integration `requirements.txt` files: - `showcase/integrations/langgraph-python` - `showcase/integrations/strands` - `showcase/integrations/langgraph-fastapi` Picks up the forwarded-header extraction landed in #4984 and published as `copilotkit 0.1.91` on PyPI by the release in #5011. Updates `validate-pins` ratchet hash in `showcase/scripts/fail-baseline.json` (count stays at 106, FAIL set shifted because showcase pins now diverge from Dojo on `0.1.91` vs `0.1.87`). ## Why split from the @ag-ui/langgraph pin bump The matching `@ag-ui/langgraph` bump (`0.0.31` → `0.0.33` in `packages/runtime/package.json` and `packages/sdk-js/package.json`) waits for the ag-ui side: `publish-release.yml` is currently broken (OIDC `pull_request` vs `push` event mismatch — last 30 runs all failed). Fix is in flight in a separate session. Once `@ag-ui/langgraph 0.0.33` is live on npm, a follow-up PR will bump those two pins. This split unblocks D6 LGP today. D6 LGT remains waiting on the ag-ui side. ## Test plan - [ ] CI green - [ ] After merge, showcase_build.yml redeploys langgraph-python + strands + langgraph-fastapi to Railway - [ ] Production D6 LGP probe verifies forwarded headers reach the agent via aimock logs
## Release monorepo v1.58.0 **Scope:** `monorepo` | **Bump:** `minor` --- ### How this release process works 1. **This PR was created automatically** by the "release / create-pr" workflow. It bumped the `monorepo` packages to `1.58.0` and generated AI-enhanced release notes. 2. **CI runs on this PR** — the full test suite (unit tests, lint, type checks, build) must pass before merging. This is the review gate. 3. **Review the release notes** in `release-notes.md` in this PR. If a Notion draft was created, you can edit the release notes there before merging. 4. **When this PR is merged**, the `release / publish` workflow automatically: - Builds all packages - Publishes the `monorepo` packages to npm at version `1.58.0` - Creates git tag `monorepo/v1.58.0` - Creates a GitHub Release with the final release notes ### Before merging - [ ] CI is green (tests, lint, types, build) - [ ] Version bumps look correct - [ ] Release notes are accurate (edit in Notion if a draft was created) --- > **Do not merge until CI is fully green.** The full test suite runs automatically on this PR.
…s across 6 integrations 6 prebuilt-components pages were missing their PrebuiltComponents import, causing the inlineSnippets regex to skip them and drop the framework prop (iframe URLs defaulted to langgraph). 8 HITL pages had copy-pasted code examples using the deprecated v1 parameters array format instead of Zod schemas. Added a component-imports validation check to verify-shell-docs.ts to catch missing snippet imports going forward. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
…5013) Before: <img width="781" height="87" alt="Screenshot 2026-05-26 at 9 35 58 AM" src="https://github.com/user-attachments/assets/547dc74b-04e7-4784-85b4-823f1adaefb4" /> After: <img width="784" height="69" alt="Screenshot 2026-05-26 at 9 39 03 AM" src="https://github.com/user-attachments/assets/e8cf7948-a2bb-439a-90ef-9b73b40504dc" /> ## Summary - `.reference-content p { margin-bottom: 1rem }` in `globals.css` is **unlayered** CSS, so it always wins over fumadocs-ui's `prose-no-margin` utility (which lives in `@layer utilities`), causing visible extra space at the bottom of info callout boxes - Fix mirrors `prose-no-margin`'s first/last-child intent at `(0,2,1)` specificity in `globals.css` so the margin resets actually apply ## Test plan - [x] Open any docs page with a `<Callout>` block (e.g. a quickstart page) - [x] Verify no extra bottom padding/margin inside the callout box - [x] Check both light and dark mode - [x] Check callouts with and without a `title` prop
Picks up per-request header forwarding (onRequest hook + headerFactory) and the prepareStream configurable+context partition fix from ag-ui-protocol/ag-ui#1763. Together with copilotkit==0.1.91 on the Python side (R3a), this unblocks D6 LGP/LGT header propagation. The mergeConfigs() change in 0.0.33 also fixes the HTTP 400 from langgraph-api 0.7+ when both configurable and context are present. Bumped in two files: - packages/runtime/package.json: 0.0.31 -> 0.0.33 - packages/sdk-js/package.json: 0.0.31 -> 0.0.33 Added @ag-ui/langgraph to minimumReleaseAgeExclude in .npmrc. pnpm-lock.yaml regenerated. Showcase auto-redeploys on merge via showcase_build.yml.
## Summary Bumps `@ag-ui/langgraph` from `0.0.31` to `0.0.33` in `packages/runtime` and `packages/sdk-js`. Regenerates the pnpm lockfile. Companion to R3a (`copilotkit==0.1.91` Python pin bump). Together they complete the D6 header-forwarding chain for LangGraph integrations. ## What 0.0.33 contains From [ag-ui-protocol/ag-ui#1763](ag-ui-protocol/ag-ui#1763): - Per-request `headers` map + `onRequest` hook on LangGraphClient — per-request x-* attaches to every outbound call - prepareStream partitions runtime config into `configurable` + `context` so langgraph-api 0.7+ no longer returns HTTP 400 - mergeConfigs() extended with `context_schema` allowlist (gated on schemaKeys?.config) - Header preservation through clone() Published via OIDC + provenance from ag-ui's fixed publish-release.yml. Also adds `@ag-ui/langgraph` to `minimumReleaseAgeExclude` in `.npmrc` since 0.0.33 was just published. ## Test plan - [ ] CI green - [ ] After merge, showcase_build.yml redeploys LangGraph integrations - [ ] D6 LGP probe flips GREEN (currently RED on the 0.0.31 pin) - [ ] D6 LGT probe also exercises the new chain
…h-typescript R3b bumped the monorepo packages but missed two showcase-level override pins. The langgraph-typescript integration pins @ag-ui/langgraph directly in both its top-level and src/agent package.json files, bypassing whatever @copilotkit/runtime transitively resolves. Without this bump, the showcase LGT Docker image bakes 0.0.32 even though the monorepo runtime/sdk-js are on 0.0.33 (R3b). This is what's keeping the D6 LGT probe RED. Path filter showcase/** matches, so showcase_build.yml fires on merge to rebuild + Railway-redeploy langgraph-typescript with the real 0.0.33.
Derive snippet component names from SNIPPET_MAP in docs-render.tsx at runtime instead of maintaining a hardcoded 35-entry set that was already 13 entries behind. Replace name-level handledByInline gate with per-match inline pattern check to fix a false-negative path. Align function signature with sibling check functions. Add 3 unit tests. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
…ipt overrides (#5016) ## Summary Bumps two showcase-level `@ag-ui/langgraph` override pins from `0.0.32` to `0.0.33`: - `showcase/integrations/langgraph-typescript/package.json` - `showcase/integrations/langgraph-typescript/src/agent/package.json` Regenerates both `package-lock.json` files. ## Why this is needed (after R3b already shipped) R3b (#5015) bumped `packages/runtime` and `packages/sdk-js` to consume `@ag-ui/langgraph@0.0.33`. But the langgraph-typescript showcase integration pins `@ag-ui/langgraph` directly in its own `package.json` files via `overrides`, which overrides whatever the runtime transitively pulls. Without this PR, the LGT Docker image bakes 0.0.32 and the D6 LGT probe stays RED. This is the final ag-ui-side bump needed to complete the LGT header-forwarding chain end-to-end. ## What's in @ag-ui/langgraph 0.0.33 (Same as documented in #5015.) Per-request `onRequest` hook, prepareStream configurable+context partition fix for langgraph-api 0.7+, mergeConfigs context_schema allowlist. ## Test plan - [ ] CI green - [ ] After merge, `showcase_build.yml` auto-fires (path filter `showcase/**` matches) - [ ] langgraph-typescript Docker image rebuilds + pushes to GHCR - [ ] Railway redeploys langgraph-typescript service - [ ] D6 LGT probe flips GREEN
## Summary - Switches `packages/angular` from a proprietary "Commercial" license to MIT, aligning it with the rest of the CopilotKit packages. - Updates `packages/angular/LICENSE` to the MIT text (Copyright (c) Tawkit Inc.) and sets `"license": "MIT"` in `packages/angular/package.json`. ## Test plan - [ ] CI passes
Extends the active rendering path with D6 support so dashboard cells
can display D6 ("parity vs reference") state. cell-model.ts gains
ceilingDepth | 6 + d6 TestLevel field + resolveD6() + D6-ceiling
chip-color algorithm. unified-cell.tsx + feature-grid.tsx render the
new D6 chip. live-status.ts gets the small Dimension/BadgeRender delta
the branch needed.
Until d6:<slug>/<featureId> PB rows start flowing (separate PR for the
D6 probe driver + per-framework fixtures), every cell renders D6 gray
("no data -- probe pending"). This is the accurate state -- visibility
without functional risk.
Cherry-picked from feat-d6-everything-works (the per-framework fixtures
branch). The remainder of that branch -- d6-all-pills driver, fixture
reorg, harness config -- lands in a follow-up PR now that the ag-ui
header-forwarding prerequisites (#4984, #4951, #5015, #5016) are in.
## Summary
Extends the showcase dashboard's active cell rendering path with D6
support so D6 chips can display on every cell. Today D6 was only
referenced in the chips-explainer legend; CellModel capped at
ceilingDepth: 0 | 3 | 4 | 5 with no D6 in UnifiedCell.
## What this PR changes
- `cell-model.ts`: adds `d6: TestLevel | null` field, `resolveD6()`,
extends `achievedDepth`/`ceilingDepth` to `| 6`, D6-ceiling algorithm
for chip color
- `unified-cell.tsx`: renders the D6 chip
- `feature-grid.tsx`: small wiring to surface the new field
- `live-status.ts`: delta from the branch (Dimension/BadgeRender
extensions)
## State after merge
Every cell renders a D6 chip. Until `d6:<slug>/<featureId>` PB rows flow
(follow-up PR for the D6 probe driver + per-framework fixtures), every
D6 chip is gray ("no data — probe pending"). This is the accurate state.
## Why this is safe to ship now
No data layer changes. No probe driver changes. Zero functional risk to
existing cells (they keep their D5-ceiling chip colors). Pure additive
rendering plumbing.
## Follow-up
The d6-all-pills probe driver + d4/d6/shared per-framework fixture reorg
lands in a separate PR (rebased from `feat-d6-everything-works`). That's
what starts populating real D6 state.
…#5020) ## Summary Adds D6 (Parity / Reference) to the cell-drilldown DIMENSIONS array so clicking any cell chip shows D6 status alongside d5/e2e/d2/health/smoke. CellModel already has the d6 field (#5018); this is the one-line missing piece to surface it. ## Test plan - [ ] Click a cell chip -> drilldown panel shows D6 row
#5014) ## Summary - **6 prebuilt-components pages** were missing their `PrebuiltComponents` import, causing the `inlineSnippets()` regex to skip them and the `framework` prop to be dropped (iframe URLs defaulted to `langgraph` instead of the correct integration) - **8 HITL pages** had copy-pasted code examples using the deprecated v1 `parameters: [{ name, type }]` array format instead of `parameters: z.object({...})` Zod schemas - Added a `checkComponentImports()` validation to `verify-shell-docs.ts` to catch missing snippet imports going forward ### Affected pages **Prebuilt-components** (missing import): agno, aws-strands, crewai-flows, llamaindex, microsoft-agent-framework, pydantic-ai **HITL code examples** (deprecated params format): adk, ag2, agent-spec, agno, llamaindex, mastra, microsoft-agent-framework, pydantic-ai ## Test plan - [ ] Serve shell-docs locally (`cd showcase/shell-docs && npx next dev`) and verify prebuilt-components pages render with correct iframe content - [ ] Verify HITL pages show `parameters: z.object({...})` in code blocks - [ ] Run `npx tsx showcase/scripts/verify-shell-docs.ts --skip-build` and confirm no component-import warnings 🤖 Generated with [Claude Code](https://claude.com/claude-code)
## Summary Adds a D6 overlay section to the dashboard, showing green/gray/red counts across all wired cells based on parity-vs-reference probe results. Pairs with #5018 (CellModel D6 field) and #5020 (D6 drilldown dimension). ## Files - **overlay-types.ts**: add `"d6"` to the `Overlay` union and `ALL_OVERLAYS` array - **adaptive-stats-bar.tsx**: new `D6Section` component + `D6Stats` interface + `d6Stats` prop - **overlay-toggle-bar.tsx**: add D6 to `ALL_OVERLAYS` and `OVERLAY_LABELS` for the toggle pill - **page.tsx**: compute D6 stats via `resolveCell` and pass to `AdaptiveStatsBar` - **overlay-toggle-bar.test.tsx**: update pill count assertion (5 -> 6) - **overlay-selector-integration.test.tsx**: add `"d6"` to the all-overlays test case ## Test plan - [x] 44 existing overlay tests pass (overlay-toggle-bar, overlay-selector-integration, useOverlays) - [ ] Dashboard shows D6 toggle pill; toggling it shows "X green / Y gray / Z red" tally
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
7 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
See Commits and Changes for more details.
Created by
pull[bot] (v2.0.0-alpha.4)
Can you help keep this open source service alive? 💖 Please sponsor : )