chore(site): local inspector blog

[NicholasKissel]

No description provided.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
rivet-site	Ready	Preview	Comment	Dec 5, 2025 7:06pm

3 Skipped Deployments

Project	Deployment	Preview	Comments	Updated (UTC)
rivet-cloud	Ignored			Dec 5, 2025 7:06pm
rivet-inspector	Ignored	Preview		Dec 5, 2025 7:06pm
rivetkit-serverless	Skipped			Dec 5, 2025 7:06pm

[NicholasKissel]

• chore(site): local inspector blog #3593 👈 (View in Graphite)
• main

---

How to use the Graphite Merge Queue

Add the label merge-queue to this PR to add it to the merge queue.

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

This stack of pull requests is managed by Graphite. Learn more about stacking.

[pkg-pr-new]

More templates

• example-ai-agent
• example-ai-and-user-generated-actors-freestyle
• chat-room
• example-cloudflare-workers
• example-cloudflare-workers-hono
• example-cloudflare-workers-inline-client
• example-counter
• example-counter-next-js
• example-counter-serverless
• example-cursors
• example-cursors-raw-websocket
• example-deno
• example-sqlite
• example-elysia
• example-express
• example-hono
• example-hono-bun
• example-hono-react
• example-kitchen-sink
• example-next-js
• quickstart-actions
• quickstart-cross-actor-actions
• quickstart-multi-region
• quickstart-raw-websockets
• quickstart-realtime
• quickstart-scheduling
• quickstart-state
• example-raw-fetch-handler
• example-raw-websocket-handler
• example-raw-websocket-handler-proxy
• example-react
• starter
• example-stream
• example-trpc

@rivetkit/cloudflare-workers

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/cloudflare-workers@3593

@rivetkit/db

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/db@3593

@rivetkit/framework-base

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/framework-base@3593

@rivetkit/next-js

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/next-js@3593

@rivetkit/react

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/react@3593

rivetkit

pnpm add https://pkg.pr.new/rivet-dev/rivet/rivetkit@3593

@rivetkit/sql-loader

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/sql-loader@3593

@rivetkit/engine-runner

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/engine-runner@3593

@rivetkit/engine-runner-protocol

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/engine-runner-protocol@3593

commit: 81e5ebe

[claude]

Code Review: Local Inspector Blog Post

Thanks for putting together this blog post! Overall, the content is well-written and engaging. I've identified several issues that should be addressed before publishing.

---

🔴 Critical Issues

1. Confusing/Contradictory Opening (Line 12)

Issue: The phrase "launching the inspector button for the Rivet Local Inspector" is awkward and unclear.

Suggested fix:

- Today, we are launching the inspector button for the **Rivet Local Inspector**.
+ Today, we are launching the **Rivet Local Inspector**.

2. Duplicate Inspector Post Already Exists

Issue: There's already an inspector blog post at website/src/posts/2025-1-12-rivet-inspector/page.mdx (published January 12, 2025). This creates confusion:

• Are these two different inspector features?
• Is this an update to the existing inspector?
• Should the old post be deprecated?

Recommendation:

• If this is an updated/improved version, the title should reflect that (e.g., "Inspector 2.0" or "Major Inspector Updates")
• Add a note referencing the original inspector launch
• Consider whether the old post should link to this new one

---

⚠️ High Priority Issues

3. Version Mismatch (Line 71)

Issue: The post claims the inspector is available in "Rivet v2.1.0" but the Zero-Config Setup section implies it's already built into the latest rivetkit.

Suggested fix: Verify the actual version number and ensure consistency. If it's already available, consider:

The Local Inspector is included in **rivetkit v2.1.0+**.

4. Broken Documentation Link (Line 74)

Issue: The link https://rivet.dev/docs/inspector may not exist yet.

Recommendation: Verify this URL works before publishing, or update to the correct documentation path.

5. Actor Capitalization Inconsistency

Issue: Per CLAUDE.md guidelines, "Rivet Actors" should be capitalized when referring to the Rivet feature, but "actor" (lowercase) for generic usage. The post mostly follows this, but should be verified throughout.

Current usage appears correct, but double-check lines 16, 18, 26, 30, 34, 53.

---

📝 Medium Priority Issues

6. Vague Feature Description (Line 8)

Issue: "built with new features and improvements" is generic marketing speak.

Suggested improvement:

- The new Rivet Inspector is built with new features and improvements to improve developer velocity.
+ The new Rivet Inspector includes live state editing, event timelines, and an integrated REPL to streamline your development workflow.

7. Missing Context on "Now" (Line 39)

Issue: "The Inspector now includes" implies this is an update, but the opening suggests it's a new launch.

Suggested fix: Be consistent about whether this is new or updated. If it's updated:

### 3. Integrated REPL

- The Inspector now includes a context-aware REPL.
+ We've added a context-aware REPL.

8. Code Example Could Be More Realistic (Lines 44-48)

Issue: The REPL example shows a chat room with exactly 42 messages, which feels contrived.

Suggested improvement:

// Call actions directly from the Inspector console
> chatRoom.connect("user_123")
> chatRoom.call("sendMessage", { text: "Hello from Inspector!" })
< Action dispatched: "sendMessage"
< State updated: messages.length is now 5

---

💡 Nice-to-Have Improvements

9. Add Visual Context

Observation: There's an image.png included in the PR. Consider:

• Explicitly referencing the image in the markdown (it's not currently embedded)
• Adding captions to explain what the screenshot shows
• Possibly adding more screenshots for each major feature

10. Consistency with Other Blog Posts

Observation: Comparing to 2025-11-24-introducing-live-websocket-migration-hibernation/page.mdx:

• That post includes code examples in <CodeGroup> tags with separate Actor/Client files
• Consider whether the REPL example should follow similar formatting

11. Missing Information

Consider adding:

• Performance/resource requirements for running the inspector
• Any security considerations (e.g., should it only run on localhost?)
• Comparison with browser DevTools or other similar tools

---

✅ What's Working Well

1. Clear structure - The problem/solution format is effective
2. Good feature breakdown - Four numbered features are easy to scan
3. Proper noun capitalization - Mostly follows CLAUDE.md guidelines for "Rivet Actors"
4. Engaging tone - Conversational without being overly casual
5. Good use of metaphors - "X-ray vision", "treats your backend like a frontend"

---

📋 Pre-Publish Checklist

• Resolve the duplicate inspector post issue
• Verify version number (v2.1.0)
• Verify documentation link works
• Fix the awkward opening sentence
• Consider embedding the included image
• Test the inspector URL (http://localhost:6420/_inspector)
• Verify Discord link works

---

Summary

This is a strong blog post that effectively communicates the value of the Local Inspector. The main concerns are around clarity (is this new or updated?) and technical accuracy (version numbers, links). Once those are addressed, this should be ready to publish.

Overall Assessment: Approve with changes required ✏️