mirror of
https://github.com/CopilotKit/CopilotKit.git
synced 2026-09-14 16:26:20 +08:00
de656faeaa
Addresses FAC-83 by preventing Metro bundler from resolving optional Expo modules and Node.js-only packages in React Native client builds. Root Cause: Metro bundler resolves ALL module specifiers in the dependency graph at build time. Dynamic import() and external marking don't prevent Metro from traversing the import graph. Solution: 1. Expo Modules - Move behind @copilotkit/react-native/attachments subpath 2. Telemetry - Isolate behind @copilotkit/shared/telemetry with conditional node/default exports Co-authored-by: Implementation fixes for moduleResolution and CJS exports verification
CopilotKit - Runtime
✨ 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.
🏆 Featured Examples
Documentation
To get started with CopilotKit, please check out the documentation.
Analytics & Privacy
CopilotKit uses Scarf for anonymous usage analytics to help improve the product. Scarf handles all privacy compliance and does not store raw IP addresses. This helps us understand how CopilotKit is being used and prioritize improvements.
Opting Out
To disable analytics, set the environment variable:
export COPILOTKIT_TELEMETRY_DISABLED=true
Or use the DO_NOT_TRACK standard:
export DO_NOT_TRACK=1