Example receipt: verified
Fill the form with my approved details
- Approved for the selected browser tab only
- Six fields filled, password field skipped on purpose
- Every value read back and matched
Example approval
Open the project folder in VS Code?
Example receipt
Window opened and confirmed on screen
Form sent, confirmation not seen: needs attention
How a task runs
Every request that changes something on your PC goes through the same eight steps. RIXU only calls a task done once a tool confirms it.
Understands what you asked for, in the words you used.
Pulls in recent conversation and the memories that matter.
Lays out the exact steps before touching anything.
Waits for your yes on anything that needs one.
Runs only the approved steps, with Stop available throughout.
Checks the real result on screen, in the file or on the page.
Records what ran, what changed and what was confirmed.
Tells you the actual outcome, then goes back to listening.
Example receipt: verified
Example receipt: needs attention
Capabilities
This is what RIXU is designed to do. The status board further down says exactly how far each part has been proven.
English, Hindi, Urdu and Hinglish, informal spelling included, as far as the selected models support them. RIXU follows your latest request, resolves "that one" from recent context and asks one short question when an action is ambiguous.
Ordinary voice replies stay short. Ask for detail and it expands. In research mode it separates what it retrieved from what it inferred, and never invents a source.
Conversation styles
Styles change the tone, never the permissions.
Facts, preferences, projects, tasks and reminders live in a local database on your PC. Newer corrections win, duplicates merge, and only the relevant memories are pulled into a conversation. Credentials never go into ordinary memory.
Open an approved app and confirm it opened. Edit a project file and check its contents. Fill a browser field and read the value back. There is no unrestricted terminal or file access.
"Is screen par error samjhao." RIXU looks only at the window you select, asks before a screenshot goes to a cloud vision provider, treats on-screen text as untrusted and stays out of password fields.
A local brief of pending and overdue reminders and active projects, with no chat-model request. Calendar and Gmail summaries join only after you connect and authorize those accounts. Scheduled briefs are opt-in.
Gmail summaries and draft replies, Calendar events and YouTube channel insights once you grant OAuth consent. Nothing is sent, booked or published without your approval, and no account is polled silently in the background.
Local face matching picks a personal greeting. It stores encrypted face vectors, not photos, shows when the camera is on and can be paused or deleted. It never unlocks Windows or approves anything.
Voice first
Speech is recognised on your PC, replies are spoken sentence by sentence while the rest is still being written, and RIXU goes back to listening on its own. A saved mute or Tools Lock is always respected.
Capture pauses while RIXU speaks and resumes after a short guard for leftover echo, so it does not answer itself.
Fresh speech stops playback promptly. RIXU never claims perfect speaker separation and tells you when to repeat the start of a sentence.
One Stop cancels the reply being generated, the speech queue and any active task, without spending a model request.
You see the final transcript, never a fake live preview. Cancelled, echoed or low-confidence audio never starts a task.
RIXU's visualizer is driven by real audio. So is this one.
Microphone off. Turn it on to see your own voice drive the waveform.
Safety and privacy
RIXU may call its owner boss, but being the owner never skips a confirmation. These safeguards apply in every conversation style.
You approve the specific action and its scope, not a vague permission to do things.
One switch blocks every tool. Conversation keeps working, actions do not.
Available for the whole run, and it cancels speech, generation and tasks together.
A history of what ran and what was confirmed, with uncertain outcomes kept as needs attention.
Speech recognition, memory and face matching run on your PC. Cloud providers are optional and never switched on silently.
Never hardcoded, printed, stored in memory or packed into an installer.
Text on a screen or web page cannot give RIXU instructions, and stale page elements are rejected.
Isolated IPC with trusted sender checks, local-only services and scoped file access.
Status board
Each status reflects the latest validation. Anything that depends on a real microphone, camera, speaker or account stays in live verification until it has been tested on a real PC.
Showing 20 of 20 capabilities
Whisper transcribes speech on the PC itself. Testing with a physical microphone is still pending.
Silero VAD detects when you finish speaking and filters RIXU's own playback. Room echo and interruption still need real hardware tests.
Each sentence is spoken as soon as it is ready instead of waiting for the full reply.
Local Piper voices. Hinglish accent quality is not fully verified.
Not established with the local Piper voices yet.
A configurable sound trigger that wakes RIXU without a keyboard.
The current conversation provider, with replies streamed as they arrive.
Mixed-language sentences and informal spelling, as far as the selected models practically support them.
Facts, preferences, projects and decisions stored locally in SQLite.
Kept on disk, so they survive restarts.
Each action runs only inside the scope you approved.
Stop cancels work in progress, Tools Lock blocks tools entirely, and every action leaves a receipt.
RIXU looks only at the window you choose.
Checks the page after an action instead of assuming it worked.
Integration scaffolds exist. Live accounts need OAuth setup and your consent.
Enrollment needs the real owner and camera permission. Matching is approximate.
Not built, which is why face matching is never used for security.
The original RIXU visual identity.
Checked in the latest validation on a PC whose local runtime was already set up.
Not established yet. A new PC still needs the local runtime set up first.
Download
Every published installer comes with its SHA-256 checksum, so you can confirm the file is exactly the one that was released.
RIXU 0.21.0
Current release
Local speech recognition and speech output, streaming conversation, persistent local memory, reminders, approved tools with receipts, and screen and browser result checks.
The installer for this version is not published on this page yet.
SHA-256 checksum
The checksum appears here together with the installer.
Get-FileHash .\<installer file name> -Algorithm SHA256FAQ
The questions worth asking before you let an assistant act on your PC.
No. Anything that changes something on your PC or in an account waits for your exact approval, and Tools Lock blocks tools entirely. Being the owner never skips a confirmation.
Your speech is transcribed locally with Whisper. The text of a conversation goes to the conversation provider you configured, currently Groq. Cloud voices and other providers are optional and are never switched on silently.
No. It only chooses a personal greeting. Matching is approximate and has no anti-spoof protection, so it never unlocks Windows, approves tasks, grants permissions or signs in to accounts.
It understands English, Hindi, Urdu and Hinglish as far as the selected models support them. Spoken replies use local Piper voices for Hindi and English. Natural Urdu speech is not established yet.
Not on its own yet. The current build expects its local runtime to be set up already. A self-contained installer for a fresh PC is listed on the status board as not implemented.
The task stays marked as needs attention. RIXU does not blindly repeat an uncertain send, click or file change, and it tells you what it could and could not confirm.