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

• actor-actions
• example-ai-agent
• example-ai-and-user-generated-actors-freestyle
• chat-room
• example-cloudflare-workers
• example-cloudflare-workers-hono
• example-cloudflare-workers-inline-client
• cross-actor-actions
• example-cursors
• example-cursors-raw-websocket
• custom-serverless
• example-sqlite
• example-elysia
• example-experimental-durable-streams-ai-agent
• hello-world
• example-hono
• hono-react
• example-kitchen-sink
• multi-region
• native-websockets
• next-js
• example-raw-fetch-handler
• example-raw-websocket-handler
• example-raw-websocket-handler-proxy
• example-react
• scheduling
• state
• 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/virtual-websocket

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/virtual-websocket@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: 06d774c

[claude]

PR Review: Local Inspector Blog Post

This PR adds a blog post announcing the new Rivet Local Inspector. Overall, the content is well-written and engaging. Below are my findings:

Issues Found

1. Incorrect Frontmatter Format (Critical)

Location: website/src/posts/2025-12-05-introducing-the-new-local-inspector/page.mdx:1-4

The frontmatter uses export statements instead of YAML frontmatter. Based on other blog posts in website/src/content/posts/, the correct format should use YAML frontmatter wrapped in --- delimiters.

Current format uses TypeScript exports, but it should follow the YAML pattern like other posts.

2. Inconsistent Date Format (Major)

Location: Filename and frontmatter

The blog post is dated 2025-12-05 (December 5, 2025), but today is 2025-01-15 (January 15, 2025). This is a future date. Should this be:

• 2024-12-05 (December 5, 2024 - past)?
• 2025-01-05 (January 5, 2025 - recent past)?

Please verify the intended publication date.

3. Incomplete Sentence (Major)

Location: page.mdx:12

The sentence "Today, we are launching the inspector button for the Rivet Local Inspector" is awkward. "Launching the inspector button" does not make sense. Should be something like:

• "Today, we are launching the Rivet Local Inspector"
• "Today, we are announcing the Rivet Local Inspector"

4. Vague Placeholder (Minor)

Location: page.mdx:12

The phrase "giving you X-ray vision into your application state" is a good metaphor but consider being more specific about what visibility the inspector provides.

5. Capitalization Inconsistency (Minor)

Location: Throughout the document

Following CLAUDE.md conventions, "Rivet Actor" should be capitalized as a proper noun when referring to the Rivet Actors feature specifically. The document correctly uses "Rivet Actors" in some places (lines 16, 26) but could be more consistent.

Content Quality

Strengths:

• Clear problem/solution structure
• Engaging tone with concrete examples
• Good use of code snippets to demonstrate features
• Comprehensive feature overview (Live State Editing, Event Timeline, REPL, Connection Topology)

Suggestions:

1. The REPL example (lines 44-48) shows a nice interaction pattern, but it would be helpful to clarify if this is actual console output or pseudocode
2. Consider adding a screenshot or reference to the included image.png in the blog post content
3. The "Available Now" section references v2.1.0, but verify this version number matches the actual release

Security and Best Practices

✅ No security concerns (informational blog post only)
✅ No code quality issues (documentation only)
✅ No performance concerns

Recommendations

1. Fix the frontmatter format to use YAML (critical for build/deployment)
2. Verify and correct the publication date
3. Fix the incomplete sentence about "launching the inspector button"
4. Consider incorporating the image that is included in the PR
5. Verify version number (v2.1.0) matches the actual release

---

Great work on documenting this feature! The writing is engaging and developer-focused. Once the frontmatter format and date issues are resolved, this will be ready to publish.