Remove deprecated response_type parameter from query settings UI

[danielaskdd]

Remove response_type Parameter from Query Settings UI

Summary

The query parameter response_type is deprecated, as it can no longer effectively control the query output. Output behavior can now be guided through the user_prompt. In the future, full output customization will be achieved by modifying the prompt templates.

This PR removes the response_type parameter from the query settings interface and fixes it to "Multiple Paragraphs" for all queries. The parameter is no longer configurable by users through the UI.

Changes Made

1. Frontend UI (lightrag_webui/src/components/retrieval/QuerySettings.tsx)

• Removed the entire "Response Format" section including:
  • Select dropdown for choosing response format
  • Reset button for response_type
  • Tooltip and label components
• Removed response_type from defaultValues object

2. Query Execution (lightrag_webui/src/features/RetrievalTesting.tsx)

• Hardcoded response_type: 'Multiple Paragraphs' in the queryParams object
• All queries now consistently use "Multiple Paragraphs" format regardless of stored settings

3. Settings Store (lightrag_webui/src/stores/settings.ts)

• Removed response_type: 'Multiple Paragraphs' from initial querySettings state
• Incremented storage version from 18 to 19
• Added migration for version 19 that automatically removes deprecated response_type from localStorage

Migration Strategy

The implementation includes automatic migration for existing users:

• Users with response_type in localStorage will have it automatically removed on next app load
• Storage version bump ensures migration runs exactly once
• No manual intervention required from users

Testing

• ✅ Frontend builds successfully with no compilation errors
• ✅ Linting passes with no warnings or errors
• ✅ All queries will use "Multiple Paragraphs" format consistently
• ✅ No breaking changes to the API (response_type remains optional in QueryRequest interface)

Breaking Changes

None - This is a UI-only change. The backend API still accepts response_type as an optional parameter, ensuring backward compatibility with other clients.

[danielaskdd]

@codex review

[chatgpt-codex-connector]

Codex Review: Didn't find any major issues. Hooray!

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".