cr

[arthrod]

User description

Checklist

• yarn typecheck
• yarn lint:fix
• yarn test
• yarn brl
• yarn changeset
• ui changelog

---

PR Type

Bug fix, Documentation

---

Description

• Removed max-w-[700px] max-width constraint from the aiChat variant across multiple editor components

• Allows the AIChat assistant input to expand to full available width when the panel is expanded

• Updated changelog documentation to reflect the fix (version build(deps-dev): bump @storybook/addon-storysource from 5.3.0-beta.31 to 5.3.0-rc.0 udecode/plate#28.3, January 20)

• Changes applied consistently across all editor implementations: main registry, plate-template, and plate-playground-template

---

Diagram Walkthrough

flowchart LR
  A["aiChat variant<br/>with max-w-[700px]"] -- "Remove constraint" --> B["aiChat variant<br/>full width"]
  B --> C["Editor components<br/>updated"]
  C --> D["Changelog<br/>documented"]

Loading

File Walkthrough

	Relevant files
Documentation	2 files components-changelog-docs.json Add AIChat assistant input width fix to changelog                apps/www/public/r/components-changelog-docs.json Added new changelog entry for January 20 build(deps-dev): bump @storybook/addon-storysource from 5.3.0-beta.31 to 5.3.0-rc.0 udecode/plate#28.3 documenting AIChat assistant input width fix Updated JSON content field with the new changelog section +1/-1      changelog.mdx Add AIChat assistant input width fix to changelog                docs/components/changelog.mdx Added new changelog entry for January 20 build(deps-dev): bump @storybook/addon-storysource from 5.3.0-beta.31 to 5.3.0-rc.0 udecode/plate#28.3 documenting AIChat assistant input width fix Entry describes the fix for assistant input not expanding when panel is expanded +3/-0
Bug fix	5 files editor-static.tsx Remove max-width constraint from aiChat editor variant      templates/plate-playground-template/src/components/ui/editor-static.tsx Removed max-w-[700px] constraint from aiChat variant Allows assistant input to expand to full available width +1/-1      editor-static.tsx Remove max-width constraint from aiChat editor variant      templates/plate-template/src/components/ui/editor-static.tsx Removed max-w-[700px] constraint from aiChat variant Allows assistant input to expand to full available width +1/-1      editor-static.tsx Remove max-width constraint from aiChat editor variant      apps/www/src/registry/ui/editor-static.tsx Removed max-w-[700px] constraint from aiChat variant Allows assistant input to expand to full available width +1/-1      editor.tsx Remove max-width constraint from aiChat editor variant      templates/plate-playground-template/src/components/ui/editor.tsx Removed max-w-[700px] constraint from aiChat variant Allows assistant input to expand to full available width +1/-1      editor.tsx Remove max-width constraint from aiChat editor variant      templates/plate-template/src/components/ui/editor.tsx Removed max-w-[700px] constraint from aiChat variant Allows assistant input to expand to full available width +1/-1
Enhancement	1 files editor.json Remove max-width constraint from aiChat editor variant      apps/www/public/r/editor.json Removed max-w-[700px] constraint from aiChat variant in editor.tsx content Removed max-w-[700px] constraint from aiChat variant in editor-static.tsx content Both changes allow the aiChat editor variant to expand to full available width +2/-2
Additional files	2 files tailwind.css +1/-1      editor.tsx +1/-1

---

[sourcery-ai]

Sorry @arthrod, your pull request is larger than the review limit of 150000 diff characters

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[gemini-code-assist]

Summary of Changes

Hello @arthrod, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request resolves a UI issue where the AI chat assistant's input field was not expanding as expected due to a maximum width constraint. The fix involves removing this constraint from the relevant editor component styles, ensuring the input can now dynamically adjust its width. This change is also reflected in the project's changelog documentation.

Highlights

• AI Chat Input Width Fix: The aiChat variant in editor components no longer has a max-w-[700px] constraint, allowing the assistant input field to expand properly.
• Changelog Update: A new entry for January 20, 2026, has been added to the components changelog, documenting the AI Chat input width fix.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[qodo-code-review]

ⓘ Your approaching your monthly quota for Qodo. Upgrade your plan

PR Compliance Guide 🔍

Below is a summary of compliance checks for this PR:

Security Compliance
🟢	No security concerns identified No security vulnerabilities detected by AI analysis. Human verification advised for critical code.
Ticket Compliance
⚪	🎫 No ticket provided Create ticket/issue
Codebase Duplication Compliance
⚪	Codebase context is not defined Follow the guide to enable codebase context checks.
Custom Compliance
⚪	Consistent Naming Conventions Objective: All new variables, functions, and classes must follow the project's established naming standards Status: 🏷️ Missing diff context: Several additional modified TS/TSX files are listed but not included in the provided diff, so new identifiers cannot be fully verified for naming convention compliance. Referred Code 'use client';
	No Dead or Commented-Out Code Objective: Keep the codebase clean by ensuring all submitted code is active and necessary Status: Missing diff context: Additional modified files are not shown in the diff, preventing verification that no dead or commented-out code was introduced there. Referred Code 'use client';
	Robust Error Handling Objective: Ensure potential errors and edge cases are anticipated and handled gracefully throughout the code Status: Missing diff context: Because multiple changed implementation files are not included in the diff, it cannot be confirmed that any newly added logic handles error/edge cases appropriately. Referred Code 'use client';
	When relevant, utilize early return Objective: In a code snippet containing multiple logic conditions (such as 'if-else'), prefer an early return on edge cases than deep nesting Status: Missing diff context: The provided diff does not include all modified TS/TSX files, so any newly introduced conditional logic cannot be reviewed for early-return usage vs. deep nesting. Referred Code import * as React from 'react';

Compliance status legend

🟢 - Fully Compliant
🟡 - Partial Compliant
🔴 - Not Compliant
⚪ - Requires Further Human Verification
🏷️ - Compliance label

[qodo-code-review]

ⓘ Your approaching your monthly quota for Qodo. Upgrade your plan

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Impact
High-level	Consolidate duplicated component definitions The editor component definition is duplicated across multiple templates and applications. This should be refactored into a single, shared component from a common UI package to improve maintainability. Examples: templates/plate-playground-template/src/components/ui/editor.tsx [75] 'max-h-[min(70vh,320px)] w-full overflow-y-auto px-3 py-2 text-base md:text-sm', apps/www/src/registry/ui/editor.tsx [77] 'max-h-[min(70vh,320px)] w-full overflow-y-auto px-3 py-2 text-base md:text-sm', Solution Walkthrough: Before: // apps/www/src/registry/ui/editor.tsx const editorVariants = cva({ variants: { aiChat: '... max-w-[700px] ...', // Change applied here // ... } }); // templates/plate-playground-template/src/components/ui/editor.tsx const editorVariants = cva({ variants: { aiChat: '... max-w-[700px] ...', // And also applied here // ... } }); // ... and other identical files After: // packages/shared-ui/src/editor.tsx (New shared component) const editorVariants = cva({ variants: { aiChat: '...', // Change applied once // ... } }); export const Editor = ...; // apps/www/src/registry/ui/editor.tsx export { Editor } from '@packages/shared-ui/editor'; // Import from shared location // templates/plate-playground-template/src/components/ui/editor.tsx export { Editor } from '@packages/shared-ui/editor'; // Import from shared location Suggestion importance[1-10]: 9 __ Why: The suggestion correctly identifies a significant architectural issue of code duplication, which this PR's repetitive changes across multiple files perfectly illustrates, and addressing it would greatly improve project maintainability.	High
General	Explicitly remove max-width constraint Add the max-w-none utility class to the aiChat variant to explicitly override any inherited max-width constraints. src/registry/ui/editor.tsx [76-77] aiChat: - 'max-h-[min(70vh,320px)] w-full overflow-y-auto px-3 py-2 text-base md:text-sm', + 'max-h-[min(70vh,320px)] w-full max-w-none overflow-y-auto px-3 py-2 text-base md:text-sm', [To ensure code accuracy, apply this suggestion manually] Suggestion importance[1-10]: 5 __ Why: The suggestion to add max-w-none is a good defensive practice to ensure no max-width is applied, but the PR already achieves the intended outcome by removing max-w-[700px]. This change offers a minor robustness improvement.	Low
More

[gemini-code-assist]

Code Review

This pull request addresses a UI bug by removing the max-w-[700px] constraint from the aiChat variant across multiple editor components. This change allows the AIChat assistant input to correctly expand to the full available width when its containing panel is expanded. The fix has been consistently applied to all relevant editor implementations, including the main registry, plate-template, and plate-playground-template. Additionally, the changelog has been updated to document this fix. The changes are straightforward and correctly implemented. Great work!

[qodo-code-review]

ⓘ Your approaching your monthly quota for Qodo. Upgrade your plan

Code Review by Qodo

🐞 Bugs (1) 📘 Rule violations (0) 📎 Requirement gaps (0)

1. Changelog wording vague 🐞 Bug ✓ Correctness

Description

• The changelog claims an “assistant input width” fix, but in this codebase the aiChat editor
  variant is used to render the last assistant message content preview via AIChatEditor (not the
  command input field).
• This can mislead readers about what actually changed (a max-width constraint removal on the
  rendered assistant content/editor surface), making it harder to verify the fix or debug similar UI
  width issues.

Code

docs/components/changelog.mdx[R13-14]

+### January 20 #28.3
+- **AIChat**: Fixed assistant input width not expanding when panel is expanded

Evidence

The changelog entry describes an “assistant input” width fix, but the assistant content shown in the
AI menu is derived from the last assistant message and rendered through AIChatEditor using
EditorStatic with variant="aiChat". This indicates the relevant surface is the assistant
message/editor rendering, not the command input field.

docs/components/changelog.mdx[13-14]
apps/www/src/registry/ui/ai-menu.tsx[85-88]
apps/www/src/registry/ui/ai-menu.tsx[199-203]
apps/www/src/registry/ui/ai-chat-editor.tsx[12-24]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The changelog entry for Jan 20 (#28.3) states that the "assistant input width" was fixed, but in this codebase the `aiChat` editor variant is used to render the assistant message content preview (via `AIChatEditor`). This makes the changelog wording ambiguous/misleading.

## Issue Context
In `AIMenu`, `content` is taken from `useLastAssistantMessage()` and rendered by `AIChatEditor`, which uses `EditorStatic variant="aiChat"`.

## Fix Focus Areas
- docs/components/changelog.mdx[13-14]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

ⓘ The new review experience is currently in Beta. Learn more