Voice-first help
Talk to NyrA, keep the buddy visible, and use mute or pause controls when you need silence.
Founding paid beta for Windows
A voice-first desktop helper that can look at your screen and perform visible computer-control workflows with your permission.
Positioning stays narrow: practical desktop help with visible controls, not an unrestricted autonomous worker.
Talk to NyrA, keep the buddy visible, and use mute or pause controls when you need silence.
NyrA can look at the screen only through explicit consent and app-level permission gates.
Clicking, typing, waiting, and app actions run through paid entitlement checks, consent checks, and high-impact approval rules.
These are current build artifacts. They must be refreshed whenever the shipping UI changes.

Permissioned screen-aware help for visible desktop tasks.

Visible click/type automation with explicit guardrails.

Built around deliberate interaction instead of reacting to every background word.

Camera look is a permissioned feature, not a hidden background capture promise.

Paid beta access is tied to backend-verified subscription and device activation.
The product promise depends on being honest about permission, billing, support, and limits.
Microphone, camera, screen, computer-control, third-party AI, memory, and passive-log consent are implemented and gated.
Payment, credential, destructive, account-changing, system, installer/script, terminal, and data-sharing risks require approval.
API swarm, voice, realtime, screen capture, computer control, file/app control, and developer terminal are gated behind active license state.
Monthly subscription price from the command center.
Draft policy pages are ready for review. They are not final legal advice and should be reviewed before live payment collection.
Clear limits reduce support risk and keep the beta honest.
NyrA can assist with visible workflows, but sensitive actions are gated and high-impact actions require approval.
The beta should avoid legal, medical, financial, child-focused, and enterprise compliance workflows.
The user-facing promise should stay wake/trigger based, with pause, mute, and consent controls visible.