Settings
The engine, the voice, the devices and who may connect.
What this page covers
OutcomeChoose the engine and the two audio devices, then prove the choice with one exchange.
Before you beginSign in to the CLI you intend to use — beforehand, or from Engine, which opens a sign-in shell for it.
Follow these steps
Engine is where you choose which CLI this conversation and its tasks run through, and where a signed-out one can be signed in. The login opens in a shell and finishes there; Ginu never sees or stores the credential.
Voice shapes both directions: eleven voices and a speaking speed on one side, and a Patience control on the other that decides how long a pause may be before Ginu takes its turn. It stays where you put it.
Devices, theme and text size are preferences for this device and apply the moment you change them. Connections governs access from another device; Permissions is a read-only account of what this session has granted.
Example
After changing a device, say: Can you hear me? Keep your reply short.
Read the transcript and listen on the intended output. One short repeatable request is what makes a device change verifiable at all.
Two devices, one engine, one change at a time
Engine shows which CLIs are installed and which are signed in, and lets you pick the one this session talks through. Selecting it does not sign you in to that provider — Ginu has no model access of its own, and being signed out is worth ruling out before you go looking for a missing spoken reply.
Input and output are separate choices and should be separate devices. A wireless headset used as both drops macOS into call quality for the whole session, because the microphone never closes; a built-in or wired microphone with headset output avoids it.
Appearance is how the app looks, Connections is who may reach it from another device, and standing permissions decide which actions stop to ask. Three different questions that are easy to conflate when something is refusing to happen.
Notes
- Choosing an engine does not sign you in to that provider. Ginu has no model access of its own — the CLI account you already have is what does the work, and its costs stay yours.
- Signed out of the selected CLI, Ginu says so aloud and refuses to spawn tasks. Those are the two consequences you cannot see on the page itself.
Check
Engine reports the CLI you meant to use, and a spoken exchange goes through the input and output you chose.