Your first conversation
From installing the app to talking through your first task.
What this page covers
OutcomeFinish with one short, spoken exchange and one small task you can inspect.
Before you beginHave the Ginu app installed, an account for Claude Code, Codex or the Gemini CLI, and a project you are comfortable experimenting in. The first-run screens help with the rest.
Follow these steps
Install the app. Ginu is in a closed beta. The Download page takes an email and offers a place; invited Windows testers receive an installer link by email, and the Mac app follows the same way. Run the installer and open Ginu like any other app.
Accept the agreement. The first launch opens with the terms and the privacy notice. Sending basic usage reports is off until you turn it on. Tick the box and press Accept and continue; Decline and quit leaves nothing behind but a record that you were asked.
Let the prerequisites check run. Ginu checks what it needs on this computer and checks again by itself, so something you install while the screen is open shows up without a restart. git is required, because memory, projects and Work are stored with it. tmux is optional: without it only Shell is off, and it does not apply on Windows. If git is missing, Windows offers an Install button; elsewhere the screen shows a command you can copy.
Have one AI CLI ready, and sign in to it. Ginu talks through Claude Code, Codex or the Gemini CLI and has no model access of its own, so it uses the account you already have. The screen shows a card for each one: Install where Ginu can do that for you, Sign in when it is installed but signed out. Sign-in opens that CLI’s own login, and Ginu never sees the credential. Continue unlocks once git is present and one CLI is ready.
Choose which CLI to talk through. The next screen lists the CLIs it found and the ones it can drive. Pick one; you can change it later in Settings → Engine.
Import, or skip it. Ginu can scan for instructions and memory another CLI already holds, so it starts out knowing some of your conventions. Nothing is imported unless you select it, and Import nothing is a normal answer.
Finish. Ginu is ready in text mode at this point, and nothing speaks until you press Start conversation. Either ask to be asked a few profile questions by voice later, or skip and fill them in under Settings → Profile.
Let the speech models arrive. The first launch downloads a few gigabytes of them; the prerequisites screen states the figure when it is known. You can type to Ginu meanwhile. They stay on your computer afterwards, so later launches skip the download.
Put earphones in, and split your input from your output. Never a wireless headset as both microphone and speaker: while its microphone is open the whole device drops to call quality, and Ginu holds the microphone open for the whole session so you can interrupt it. Use the built-in or a wired microphone for input and the headset for output, and choose them in Settings.
Allow the microphone, then talk. Your computer asks the first time Ginu opens the microphone; if nothing asks and Ginu stays deaf, check your system’s microphone privacy settings for Ginu. Press Start conversation on Home and say something: “What is in this project?” is a good first question. Then cut it off mid-sentence — it stops, hears you, and answers the new thing.
Example
What is in this project? Give me a short overview before changing anything.
Read the answer on Home and listen to the spoken reply. This gives you a small, repeatable check of the microphone, selected agent and output device.
Make the first task easy to review
Choose a result you can recognise: an overview of a folder, a short note or an investigation with a clear question. Name what Ginu may change and what needs your approval.
A small first task lets you learn the controls without also learning a new codebase. Keep the transcript visible; it shows what Ginu heard when a name or request was unclear.
Notes
- The first launch takes longer than later ones while the models load into memory. Text works throughout, so you are never waiting on a blank screen.
- The system’s microphone indicator stays on for the whole session, including while you are muted. That is the input stream being open, with frames dropped in software.
- A voice session cannot answer the CLI’s own permission prompt out loud, so permissions work differently from running the CLI yourself. Check the current mode with
/permissionbefore you hand over work you would not want run unreviewed. - Your memory, notes and transcripts stay on your computer. The Reference lesson lists where.
Check
You can hear the answer, see its transcript and interrupt with a correction. If one of those fails, use Troubleshooting before handing over more work.