Omarchy Shell plugin · v0.3.8

Your peers.One surface.

Discover, organize, inspect, and control local P2P clients and overlay-network daemons without turning your desktop into a dashboard.

Install plugin See it live

Discovery coverage

30+ known services across four runtime paths.

30+

Known services

Mesh networks, anonymous overlays, file sharing, torrents, content networks, and node software.

Runtime paths

User and system units, Docker, Podman, and exact current-user process observation.

Privacy boundary

Peer endpoints, PIDs, paths, and console URLs are redacted before reaching the UI.

Real interface

Choose a list, detail view, icon row, or grid.

These captures come from the running plugin. The screenshot workflow enables and verifies the privacy filter before capture.

Service layouts

Choose your scan density.

Move from rich grouped cards to focused details, tooltip-backed icon rows, or a two-column grid.

Comfortable grouped service list — **Comfortable** · Full summaries, grouped headings, and labeled actions.

I2P Router card with privacy-filtered details expanded — **Expanded details** · Inset service ownership and runtime context remain visually separate from card rails.

I2P Router service settings with previous and next navigation — **Service editor** · Customize one service, then move through the visible set without returning to the list.

Compact service list with icon indicators — **Compact icons** · Counts become clear pills; controls retain descriptive tooltips.

Two-column service grid — **Grid** · Two responsive columns expose more detected services at once.

Settings explorer

Depth stays in settings.

Configuration is organized by intent so the main widget remains operational and uncluttered.

Privacy and behavior settings — **General** · Privacy defaults, startup behavior, alerts, and transfers.

Appearance settings — **Appearance** · Bar, panel, loading feedback, cards, and theme roles.

Service organization settings — **Services** · Layout, sorting, grouping, favorites, density, and saved views.

Performance settings — **Performance** · Polling, event refresh, reconciliation, and traffic sampling.

Discovery settings — **Discovery** · Console routing, filters, custom services, and settings data.

Package settings — **Packages** · Detected software, optional installs, backups, and removal.

Quiet in the bar.
Show one aggregate, health, or separate category counts with custom icons.

Capabilities

Group services, run validated actions, and inspect status.

Group and filter

Group by category, status, backend, scope, or favorites. Save named views and stabilize live sorts.

Recover configuration

Validated actions, failure-aware refreshes, retained configuration backups, and atomic settings persistence.

Inspect runtime state

Health, restarts, transitions, connection counts, transfer activity, diagnostics, and local consoles when available.

User guide

Usage, configuration, services, privacy, performance, troubleshooting, and removal.

This page is the user-facing reference for installation, behavior, and troubleshooting.

Usage

Click the bar widget to open services; middle-click it to open settings.
Search by label, service, runtime, unit, or category. Reveal the filter row for status, layout, and compactness controls.
Right-click a service for safe actions and logs; middle-click it for service-specific settings.
Right-click the bar widget for a complete refresh. Press / in the panel to focus search.

Configuration

General owns privacy and startup behavior. Appearance controls bar and card presentation. Services owns layouts, sorting, grouping, favorites, and named views. Performance tunes refresh work. Discovery owns routing and custom observation-only services. Packages handles optional installs, backups, and removal.

Comfortable, compact, and minimal density work in list and grid layouts. Category grouping is available in either layout.

Supported services and runtimes

Built-in discovery covers mesh and overlay networks, anonymous networks, download clients, content networks, synchronization tools, and node software. This includes Tailscale, Yggdrasil, ZeroTier, Nebula, NetBird, I2P, IPFS, Syncthing, qBittorrent, Transmission, Deluge, aria2, Soulseek clients, GNUnet, RetroShare, Monero, and related tools.

Only detected services appear. The plugin observes system and user units, exact current-user processes, Docker, and Podman. Package actions are offered only for the maintained allowlist; containerized, manual, and externally managed deployments remain discoverable without becoming package-managed.

Privacy and diagnostics

Privacy filtering is enabled by default and removes peer or socket endpoints, process IDs, configuration paths, and console URLs before status reaches the interface. Keep it enabled for screenshots and public reports.

Support reports force the private projection. The optional event journal stores only allowlisted event kinds, counts, and timestamps. It never stores service identities or arbitrary detail.

Performance

One keep-loaded service shares status work across monitors. Snapshot indexes, a short-lived cache, request coalescing, deferred updates while scrolling, and event-assisted refresh avoid redundant scans. Podman uses bounded reconciliation instead of a persistent event process.

Use Performance settings to adjust foreground and background intervals, stopped-container reconciliation, traffic sampling, and event-assisted refresh. Disabling traffic rates also skips container-stat collection.

Troubleshooting

If data is stale, run a complete refresh and check the panel health marker.
If controls are unavailable, confirm the service is detected and has a supported unit, container, or exact process identity.
Use Performance settings to copy a privacy-filtered support report.
Restart Omarchy Shell after installation or an update if the widget does not load.

Support options ↗Report an issue ↗

Removal and retained data

Remove the widget from the bar, then run omarchy plugin remove io.github.bolens.p2p-services. This does not stop or remove service packages, containers, or their configuration.

Plugin settings and backups remain under the Omarchy directories in $XDG_STATE_HOME and $XDG_DATA_HOME so uninstalling cannot destroy user data. Delete those plugin directories separately only after confirming their backups are no longer needed.

Installation

Add one peer.

Requires Omarchy Shell and Python 3. Docker and Podman integrations are optional.

Privacy filtering defaults to enabled. Keep it enabled when sharing screenshots, diagnostics, or issue reports.

OMARCHY · PLUGIN INSTALL

omarchy plugin add \
  https://github.com/bolens/omarchy-p2p-services.git \
  --enable

omarchy restart shell