Summary
The model fallback transition system (resolveFallbackTransition, fallback notices, fallback state in session entries) is dead code in RemoteClaw. CLI runtimes manage their own model selection — RemoteClaw has no model fallback.
What to Remove
resolveFallbackTransition() calls and surrounding logic in agent-runner.ts:448-466
- Fallback notice building and delivery (
buildFallbackNotice, buildFallbackNoticePayload)
- Session entry fields:
fallbackNoticeSelectedModel, fallbackNoticeActiveModel, fallbackNoticeReason
fallbackProvider, fallbackModel, fallbackAttempts variables in agent-runner.ts
selectedProvider, selectedModel tracking (only used for fallback comparison)
Acceptance Criteria
-
Given a message is processed
When the agent runner executes
Then no fallback transition logic runs
-
Given the session store
When entries are written
Then no fallbackNotice* fields are present
-
pnpm check passes
-
Existing tests pass (or are updated to remove fallback assertions)
Depends On
Summary
The model fallback transition system (
resolveFallbackTransition, fallback notices, fallback state in session entries) is dead code in RemoteClaw. CLI runtimes manage their own model selection — RemoteClaw has no model fallback.What to Remove
resolveFallbackTransition()calls and surrounding logic inagent-runner.ts:448-466buildFallbackNotice,buildFallbackNoticePayload)fallbackNoticeSelectedModel,fallbackNoticeActiveModel,fallbackNoticeReasonfallbackProvider,fallbackModel,fallbackAttemptsvariables inagent-runner.tsselectedProvider,selectedModeltracking (only used for fallback comparison)Acceptance Criteria
Given a message is processed
When the agent runner executes
Then no fallback transition logic runs
Given the session store
When entries are written
Then no
fallbackNotice*fields are presentpnpm checkpassesExisting tests pass (or are updated to remove fallback assertions)
Depends On