chore(site): rivet inspector button blog

[NicholasKissel]

No description provided.

[railway-app]

🚅 Deployed to the rivet-pr-3929 environment in rivet-frontend

Service	Status	Web	Updated (UTC)
website	✅ Success (View Logs)	Web	Jan 16, 2026 at 2:56 am
frontend-inspector	✅ Success (View Logs)	Web	Jan 16, 2026 at 2:54 am
frontend-cloud	✅ Success (View Logs)	Web	Jan 16, 2026 at 2:54 am

[NicholasKissel]

• chore(site): rivet inspector button blog #3929 👈 (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.

[claude]

PR Review: Inspector Button Blog Post

Overall Assessment

This is a small, straightforward blog post addition announcing the Inspector button feature. The content is clean and follows the existing blog post structure.

✅ Strengths

1. Proper Structure: Follows the established frontmatter format with author, published date, category, and keywords
2. Clear Content: Concise announcement with a bulleted list of features
3. Good Image: The accompanying image is professional and clearly shows the "Open Inspector" button
4. Consistent Formatting: Matches the style of other changelog posts in the repository

📝 Minor Observations

1. Date Format Inconsistency: I noticed the folder uses 2026-01-13 but there's an existing post at 2025-1-12-rivet-inspector (note the single digit month). While your format is more standard, the repository has mixed formats in folder names.

2. Content Depth: This is very brief compared to some other changelog posts. Consider adding:

   • A brief sentence about where to find the button (e.g., "in the local development toolbar" or "in the Rivet CLI")
   • A link to documentation if available
   • An example use case or workflow

3. Related Content: There's a previous post about Rivet Inspector launch (2025-1-12-rivet-inspector). You might want to cross-reference it or explain how this button relates to the Inspector that was previously launched.

4. Keywords: The keywords look appropriate, though you might consider adding "CLI" or "Button" if those are relevant to the feature.

🔍 Content Suggestions (Optional)

Consider expanding slightly to match the depth of similar changelog posts:

# Rivet Inspector Button

We've added an Inspector button to your local development environment. Click it to instantly open the Rivet Inspector and view:
- Actor state
- Logs  
- Connections
- Configuration

The button appears in the [specific location] when running Rivet locally, providing quick access to debugging tools without leaving your terminal.

[Optional: Learn more about the Rivet Inspector in our [launch announcement](/posts/2025-1-12-rivet-inspector)]

✅ Recommendation

Approve with optional enhancements. The PR is ready to merge as-is. The suggestions above are minor enhancements that would make the post more informative but are not blockers.

---

Note: This is a documentation-only change with no code modifications, so no concerns regarding bugs, performance, security, or test coverage.

[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@3929

@rivetkit/db

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

@rivetkit/framework-base

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

@rivetkit/next-js

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

@rivetkit/react

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

rivetkit

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

@rivetkit/sql-loader

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

@rivetkit/virtual-websocket

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/virtual-websocket@3929

@rivetkit/engine-runner

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

@rivetkit/engine-runner-protocol

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

commit: 17da3f5

[graphite-app]

Merge activity

• Jan 16, 2:56 AM UTC: NicholasKissel added this pull request to the Graphite merge queue.
• Jan 16, 2:57 AM UTC: CI is running for this pull request on a draft pull request (#3930) due to your merge queue CI optimization settings.
• Jan 16, 2:58 AM UTC: Merged by the Graphite merge queue via draft PR: #3930.