Find what already exists.
Limitless can surface official and community plugins as candidates. Omarchy and the user still decide what fits.
Why it fits
Omarchy is built to be customized, but customization should not start from scratch.
Some work becomes a published plugin. Much of it remains a useful personal tweak. Limitless lets the agent check both before rebuilding either one.
Reuse work before it becomes a plugin.
Useful steps and approved customizations can be retained even when nobody plans to publish a package.
Use one Library connection.
The configured agent can also use Limitless for work beyond Omarchy. No second package or connection is required.
How it works
The agent checks before it builds.
The plugin connects to the agent already selected in Omarchy. Describe the task once; Limitless checks for one useful next move.
- Need
The goal already in the agent’s context.
- Check
Search locally, or search the service after opt-in.
- Answer
Get one component, one reusable method, or no match.
- Verify
Omarchy checks the result locally before use.
- Keep
Retain useful work under the owner’s sharing settings.
Use approved exact files only after Omarchy verifies them and the user enables the change.
Reuse the useful approach while the agent creates fresh work for the current environment.
When nothing safely fits, the agent receives no candidate and builds normally.
Inside Omarchy
Use it from Omarchy. No terminal required.
Setup, search, settings, and activity stay in the panel. The optional CLI exists for diagnostics and lower-level control.
Query local or opted-in service discovery and set contribution defaults.
Connect the Omarchy default agent and, optionally, other supported clients.
See connection status, usage, account, and sharing settings.
See private totals for Omarchy-specific and general Limitless activity.
Understand the project, update the runtime, and reach official sources.
Codex, Claude Code, Grok, and Antigravity CLI have verified setup adapters.
Trust and control
Local by default. Connected only when you opt in.
The plugin and local Library are open source. Local work stays under the user’s control. Connecting to the service does not publish anything.
Local first
Installation does not require an account, hosted service, elevated privileges, or a model API. If the service is unavailable, local reuse remains available.
Inspect how it works
The runtime, agent connection, local selection, and installation checks are public and independently inspectable.
Share deliberately
Owners choose local, public, team, or organization scope and whether contribution is manual, agent-mediated, or automatic. Automatic public sharing requires explicit saved authorization.
Limitless Library for Omarchy