Your ComputerUnderstands You Now.
Operance is a local-first AI desktop action layer. Say or type what you want, then route it through typed actions, validation, policy, and OS adapters before anything runs.
Fedora KDE Plasma Wayland first · Windows and macOS are architecture targets
No Raw Shell Access. No Guessing.
Every command turns into a typed, checked action instead of an arbitrary shell call. Common phrases are matched deterministically. Optional local model planning is still constrained to Operance's typed action schema, validation, policy, and confirmation gates.
The current public beta is honest about scope: Fedora KDE Plasma Wayland first, source checkout for contributors, and an RPM runtime path for early testers.
Powerful. Private. Safe by Design.
Voice or Text, Your Choice
Click the tray to talk, type a command, or run the local voice loop during development.
Easy to Extend
Add commands or port to a new OS by working through providers and adapters, not by branching the core.
Operance keeps the core desktop workflow on your machine. The tray and verified commands work without an AI model; optional planner fallback can be enabled only after readiness checks pass.
- + No cloud required for core use. Verified commands work offline without a model.
- + No account required. Install, smoke test, and file issues from a local setup.
- + No arbitrary shell execution. Tools must pass typed schema, validation, and policy.
- + Open source. Inspect the runtime, adapters, planner, and safety code.
- + AI is optional. Local planner fallback is bounded and disabled unless configured.
Install the Packaged Fedora Beta.
Download setup.sh and the RPM from the same GitHub
release, then run these commands to install, verify, and list the
commands available on your host.
bash ./setup.sh --package ./operance-0.1.0-1.noarch.rpm
operance --installed-smoke
operance --supported-commands --supported-commands-available-only
Just Say What You Mean.
Current Fedora KDE Wayland beta examples. Availability depends on host readiness; destructive actions ask for confirmation.
Read the Docs. Build What's Missing.
All guidance lives in the repo as Markdown. Start with the README, then pick the doc that matches what you want to build.
One Engine. Many Operating Systems.
Your words pass through shared safety layers before any native desktop action runs. Intent, planner, policy, validation, daemon, and runtime orchestration stay portable while providers and adapters own host readiness and OS-native execution.
Windows and macOS provider scaffolds exist for adapter authors, but the public beta runtime is Linux first.
Safe Because of How It's Built.
Operance does not rely on a model deciding what is safe. Safety is structural: every command has to resolve to an approved typed action before it can reach an adapter.
The planner cannot invent an arbitrary command. Every action must be in the typed tool catalog.
Verified tray and command flows work locally without an AI model or hosted account.
Move, rename, quit, and delete flows are confirmation-gated where policy requires it.
Common commands are matched deterministically, so the beta remains useful without planner setup.
Linux Now. More Later.
Ready to Turn Intent into Action?
Public beta · Open source · MIT licensed
operance --version · v0.1.0 · MIT License