Skip to content

Hide internal system tools from company settings - #799

Merged
Y1fe1Zh0u merged 1 commit into
mainfrom
agent/hide-system-tools-company-settings
Jul 28, 2026
Merged

Hide internal system tools from company settings#799
Y1fe1Zh0u merged 1 commit into
mainfrom
agent/hide-system-tools-company-settings

Conversation

@Y1fe1Zh0u

Copy link
Copy Markdown
Collaborator

What changed

  • Stop rendering the system tool category in Company Settings.
  • Add a frontend contract test covering the render guard.

Why

Finish and other system-category entries are Runtime protocol details, not company-managed capabilities. The legacy database row can still appear in the tools response, which caused Company Settings to expose a misleading category and toggle.

Impact

Company administrators no longer see the System tools group. The underlying tools collection, displayed global count, search behavior, backend records, and Runtime behavior remain unchanged.

Validation

  • npm test — 86 passed
  • npm run build — passed

Not tested

  • Browser E2E against a deployed tenant

System-category tools are Runtime protocol details rather than tenant-configurable capabilities. Skip rendering the generated system group while leaving the underlying collection, counts, search, and backend records unchanged.\n\nConstraint: Preserve legacy database rows, Runtime behavior, and existing collection logic.\nConfidence: high\nScope-risk: narrow\nDirective: Keep system-category tools out of user-facing tool management surfaces.\nTested: npm test (86 passed); npm run build\nNot-tested: Browser E2E against a deployed tenant
@Y1fe1Zh0u
Y1fe1Zh0u marked this pull request as ready for review July 28, 2026 10:08
@Y1fe1Zh0u
Y1fe1Zh0u merged commit 946ac1e into main Jul 28, 2026
4 checks passed
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