fix: remove useless config params

[MasterPtato]

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

[railway-app]

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

Service	Status	Web	Updated (UTC)
website	😴 Sleeping (View Logs)	Web	Feb 27, 2026 at 12:11 am
frontend-inspector	😴 Sleeping (View Logs)	Web	Feb 26, 2026 at 11:52 pm
frontend-cloud	❌ Build Failed (View Logs)	Web	Feb 26, 2026 at 8:21 pm
mcp-hub	✅ Success (View Logs)	Web	Feb 26, 2026 at 8:15 pm
ladle	❌ Build Failed (View Logs)	Web	Feb 26, 2026 at 8:07 pm

[MasterPtato]

• fix: always trigger serverless ended early error #4320
• fix: remove useless config params #4319 👈 (View in Graphite)
• fix: add serverless leak fix oneoff #4318
• chore: add log for runners with no alloc idx #4316
• fix(ups): upgrade nats, fix chunking, add chunking tests #4315
• chore: fix tests #4314
• fix: various serverless bug fixes #4313
• fix(guard, runner): enforce http body size and ws msg size #4252
• fix(pegboard): add threshold parameters to runner protocol metadata #4247
• chore: get docker compose working again #4246
• fix(epoxy): make quorum sizes match paper #4234
• fix(rivetkit): stall stop handler until start completes #4192
• 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: fix: remove useless config params

Good cleanup overall — removing unused/dead config parameters reduces surface area and simplifies configuration. A few follow-up issues worth tracking (PR is already merged):

---

Bugs / Incomplete Cleanup

1. Schema not updated for the runner_http_max_response_body_size → runner_max_response_payload_body_size rename

The Rust struct field was renamed in pegboard.rs, but config-schema.json shows no corresponding change (no removal of the old name, no addition of the new name). The schema is out of sync with the Rust struct. Any user setting runner_max_response_payload_body_size in their config will have it silently ignored.

The schema should be regenerated to reflect the rename.

2. Dead field: gateway_http_max_request_body_size has no getter

Pegboard::gateway_http_max_request_body_size still exists as a public struct field and in the config schema, but its getter was removed and it is no longer consumed anywhere. Setting this field in a config file has no effect. Either remove the field entirely or restore enforcement.

---

Minor Issues

3. Misleading function name for response body limiting

In proxy_service.rs (around line 803–812), the response body buffer limit is enforced using self.state.config.guard().http_max_request_body_size(). This uses a request-body-named getter to limit a response body. While the 20 MiB default is the same right now, the naming will cause confusion if the limits ever need to diverge.

4. Potentially breaking default limit reduction

Guard::http_max_request_body_size default dropped from 256 MiB → 20 MiB, and runner_max_response_payload_body_size dropped from 128 MiB → 20 MiB. These are significant reductions that could silently break actors processing larger payloads. The PR description has the "Breaking change" box unchecked — worth confirming this is intentional and noting it in release notes.

---

Summary

Issue	Severity
Schema not updated for field rename	Bug
Dead gateway_http_max_request_body_size field (no getter, not enforced)	Incomplete cleanup
http_max_request_body_size() used to limit response body size	Minor / confusing naming
Undocumented breaking default limit reduction (256→20 MiB, 128→20 MiB)	Worth noting

[pkg-pr-new]

More templates

• actor-actions
• actor-actions-vercel
• ai-agent
• ai-agent-vercel
• example-ai-and-user-generated-actors-freestyle
• chat-room
• chat-room-vercel
• example-cloudflare-workers
• example-cloudflare-workers-hono
• collaborative-document
• collaborative-document-vercel
• cross-actor-actions
• cross-actor-actions-vercel
• example-cursors
• example-cursors-raw-websocket
• example-cursors-raw-websocket-vercel
• example-cursors-vercel
• custom-serverless
• example-elysia
• example-experimental-durable-streams-ai-agent
• example-experimental-durable-streams-ai-agent-vercel
• geo-distributed-database
• geo-distributed-database-vercel
• hello-world
• hello-world-vercel
• example-hono
• hono-react
• hono-react-vercel
• example-kitchen-sink
• example-kitchen-sink-vercel
• multi-region-vercel
• multiplayer-game
• example-multiplayer-game-patterns
• example-multiplayer-game-patterns-vercel
• multiplayer-game-vercel
• native-websockets
• native-websockets-vercel
• next-js
• per-tenant-database
• per-tenant-database-vercel
• example-raw-fetch-handler
• example-raw-fetch-handler-vercel
• example-raw-websocket-handler
• example-raw-websocket-handler-proxy
• example-raw-websocket-handler-proxy-vercel
• example-raw-websocket-handler-vercel
• example-react
• example-react-vercel
• sandbox
• sandbox-coding-agent
• sandbox-coding-agent-vercel
• sandbox-vercel
• scheduling
• scheduling-vercel
• example-sqlite-drizzle
• example-sqlite-raw
• state
• state-vercel
• example-stream
• example-stream-vercel
• example-trpc

@rivetkit/cloudflare-workers

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

@rivetkit/framework-base

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

@rivetkit/next-js

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

@rivetkit/react

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

rivetkit

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

@rivetkit/sql-loader

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

@rivetkit/sqlite-vfs

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/sqlite-vfs@4319

@rivetkit/traces

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

@rivetkit/workflow-engine

pnpm add https://pkg.pr.new/rivet-dev/rivet/@rivetkit/workflow-engine@4319

@rivetkit/virtual-websocket

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

@rivetkit/engine-runner

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

@rivetkit/engine-runner-protocol

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

commit: 2f068b7