mirror of
https://github.com/CopilotKit/CopilotKit.git
synced 2026-09-14 16:26:20 +08:00
f8520c9804
Follow-up to #6993. That PR fixed two `react-core` references; four of their six citations were stale, so this audits the other 13. ## Method Three passes, because the first two are cheap and the third is the only one that finds real defects. 1. **Mechanical** — every `packages/...:NN-MM` citation: does the path exist, is the span in range? 71 citations, 57 with spans. 2. **Symbol** — every `useXxx(` and `<CopilotXxx` in the docs against the 389 identifiers actually exported from `v2/src`. 3. **Semantic** — read the cited lines and check they support the claim. This is where the rot lives: the lines exist, they just say something else. ## Findings fixed | File | Defect | | --- | --- | | `capabilities.md` | Cited `runtime/src/agent/index.ts:821-829,883-887` for "shallow-merges capabilities at the category level". Those are factory-mode config types and sampling params (`frequencyPenalty`, `stopSequences`). The mechanism is `:940-947` — whose own doc comment says **shallow-merged** — and `:999-1012`. | | `provider-setup.md` | Claimed the provider resolves `publicLicenseKey \|\| publicApiKey`. Only one of four sites does. Citation also pointed at an unrelated line (`copilotkit.tsx:172` is `source: "agent"`). | | `custom-message-renderers.md` | Cited lines 73-95 of a 93-line file. The iterate-and-break it describes is at `:68-91`. | | `suggestions.md` | `useFeatureFlag("suggestions")`, twice, with no import and no definition. CopilotKit exports no such hook. | | `threads.md` | `useThreadSelection()`, same problem. | ### The license-key one is a product finding, not just a docs bug Precedence when both keys are set is inconsistent in the code: | Site | Order | | --- | --- | | `CopilotKitProvider.tsx:487` | `publicApiKey ?? publicLicenseKey` | | `copilotkit.tsx:111` | `publicApiKey \|\| publicLicenseKey` | | `copilotkit.tsx:217` | `publicLicenseKey \|\| publicApiKey` | | `copilotkit.tsx:883` | `publicApiKey \|\| publicLicenseKey` | Three prefer `publicApiKey`, one prefers `publicLicenseKey`. So which wins depends on which path runs. Rather than document one order as if it were the contract, the doc now says to write the canonical name and not to set both — true regardless of path. **The underlying inconsistency is untouched here and probably wants its own issue.** ## Findings I retracted Recording these because two of my three automated passes produced false positives, and the ratio matters for anyone repeating this. - **50 "missing paths."** My regex alternated `(?:ts|tsx)`, so it matched `ts` first and truncated every `.tsx`. All 50 were my own artifact. Real count: zero missing paths. - **41 "unsupported spans."** A heuristic checking whether the claim's backticked identifiers appear in the cited lines. It attributes each `Source:` to the nearest paragraph above, which is the wrong one in multi-paragraph gotchas. Useful as a reading list, worthless as a finding. - **"13 uses of the deprecated provider."** Most were the *filename* `CopilotKitProvider.tsx` inside `Source:` citations, not component usages. There are 2 real JSX usages, both passing only `runtimeUrl`, both valid — and `provider-setup.md` already carries a callout explaining that `CopilotKit` is the v1/v2 bridge and `CopilotKitProvider` "is a perfectly good choice if you do not need the v1 bridge". No defect. ## Testing ``` $ python3 audit_citations.py citations: 71 mechanically broken: 0 with a line span: 57 path-only: 14 $ tsx scripts/sync-plugin-skills.ts --check plugin skill mirror in sync $ oxfmt --check skills/react-core/references/*.md All matched files use the correct format. ``` Symbol pass after the fixes leaves only legitimate non-exports: React's own hooks, two helpers the docs define inline (`useAvailableAgents`, `useMyFeatureFlag`), and `useAgents`, which `switching-agents.md` correctly documents as **not existing**. Edits were made in `packages/react-core/skills/` and mirrored by the sync script. ## Coverage, honestly The mechanical and symbol passes cover all 15 files completely. The semantic pass does not: I read roughly 15 of the 57 spans closely, prioritising the files documenting APIs that have moved most. The five defects above are what that subset produced. A full semantic read of the remaining ~40 spans would likely find more, and the same audit has not been run on the `runtime` skill (26 references) or `a2ui-renderer`. 🤖 Generated with [Claude Code](https://claude.com/claude-code) <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit - **Documentation** - Updated React guidance with current source references across capabilities, message renderers, attachments, chat components, client-side tools, debugging, human-in-the-loop rendering, tool calls, agent access, and agent switching. - Clarified that production SPAs require `runtimeUrl`, with Intelligence configured server-side on the runtime using `CPK_INTELLIGENCE_API_KEY`. - Removed outdated `publicLicenseKey` guidance from setup and API documentation. - Corrected feature-flag examples to use an application-defined hook. - Updated thread-selection examples to derive the active thread ID from application state. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
CopilotKit - React Core
✨ Why CopilotKit?
- Minutes to integrate - Get started quickly with our CLI
- Framework agnostic - Works with React, Next.js, AGUI and more
- Production-ready UI - Use customizable components or build with headless UI
- Built-in security - Prompt injection protection
- Open source - Full transparency and community-driven
🧑💻 Real life use cases
Deploy deeply-integrated AI assistants & agents that work alongside your users inside your applications.
🖥️ Code Samples
Drop in these building blocks and tailor them to your needs.
Build with Headless APIs and Pre-Built Components
// Headless UI with full control
const { visibleMessages, appendMessage, setMessages, ... } = useCopilotChat();
// Pre-built components with deep customization options (CSS + pass custom sub-components)
<CopilotPopup
instructions={"You are assisting the user as best as you can. Answer in the best way possible given the data you have."}
labels={{ title: "Popup Assistant", initial: "Need any help?" }}
/>
// Frontend actions + generative UI, with full streaming support
useCopilotAction({
name: "appendToSpreadsheet",
description: "Append rows to the current spreadsheet",
parameters: [
{ name: "rows", type: "object[]", attributes: [{ name: "cells", type: "object[]", attributes: [{ name: "value", type: "string" }] }] }
],
render: ({ status, args }) => <Spreadsheet data={canonicalSpreadsheetData(args.rows)} />,
handler: ({ rows }) => setSpreadsheet({ ...spreadsheet, rows: [...spreadsheet.rows, ...canonicalSpreadsheetData(rows)] }),
});
Integrate In-App CoAgents with LangGraph
// Share state between app and agent
const { agentState } = useCoAgent({
name: "basic_agent",
initialState: { input: "NYC" }
});
// agentic generative UI
useCoAgentStateRender({
name: "basic_agent",
render: ({ state }) => <WeatherDisplay {...state.final_response} />,
});
// Human in the Loop (Approval)
useCopilotAction({
name: "email_tool",
parameters: [
{
name: "email_draft",
type: "string",
description: "The email content",
required: true,
},
],
renderAndWaitForResponse: ({ args, status, respond }) => {
return (
<EmailConfirmation
emailContent={args.email_draft || ""}
isExecuting={status === "executing"}
onCancel={() => respond?.({ approved: false })}
onSend={() =>
respond?.({
approved: true,
metadata: { sentAt: new Date().toISOString() },
})
}
/>
);
},
});
// intermediate agent state streaming (supports both LangGraph.js + LangGraph python)
const modifiedConfig = copilotKitCustomizeConfig(config, {
emitIntermediateState: [
{
stateKey: "outline",
tool: "set_outline",
toolArgument: "outline",
},
],
});
const response = await ChatOpenAI({ model: "gpt-4o" }).invoke(
messages,
modifiedConfig,
);
🏆 Featured Examples
Documentation
To get started with CopilotKit, please check out the documentation.