Skip to content

🤖 fix: restyle section headers and rename section chat copy#2985

Open
jaaydenh wants to merge 5 commits intomainfrom
sections-wpd8
Open

🤖 fix: restyle section headers and rename section chat copy#2985
jaaydenh wants to merge 5 commits intomainfrom
sections-wpd8

Conversation

@jaaydenh
Copy link
Copy Markdown
Contributor

Summary

Restyle sidebar section headers to remove the tinted background and left color bar, replacing them with colored section-name text and left indentation. Also rename section-related copy from "workspace" to "chat".

Background

The section header design previously used a subtle background tint and a left color bar to indicate the section color. The new design simplifies this by applying the section color directly to the section name text, removing visual clutter. The "workspace" terminology in section-specific UI is also updated to "chat" for consistency with the product direction.

Implementation

SectionHeader.tsx:

  • Removed backgroundColor, borderLeftWidth, borderLeftColor inline styles from the header container
  • Added pl-3 (0.75rem) left indentation
  • Applied style={{ color: sectionColor }} to the section name text (removed text-foreground class)
  • Renamed plus button: aria-label → "New chat in section", tooltip → "New chat"

ProjectSidebar.tsx:

  • Empty-state copy: "No workspaces in this section" → "No chats in this section"

sections.test.ts:

  • Updated aria-label selector to match new string

Generated with mux • Model: anthropic:claude-opus-4-6 • Thinking: xhigh • Cost: $2.40

@jaaydenh
Copy link
Copy Markdown
Contributor Author

@codex review

@chatgpt-codex-connector
Copy link
Copy Markdown

Codex Review: Didn't find any major issues. Chef's kiss.

ℹ️ 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".

@jaaydenh
Copy link
Copy Markdown
Contributor Author

@codex review

Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 6565709055

ℹ️ 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".

Comment on lines 124 to 127
function getItemPaddingLeft(depth?: number): number {
const safeDepth = typeof depth === "number" && Number.isFinite(depth) ? Math.max(0, depth) : 0;
return 12 + Math.min(32, safeDepth) * 12;
return 8 + Math.min(32, safeDepth) * 12;
}
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P3 Badge Keep row indent baseline consistent with task-group rows

Reducing AgentListItem base left padding from 12 to 8 shifts workspace rows left, but task-group rows still use the previous baseline (TaskGroupListItem keeps 12 + depth*12). In lists that contain both task-group headers and normal workspace rows, this creates a persistent 4px horizontal misalignment between related rows and connectors, making hierarchy rendering inconsistent in grouped sections.

Useful? React with 👍 / 👎.

@jaaydenh jaaydenh self-assigned this Mar 31, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant