wip: kitchen sink agentic loop finish

[NathanFlurry]

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

[NathanFlurry]

• fix(pegboard): align drain grace defaults with stop threshold #4958 : 2 dependent PRs (#4960 , #4966 )
• fix(rivetkit): preserve bridge error messages #4959
• fix(rivetkit): fire abort signal on shutdown finalize #4957
• fix(rivetkit): use startup kv preload #4956
• fix(client): flatten skipReadyWait option #4955
• ci(publish): add manual preview publish flow #4954
• fix(depot): add ltx decode diagnostics #4953
• fix(universaldb): preserve plain set values #4952
• fix(universaldb): align versionstamp operand encoding #4951
• fix(rivetkit): export database provider types #4950
• wip: kitchen sink agentic loop finish #4949 👈 (View in Graphite)
• chore(rivetkit): note duplicate admission logic #4948
• test(rivetkit): cover bypass fetch header forwarding #4947
• feat(kitchen-sink): add actor probe controls #4946
• fix(gateway): split actor response wait errors #4945
• fix(guard): handle bypass preflight before query parse #4944
• feat(kitchen-sink): add mock agent event log copy #4943
• fix(kitchen-sink): default mock agent to local endpoint #4942
• test(rivetkit): enable driver lifecycle regressions #4941
• test(rivetkit): verify cached websocket db refs exceed grace #4940
• fix(rivetkit-core): keep sleeping actors reachable during grace #4939
• test(rivetkit): cover async websocket close db access #4938
• fix(rivetkit): keep actors awake until keepAwake work finishes #4937
• fix(rivetkit): persist native onSleep state on errors #4936
• fix(rivetkit-core): allow dispatch during sleep grace #4935
• fix(rivetkit): make duplicate sleep requests idempotent #4934
• main

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

[github-actions]

Preview packages published to npm

Install with:

npm install rivetkit@pr-4949

All packages published as 0.0.0-pr.4949.5f0637c with tag pr-4949.

Engine binary is shipped via @rivetkit/engine-cli on linux-x64-musl, linux-arm64-musl, darwin-x64, and darwin-arm64. Windows users should use the release installer or set RIVET_ENGINE_BINARY.

Docker images:

docker pull rivetdev/engine:slim-5f0637c
docker pull rivetdev/engine:full-5f0637c

Individual packages

npm install rivetkit@pr-4949
npm install @rivetkit/react@pr-4949
npm install @rivetkit/rivetkit-napi@pr-4949
npm install @rivetkit/workflow-engine@pr-4949

[claude]

Code Review: kitchen-sink agentic loop finish

Note: This is a draft PR — feedback is provided for early guidance.

Overview

This PR modifies the examples/kitchen-sink dev scripts to:

1. Hardcode VITE_RIVET_ENDPOINT=http://127.0.0.1:6420 into the dev script.
2. Add a third concurrent process to dev:serverless that polls until the server is ready.
3. Introduce a new inline dev:serverless:configure script that polls /api/rivet/metadata for up to 2 minutes before erroring.

---

Issues

Silent error swallowing (dev:serverless:configure)

The catch {} in the polling loop discards all network errors silently. During development, swallowed errors (e.g., DNS failures, ECONNREFUSED with a mismatched port) make it impossible to diagnose why the poller is not making progress. Recommend at minimum logging the caught error:

} catch (err) { console.log('serverless configuration error: ' + err.message); }

Inline script is unreadable

The entire dev:serverless:configure value is a single minified line. This is hard to read, hard to diff, and hard to maintain. Extract it to scripts/wait-for-serverless.mjs (or similar) and reference it as node scripts/wait-for-serverless.mjs. The repo already uses scripts/ for similar helpers.

Asymmetric VITE_RIVET_ENDPOINT between dev and dev:serverless

The dev script now sets VITE_RIVET_ENDPOINT=http://127.0.0.1:6420, but dev:serverless does not. If the serverless mode also needs Vite to point to a specific endpoint, this is likely an omission. If not, a comment explaining the difference would help.

Hardcoded port 6420

The endpoint http://127.0.0.1:6420 is hardcoded with no comment explaining what service owns this port or why it is fixed. If it is the engine's default, call that out. Consider making it overridable via an env var or documenting it in a .env.example.

---

Minor Notes

• The polling uses sleep(1000) in a retry/backoff loop, which is acceptable (retry/reconnect backoff is an explicitly listed valid use case).
• The 120-iteration / 2-minute timeout is a reasonable upper bound for a local dev server.
• concurrently -n server,vite,configure label count now matches the command count.

---

Summary

The intent is clear and the overall approach is sound. Main asks before merging:

1. Extract the inline configure script to a dedicated file.
2. Log (do not silently swallow) caught errors in the polling loop.
3. Clarify whether dev:serverless also needs VITE_RIVET_ENDPOINT, and document the 6420 port.