feat(rivetkit): add per-call poolName option to getOrCreate and create

[abcxff]

No description provided.

[abcxff]

Stack for rivet-dev/rivet

• #5496 feat(rivetkit): add per-call poolName option to getOrCreate … 👈
• #5542 fix(frontend): source actor deployment logs pool from runner …
• #5540 feat(frontend): add pool selector to create actor dialog adv …
• #5541 feat(frontend): delete managed pool from compute config page
• #5499 feat(frontend): pool switcher and pool-scoped titles for log …
• main

Get stack: forklift get 5496
Push local edits: forklift submit
Merge when ready: forklift merge 5496

_{change ylosnxmq}

[claude]

Review

Clean, well-scoped feature: adds a per-call poolName override to getOrCreate/create on both the Rust client and TypeScript engine client, falling back to the client's configured pool name. Plumbing is symmetric across both languages (options struct -> query/request schema -> wire request -> gateway URL query param), and the test coverage mirrors that symmetry nicely (override + fallback cases for create, getOrCreate, and gateway_url/buildGatewayUrl on both sides).

Re-verified against the latest commit (9b3e592); the diff is unchanged from the prior review.

Findings

Nit - pre-existing dead option, adjacent to this change (Rust Client::create): rivetkit-rust/packages/client/src/client.rs create() still does let _region = opts.region; and never forwards it. RemoteManager::create_actor (and the wire-level ActorsCreateRequest) has no region field at all, so CreateOptions.region has silently had zero effect even before this PR. Not introduced here, but this PR touches the exact same CreateOptions/create() path to wire up pool_name, so it is a good opportunity to either fix or remove region from CreateOptions so the two per-call overrides do not have inconsistent behavior (pool_name works, region silently does not).

Nit - no cross-SDK parity for Swift: rivetkit-swift ActorQuery/RemoteManager only supports pool name via client config, no per-call override. Not required by CLAUDE.md (parity rules there are scoped to the runner protocol, not client SDKs), but worth a follow-up if per-call pool selection is meant to be a first-class cross-SDK feature.

Nit - empty-string override not guarded: both pool_name.unwrap_or_else(...) (Rust) and the TS poolName ?? this.#config.poolName fallback treat an explicit empty string as a valid override rather than falling back. Probably fine since this mirrors existing region/createInRegion handling, just flagging in case an empty string should be treated as unset.

Nothing blocking. Good test coverage on both the Rust (bare.rs) and TypeScript (remote-engine-client-pool-name.test.ts) sides, including the gateway-URL query-param paths in addition to the JSON body paths.

[railway-app]

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

Service	Status	Web	Updated (UTC)
kitchen-sink	😴 Sleeping (View Logs)	Web	Jul 31, 2026 at 5:30 pm
frontend-inspector	😴 Sleeping (View Logs)	Web	Jul 31, 2026 at 5:29 pm
frontend-cloud	😴 Sleeping (View Logs)	Web	Jul 31, 2026 at 5:27 pm
website	😴 Sleeping (View Logs)	Web	Jul 31, 2026 at 4:41 pm
mcp-hub	✅ Success (View Logs)	Web	Jul 31, 2026 at 4:29 pm
ladle	✅ Success (View Logs)	Web	Jul 28, 2026 at 2:51 pm