Why: The three modes have to be visible where the user sends a message.
Evidence: vitest and knip passed inside make test. A mock instance saved plan mode.
Impact: An empty mode still renders as 默认.
Refs: feature/permission-hooks
Why: The three modes have to be visible where the user sends a message.
Evidence: vitest and knip passed inside make test. A mock instance saved plan mode.
Impact: An empty mode still renders as 默认.
Refs: feature/permission-hooks
Why: Plan, default, and auto-edit have to be visible where the user sends a message, and confirmation cards need to show the arguments.
Evidence: The mode control and card detail only use existing color, radius, and type tokens.
Impact: An empty mode still renders as 默认. Confirm cards use the wait color instead of the success color.
Refs: feature/permission-hooks
Co-authored-by: Cursor <cursoragent@cursor.com>
weichen
merged commit 82d216b324 into main2026-10-03 17:06:49 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Why: The three modes have to be visible where the user sends a message.
Evidence: vitest and knip passed inside make test. A mock instance saved plan mode.
Impact: An empty mode still renders as 默认.
Refs: feature/permission-hooks