Skip to content

Settings page - UX and functionality comments #23

Description

@halr9000

Sharing some UX comments on the settings page:

Inconsistent styles

  • Tab names and case don't match most of the section names. These should be identical for clarity. (eg "Agent connection" vs "MCP CONNECTION".)
  • Inconsistent placement of headers inside vs outside of boxes. Eg. "Monthly budget" vs "MCP CONNECTION".
  • Gradient appears on box top border on some but not all sections. (Honestly, I'd lose this type of gradient entirely, it's distracting for no reason.)
  • Several other examples on this page where header levels and text styles are used inconsistently between sections.

MCP Connection

The text is very duplicative, eg "ready to connect" appears 3x. "Read-only" 2x. Multiple other terms and phrases to indicate that the MCP is private and makes no changes are also repetitive. Even the "MCP" pills after Codex and Claude are redundant in this context IMHO. https://github.com/petergyang/no-ai-slop is your friend.

With regards to "private by default" and the folded text, I'd suggest that settings should only show settings, and concepts and guidance don't belong on the page at all. Hover text is always good, but anything beyond a brief phrase or sentence should be folded or a link to docs. Or to the Learn section if you were to expand that to explain concepts.

Image

Compare to a randomly selected Claude settings screen (and this one is wordier than most tbh). I've unfolded the "how we protect your data" section. Lots of links,

Image

Cost Estimates transparency

Consider adding a subheading that indicates the source and date these cost figures were last updated. It's not immediately clear when or why one should need to edit these. If the source is from a vendor's own website and moderately recent, that should lead most users to not bother, which is a good thing. Only people who are using other providers you don't include OOtB, or know they have lower rates will want to tweak these.

User language signals

I think this section deserves a link or folding section with detail about what this is for. Someone coming to settings before going through all of the app screens (ie, me) has no clue why the page is swearing at the user. Also:

  • "20 phrases" count seems to serve no purpose
  • "machine wide" is redundant as everything in the app would be? (I just found this term in another section on this page. No-ai-slop or similar prompting would help to catch these.)
  • "Up to 64 per group" likewise isn't adding value. If there's a hard limit, can't you just do the math for the user under each text box?

Cost estimates

I would review all text and styles for clarity and redundancy. I'm seeing major case of tense disagreement between terms like: all history, means now, past time, since then, from now. Also, all those buttons are...weird. Not clear to me what save vs default does, and I can't imagine someone wanting to have line-item granularity on whatever they do. Seems more of an all at once thing at most. Button label styles are inconsistent, (default looks inactive, but isn't). Also, those with narrow browser widths will see overflow like this:

Image

Update frequency

Checking every 10 min seems very excessive. How about daily? Can just expose the number if someone wants it to happen more often.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions