Skip to content

Re-tab /settings to the approved IA: nine standard-named nodes, search front door, working set, presets #1303

Description

@santoshkumarradha

Split from #1295 (closed as superseded); this is the tracking issue for the reorganization. The approved tree, its naming sources and its placement rules are the hierarchy comment on #1295.

Children:

The shape

  • Nine standard-named nodes, depth two: Models & Providers, Permissions, Budget, Context & Memory, Tasks, Workspace, Appearance, Connections, General. Subgroups only where scanning would fail (Permissions, Models & Providers, General); every other node flat.
  • The panel opens on search; tabs become facets. Default view is the working set (about a dozen rows); every row stays reachable behind search and an all-rows toggle, with totality enforced by the chrome_test pattern that already fails the build when a registry key loses its tab.
  • Presets as the first row of Permissions: safe / balanced / yolo writing the trust bundle (the models.crew word is the working precedent: one word writes five tier rows).
  • The /autonomy rules live under Permissions as "Questions while you are away"; the ssh quartet moves to General > System; the countdowns inline under the rows they govern.

Evidence: audit-notes/settings-inventory.md (all 77 rows on this branch, 81 on dev, per-tab tables, the twelve label mismatches, and the naming collisions the re-tab dissolves) on feat/1089-custom-connections.

—

Co-Authored-By: codeaf agentfield-bot@users.noreply.github.com

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

area:chatThe v3 surface a person sits in front of (internal/tui3)epicA parent issue whose children are the workfeatureWork that adds a capability; developers break it into tasks

Type

No type

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions