We're building tools for connected work. Start with early software that has public setup instructions, or explore what's still being developed and planned.
These entries have public source setup instructions. They are early software, not a hosted or production-ready suite. Check each product's prerequisites and limitations before installing.
File a ticket, hand it to your coding agent
A pluggable personal issue tracker that turns "I should fix that" moments into agent work. File a ticket in the browser or a terminal TUI, then copy a composed prompt or open a terminal already running your coding agent on it — with AI enrichment, git-backed history, and before/after media.
Click any element, get its source — or hand it to your agent
A framework-agnostic element inspector for dev servers: Ctrl+Alt+Click anything in your running app to see the file, line, and component tree behind it. Then open it in your IDE, or hand it — with its surrounding source — to a coding agent over MCP.
Illuminate the shortcuts you need, when you need them
Find desktop and app shortcuts, see their keys on a keyboard, and use an optional agent companion to search and configure the app. Public alpha testing starts with Omarchy on Linux.
The full catalog includes beta, development and planning entries. A listing describes a direction; it does not mean the product is available or that every app already works together.
Explore all 45 catalog entries →Use research to choose a concrete workflow. Research is a starting hypothesis, not proof of demand.
Connect real interactions and source-owned records, then check the result and failure recovery. Local integration is distinct from a publicly available release.
Improve the tool from observed use. Internal dogfooding and customer validation are different evidence, and neither is implied by a catalog card.