rivetkit
RivetKit backend and Rivet Actor runtime guidance. Use for building, modifying, debugging, or testing Rivet Actors, registries, serverless/runner modes, deployment, or actor-based workflows.
Security Assessment
Detected risks:
About rivetkit
RivetKit is a comprehensive backend and runtime toolkit designed to support the development, deployment, and debugging of Rivet Actors. It enables developers to build high-performance, long-lived, in-memory processes that go beyond traditional HTTP endpoints, databases, or queues. By leveraging the actor-based model, RivetKit addresses the challenges of real-time collaboration, workflow orchestration, and geo-distributed data management, providing a more efficient and scalable approach for AI agents and complex applications.
The skill provides a robust set of features for inspecting and managing actors. Developers can access actor state, connections, RPCs, queue status, workflow history, and database schemas through dedicated inspector endpoints. It supports executing actions, running SQL queries, and replaying workflows, both in local development and production environments, with appropriate authentication. Additionally, RivetKit offers guidance for troubleshooting issues, including generating detailed reports on errors, environment details, and attempted solutions, and directs users to official Rivet support channels. Version checking ensures that projects are kept up-to-date with the latest RivetKit release, promoting compatibility and stability.
Targeted at developers working with AI, real-time systems, and complex workflows, RivetKit is ideal for those needing long-lived, in-memory processes that require more than conventional serverless solutions. It benefits teams building collaborative applications, distributed data systems, and workflow-driven AI agents. By providing detailed debugging tools, references to canonical documentation, and integration guidance, RivetKit empowers developers to efficiently manage actors, troubleshoot issues, and optimize their applications for performance and scalability.
FAQ
How do I debug a running Rivet Actor?
You can use the inspector HTTP API endpoints to examine actors, including their state, connections, RPCs, queues, and workflows. In local development, no auth token is needed; in production, provide the Authorization header with the Rivet Inspector token.
Which runtime environments are supported?
RivetKit supports multiple runtimes such as Node.js and Bun. Ensure you include the runtime version in any debugging report for accurate troubleshooting.
How can I ensure my project uses the latest RivetKit version?
Check the rivetkit version in your package.json under dependencies or devDependencies. If it is older than 2.2.0, upgrade using npm install [email protected].
What should I include when reporting an issue?
Include symptoms (local or deployed, error messages, relevant source code), attempts to solve the issue, and environment details such as RivetKit version, runtime, provider, and HTTP router.
Can I access the actor inspector endpoints without authentication?
Yes, in local development no authentication is required. In production, you must provide an Authorization header with the appropriate Rivet Inspector token.
All Files
118 filesInstall rivetkit
Quick Setup:
- Copy the skill folder to
.claude/skills/ - Claude will automatically detect and use the skill
Repository
rivet-dev/skills