Getting started with Jinn

By the end of this you’ll have one real meeting recorded, written up, corrected where the AI got it wrong, and answering a question you put to it — and you’ll know which screen each of those happens on.

1. Check which workspace you’re in

Everything in Jinn lives inside a workspace: one workspace is one team, with its own people, projects and AI account. Which steps below are yours depends on how you got into it:

• You created it — it’s empty and yours to set up. Carry on to step 2.
• A colleague invited you — whoever runs it has probably done steps 2 and 3 already. Step 2 isn’t yours to change in any case: managing AI keys is limited to workspace owners and admins. If the workspace already has a project you can record into, jump to step 4.

2. Set up your AI

Everything Jinn does with a meeting is AI work — writing out what was said, reading the transcript into write-ups, indexing both so search finds them by meaning. None of it happens until an AI account is behind it, so this is the step to get right before you record. Open Settings → AI Providers. Under How your AI is powered you either run on Jinn credits, which needs nothing from you, or on provider keys you paste in yourself. Whichever you choose, How your AI is powered walks through the modes, which provider does which job, and what to do when a key stops working.

3. Create a project

Click New project, name it after the work rather than the meeting — Website redesign, not Monday sync — and choose who can see it:

• Private — only you and the people you invite.
• Open — anyone in the workspace can find it and work in it.

You can change the name and description later. See projects.

4. Record a meeting

Recording happens in the Jinn desktop app, so this is the point to download it if you haven’t. It records on macOS and Linux; the browser can do everything else, but it can’t record. Now start the meeting. The recording bar appears over whatever you’re doing: click Start, then click the bar to open it and pick the project under Select project if you know it. Click Stop & Generate when the meeting ends. Jinn saves the audio, creates the recording and opens it. See recording a meeting.

5. Give it a project, if you didn’t

Recorded without picking a project? That’s the ordinary case. The recording is saved and will be transcribed, but nothing will read it until it belongs somewhere. Look in your inbox: there’s a notification saying the recording needs a project. Choose one from the notification and the rest starts by itself. See what to do about a recording with no project.

6. Read what came back

Open the recording. The transcript is written during the meeting, piece by piece, and is final a few minutes after you stop. The page updates itself, so there’s nothing to refresh. Once the transcript is there, the Default agent reads it and writes back a summary, the key points and the action items it heard. Read it, and fix what’s wrong: it’s ordinary text, so rewrite a point, delete one that isn’t real, or regenerate the whole thing.

7. Ask Jinn about it

With the project or the recording open, click Ask Jinn in the bar at the bottom of the screen (or press ⌘J, Ctrl+J off a Mac). A chat opens beside it, already reading what you had open. Ask in your own words: do we have any decisions from our last sync?, what are my next steps on this project? Jinn answers from what it finds: transcripts, your docs, and the write-ups your agents wrote, and every answer shows what it read to get there. See asking about your work. This is the step that pays for the rest. A meeting that can answer a question weeks later is worth recording; one you have to re-read isn’t.

If something didn’t happen

Where to go next