Sources Plugins

Sources & Plugins

The Sources & Plugins page manages the package sources NeoArch talks to and the curated catalog of extensions that add behavior — browse, install, launch, or uninstall the whole thing from one place.

Overview

NeoArch isn't tied to a single repository — it treats pacman, AUR, Flatpak, npm, and local plugin feeds as sources. The Sources & Plugins page shows what's connected, lets you toggle them, and manages the plugin system that extends the app itself.

Two things live here:

• Package sources — the providers used by Home & Discover and Software Updates: official repositories, AUR (live RPC), Flatpak user remotes, npm globals.
• Plugins — the curated catalog of extensions (50+ built-in), each with a lifecycle hook that runs inside NeoArch. Browse them in a card grid or a list, install the ones you want, launch them straight from this page, and remove them again — no juggling files.

The page layout

1. Grid view

By default plugins appear as a card grid — one card per plugin with its icon, name, category, and quick Launch/Install action right on the card. Use the grid toggle to jump between the card grid and the table list.

2. The toolbar (navbar)

Buttons above the grid/list:

• Install Selected — install all the plugins you've ticked, in one go. Disabled until something is selected.
• Clear — reset the current selection (with a subtle red hover to signal it removes your picks).
• A selection label showing how many plugins are checked.
• On the right: the grid / list toggle so you can flip between the two views.

3. The source panel

Controls on the right side, grouped like the other pages:

• Sources — pacman, AUR, Flatpak, and npm with a live count from the curated catalog; toggle any source on/off to filter the catalog.
• Status — All / Available / Installed states; switch to Installed to see only what's already on your machine, or Available for the ones you haven't installed yet.
• Category — chips like System, Monitor, Development, Internet, Multimedia, Games, Office, and Backup; tick one to narrow the catalog to that category.
• Sort by — Name A-Z, Name Z-A, Category, Source, or Installed First.
• Count bar at the bottom showing how many extensions match the current filters.

There's no search box on this page — the catalog is small enough to browse, and the Status/Category/Sort controls do the narrowing.

4. List view — the ⋯ menu and the right panel

Flip to list view and each row shows the plugin with a checkbox (for Install Selected) and a ⋯ menu on the right:

• Launch — run an already-installed plugin right from here.
• Install (or Uninstall for installed ones).
• View in browser — open the plugin's page.
• Copy name.

Clicking a row opens a right panel (detail card) with the plugin's description, category, and source, plus its action button — so you can read about a plugin before installing it.

How to use

1. Open Sources & Plugins from the sidebar (the sources/sparkle icon).
2. Toggle sources — pacman/AUR/Flatpak/npm; disable any source you don't use.
3. Filter the catalog — Status (All / Available / Installed), Category chips, and Sort by.
4. Install — tick plugins and press Install Selected (or install one at a time from a card, the row menu, or the detail card).
5. Run & manage — Launch installed plugins from this page; remove them via the row menu or card when you're done.

What you can expect

• 50+ built-in plugins ship with the app, grouped by category.
• Plugin feeds are just sources — they can be toggled per-machine, so you control what executes.
• Because plugins are Python, treat community plugins like AUR packages: prefer known, reviewed ones.

CLI equivalent

Sources and plugin toggles are GUI-managed; the CLI exposes package source searches directly:

neo search foo --pacman               # official repos only
neo search foo --aur                  # AUR only
neo search foo --flatpak              # Flatpak only
neo search foo --npm                  # npm only

Good to know

• Flatpak sources follow your user remotes (flatpak remotes --user) — install Flathub there if nothing shows up.
• npm sources read globally installed packages.
• Plugin lifecycle behaviors are opt-in per plugin: check the plugin's page before enabling.
• Install Selected is disabled until you tick at least one plugin, and Clear wipes the current selection.

Related pages

• Home · Settings · Home & Discover · Configuration

---

↩ Back to Home