refactor(frontend): remove legacy max-budget settings control - #213
Merged
Conversation
Co-authored-by: openhands <openhands@all-hands.dev>
6 tasks
6 tasks
saurya
marked this pull request as ready for review
August 25, 2026 01:25
malhotra5
approved these changes
Aug 27, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
HUMAN:
AGENT:
OpenHands
Why
The max-budget-per-conversation input is a legacy control shown only when
v1_enabledis false. Conversation creation now uses V1 regardless of this setting, so the control and its form plumbing are obsolete.Summary
Issue Number
N/A
How to Test
cd frontend && npm test -- __tests__/routes/app-settings.test.tsx __tests__/utils/settings-utils.test.tscd frontend && npm run lintcd frontend && npm run buildpre-commit run --config ./dev_config/python/.pre-commit-config.yamlVideo/Screenshots
Not included; this removes a control reachable only through legacy false settings.
Type
Notes
This is the first PR in a three-PR stack. Follow-ups remove frontend
v1_enabledgates, then the remaining compatibility surface.This PR was created by an AI agent (OpenHands) on behalf of the user.
Enterprise server image for this PR: