NNathan Flurrychore(release): update version to 2.3.31

f6926c31创建于 4 天前历史提交

文件	最后提交记录	最后更新时间
frontend	chore: fmt	4 个月前
src	chore: fmt	4 个月前
.gitignore	feat: `registry.start()` (#4477) * feat(rivetkit): add registry.start() as the default server pattern Replace the srvx + Hono + vite-plugin-srvx setup with a simpler registry.start() that starts the manager server, serves static files from public/ if it exists, and runs the actor driver. This is now the recommended way to run RivetKit. Key changes: - Add registry.start() method to Registry class - Add publicDir config option for static file serving - Move @hono/node-server and @hono/node-ws to regular deps - Update client default endpoint to http://localhost:6420 - Add deprecation warning when no endpoint is passed to client - Migrate all 30 examples to the new pattern - Update quickstart docs and client docs Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> * docs: update all docs to use registry.start() and consistent patterns - Replace separate actors.ts/server.ts with single index.ts + registry.start() - Update all code examples to import from "./index" instead of "./actors" - Standardize createClient endpoint to localhost:6420 (not 8080) - Remove srvx references, replace with npx tsx --watch - Add registry.start() to runtime-modes comparison and registry-configuration - Update skill-base-rivetkit.md to reference registry.start() as primary - Update StepRunServer default file to index.ts - Update react quickstart to remove StepSetupServer/StepRunServer Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	7 个月前
README.md	chore: simplify queue api (#4229) # Description Please include a summary of the changes and the related issue. Please also include relevant motivation and context. ## Type of change - [ ] Bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected) - [ ] This change requires a documentation update ## How Has This Been Tested? Please describe the tests that you ran to verify your changes. ## Checklist: - [ ] My code follows the style guidelines of this project - [ ] I have performed a self-review of my code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes to the documentation - [ ] My changes generate no new warnings - [ ] I have added tests that prove my fix is effective or that my feature works - [ ] New and existing unit tests pass locally with my changes	8 个月前
index.html	feat: use cases (#4100) # Description Please include a summary of the changes and the related issue. Please also include relevant motivation and context. ## Type of change - [ ] Bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected) - [ ] This change requires a documentation update ## How Has This Been Tested? Please describe the tests that you ran to verify your changes. ## Checklist: - [ ] My code follows the style guidelines of this project - [ ] I have performed a self-review of my code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes to the documentation - [ ] My changes generate no new warnings - [ ] I have added tests that prove my fix is effective or that my feature works - [ ] New and existing unit tests pass locally with my changes	8 个月前
package.json	chore(release): update version to 2.3.31	4 天前
tsconfig.json	chore(examples): update examples to standardized format (#3799)	9 个月前
turbo.json	feat: use cases (#4100) # Description Please include a summary of the changes and the related issue. Please also include relevant motivation and context. ## Type of change - [ ] Bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected) - [ ] This change requires a documentation update ## How Has This Been Tested? Please describe the tests that you ran to verify your changes. ## Checklist: - [ ] My code follows the style guidelines of this project - [ ] I have performed a self-review of my code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes to the documentation - [ ] My changes generate no new warnings - [ ] I have added tests that prove my fix is effective or that my feature works - [ ] New and existing unit tests pass locally with my changes	8 个月前
vite.config.ts	feat: `registry.start()` (#4477) * feat(rivetkit): add registry.start() as the default server pattern Replace the srvx + Hono + vite-plugin-srvx setup with a simpler registry.start() that starts the manager server, serves static files from public/ if it exists, and runs the actor driver. This is now the recommended way to run RivetKit. Key changes: - Add registry.start() method to Registry class - Add publicDir config option for static file serving - Move @hono/node-server and @hono/node-ws to regular deps - Update client default endpoint to http://localhost:6420 - Add deprecation warning when no endpoint is passed to client - Migrate all 30 examples to the new pattern - Update quickstart docs and client docs Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> * docs: update all docs to use registry.start() and consistent patterns - Replace separate actors.ts/server.ts with single index.ts + registry.start() - Update all code examples to import from "./index" instead of "./actors" - Standardize createClient endpoint to localhost:6420 (not 8080) - Remove srvx references, replace with npx tsx --watch - Add registry.start() to runtime-modes comparison and registry-configuration - Update skill-base-rivetkit.md to reference registry.start() as primary - Update StepRunServer default file to index.ts - Update react quickstart to remove StepSetupServer/StepRunServer Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>	7 个月前

AI Agent

Example project demonstrating queue-driven Rivet Actor AI agents with streaming Vercel AI SDK responses.

Getting Started

git clone https://github.com/rivet-dev/rivet.git
cd rivet/examples/ai-agent
npm install
npm run dev

Features

Actor-per-agent pattern with a coordinating manager Rivet Actor
Queue-based intake using for await over c.queue.iter(...) inside the run loop
Streaming AI responses sent to the UI as they arrive
Persistent history stored in Rivet Actor state
Live status updates via events and polling

Prerequisites

OpenAI API key set as OPENAI_API_KEY

Implementation

The AgentManager creates and tracks agent actors, while each AI agent Rivet Actor consumes queue messages in run and streams responses with the Vercel AI SDK.

Actor definitions and queues (src/actors.ts)
Frontend orchestration (frontend/App.tsx)
Server entry point (src/server.ts)

Resources

Read more about queues, run handlers, state, and events.

License

MIT