Skip to content

docs: keep multi-gateway Simple-mode profile rail wording aligned - #127380

Closed
kvnloo wants to merge 1 commit into
NousResearch:mainfrom
kvnloo:salvage/docs-simple-profile-rail-20260929
Closed

kvnloo wants to merge 1 commit into
NousResearch:mainfrom
kvnloo:salvage/docs-simple-profile-rail-20260929

Conversation

@kvnloo

@kvnloo kvnloo commented Sep 29, 2026

Copy link
Copy Markdown

What does this PR do?

Aligns website/docs/user-guide/desktop.md with the multi-gateway Simple-mode policy change: the profile rail now stays when there is more than one profile or more than one registered gateway, since with the statusbar hidden it is the only remaining way to switch profiles or gateways. The previous wording ("With more than one profile the profile rail stays") only covered the profile case and contradicted the updated profileRailVisible policy (profileCount > 1 || connectionCount > 1) and the sibling multi-connection-desktop.md doc updated in the same commit.

Related Issue

Fixes #

Type of Change

  • 🐛 Bug fix (non-breaking change that fixes an issue)
  • ✨ New feature (non-breaking change that adds functionality)
  • 🔒 Security fix
  • 📝 Documentation update
  • ✅ Tests (adding or improving test coverage)
  • ♻️ Refactor (no behavior change)
  • 🎯 New skill (bundled or hub)

Changes Made

  • website/docs/user-guide/desktop.md:144 — "With more than one profile the profile rail stays" -> "With more than one profile or gateway the profile rail stays", matching the profileRailVisible Simple-mode policy and multi-connection-desktop.md.

How to Test

  1. Open website/docs/user-guide/desktop.md around line 144; the profile-rail sentence now reads "With more than one profile or gateway …".
  2. Cross-check against apps/desktop/src/store/interface-mode.ts (profileRailVisible -> profileCount > 1 || connectionCount > 1) and website/docs/user-guide/multi-connection-desktop.md (line ~257), which describe the same behaviour.

Checklist

Code

  • I've read the Contributing Guide
  • My commit messages follow Conventional Commits (fix(scope):, feat(scope):, etc.)
  • I searched for existing PRs to make sure this isn't a duplicate
  • My PR contains only changes related to this fix/feature (no unrelated commits)
  • I've run pytest tests/ -q and all tests pass
  • I've added tests for my changes (required for bug fixes, strongly encouraged for features)
  • I've tested on my platform: N/A (docs-only)

Documentation & Housekeeping

  • I've updated relevant documentation (README, docs/, docstrings) — or N/A
  • I've updated cli-config.yaml.example if I added/changed config keys — or N/A
  • I've updated CONTRIBUTING.md or AGENTS.md if I changed architecture or workflows — or N/A
  • I've considered cross-platform impact (Windows, macOS) per the compatibility guide — or N/A
  • I've updated tool descriptions/schemas if I changed tool behavior — or N/A

For New Skills

N/A

Screenshots / Logs

A multi-gateway install with only the default profile would, per the old wording, expect the profile rail to disappear in Simple mode — but with the statusbar hidden the rail is the only way to switch gateways, so it stays. The corrected sentence prevents that misconception.

Introduced by commit 7eb0ae1 (@OutThisLife, #119727)


Doc Drift PRs can be configured here.

@alt-glitch alt-glitch added type/docs Documentation improvements P3 Low — cosmetic, nice to have comp/desktop Electron desktop app (apps/desktop/*) labels Sep 29, 2026
@kvnloo kvnloo closed this Sep 30, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

comp/desktop Electron desktop app (apps/desktop/*) P3 Low — cosmetic, nice to have type/docs Documentation improvements

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants