feat: Plugins settings page

[adityathebe]

Summary by CodeRabbit

• New Features
  • Added a new Plugins page in settings displaying available plugins with names, descriptions, versions, and associated agents.
  • Users can manually refresh the plugin list to fetch the latest information.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
aws-preview	Ready	Preview	Jun 24, 2026 3:10pm
flanksource-ui	Ready	Preview	Jun 24, 2026 3:10pm

[coderabbitai]

Warning

Review limit reached

@adityathebe, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 16 minutes and 8 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits.

🚦 How do rate limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 4af837af-10b2-43c8-8515-0110d42a04db

📥 Commits

Reviewing files that changed from the base of the PR and between ed27993 and 20e0fa3.

📒 Files selected for processing (5)

• src/App.tsx
• src/api/services/plugins.ts
• src/context/UserAccessContext/permissions.ts
• src/pages/Settings/PluginsPage.tsx
• src/services/permissions/features.ts

Walkthrough

This PR introduces a new Plugins settings page accessible from the application's settings menu. It adds permission controls, a plugin listing API service, React UI components for displaying plugins in a table, and integrates the page into the main app's routing and navigation.

Changes

Plugins Settings Page Implementation

Layer / File(s)	Summary
Permission and access control configuration src/services/permissions/features.ts, src/context/UserAccessContext/permissions.ts	The settings.plugins feature flag and plugins table identifier are registered, enabling feature-gating and role-based access control for the Plugins page.
Plugin API service src/api/services/plugins.ts	A new PluginListing type and getPlugins() service function are defined to fetch plugin data from the /plugins backend endpoint.
Plugins page UI components src/pages/Settings/PluginsPage.tsx	PluginsPage component fetches plugins via useQuery, renders a PluginsList table with columns for name, description, version, and agent, and wires SearchLayout's onRefresh to refetch().
App routing and navigation wiring src/App.tsx	FaPlug icon is imported, PluginsPage is dynamically imported, a "Plugins" entry is added to the settings submenu (gated by feature flag and table permission), and a /settings/plugins route is registered with authorization access check.

Sequence Diagram

sequenceDiagram
  participant User
  participant AppRouter
  participant AuthCheck as withAuthorizationAccessCheck
  participant PluginsPage
  participant useQuery
  participant getPlugins
  participant APIBackend as /plugins endpoint
  
  User->>AppRouter: Navigate to /settings/plugins
  AppRouter->>AuthCheck: Check access to tables.plugins (read)
  AuthCheck-->>AppRouter: Access granted
  AppRouter->>PluginsPage: Render component
  PluginsPage->>useQuery: Initialize query with getPlugins
  useQuery->>getPlugins: Call on mount
  getPlugins->>APIBackend: GET /plugins
  APIBackend-->>getPlugins: Return PluginListing[]
  getPlugins-->>useQuery: Resolve with plugin data
  useQuery-->>PluginsPage: Update with data and loading state
  PluginsPage->>PluginsPage: Render SearchLayout + MRTDataTable
  PluginsPage-->>User: Display plugins table

Loading

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'feat: Plugins settings page' directly and clearly describes the main change: adding a new Plugins page to the settings section.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feat/plugins-settings

✨ Simplify code

• Create PR with simplified code
• Commit simplified code in branch feat/plugins-settings

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}