Skip to main content
You press record and, a few minutes later, something you can read is waiting. Months after that, a search brings the moment back. Almost everything between those points happens without you: each part works on what the part before it produced.
A workspace holding three projects; one project holds recordings and docs, the people who can see them and the agents that read them. Below it, a recording becomes a transcript, Jinn generates a summary, key points and action items for each agent, and later you ask an agent whenever you need it, search, and the moment is back.A workspace holding three projects; one project holds recordings and docs, the people who can see them and the agents that read them. Below it, a recording becomes a transcript, Jinn generates a summary, key points and action items for each agent, and later you ask an agent whenever you need it, search, and the moment is back.

How Jinn is put together

Workspaces, projects and agents

A workspace decides who’s on your team, what the settings say, and whose AI account the work runs on. A project decides who can open its recordings and docs, and which agents read them. One of them, Default, runs on every new transcript by itself. An agent is added once in the workspace and starts reading when you put it on a project. File the same meeting in a different project and it comes back read differently, by different roles, in front of different people. That’s the whole reason to think about projects before you record.

Your part and Jinn’s part

Every step, in order

The chain below follows a meeting. Docs your team writes and reports from your customers land in the same project, and the same agents read them.
1

You record the meeting

The Jinn desktop app’s recording bar sits on top of whatever you’re doing. Start, pause, stop. You can pick the project before you start, or leave it and decide later. When you stop, Jinn saves the audio and creates the recording.
Recorded it somewhere else? Drop the audio or video file right to Jinn instead. See uploading a recording.
2

The recording lands in Jinn

If you picked a project, it lands there. If you didn’t, it waits in your inbox with a note that it needs one — and nothing analyses it until it has one. Assigning the project from that notification is what starts everything downstream. See what needs you after a meeting.
3

Jinn transcribes it

Jinn writes the transcript while the meeting is still going, piece by piece, so most of it is there by the time you stop. The final version is ready a few minutes after you click Stop & Generate, and the page updates itself — there’s nothing to refresh.
4

The agents read it

You get one write-up per agent, in a row of agents on the recording: a summary, the key points, and the action items somebody suggested, written the way that role would write them. Default starts as soon as the transcript is ready; every other agent on the project runs when you ask for it, so a project with five agents and one in the row is working as intended. See reviewing a meeting.
5

You correct and tag

This is the only step with a deadline of sorts: do it while the meeting is fresh, because you’re the one who remembers what was meant. Correct the write-up, then tag the passages you’ll want to find again.
6

You find it whenever you need it

This is what the rest of it was for. Search what was said rather than which meeting said it — indexing reads your transcripts and write-ups for meaning — and narrow it to your own projects, to an agent or to a tag. Or ask the chat in plain words and let it find the answer for you, with a link back to the meeting it came from.

Where to go next

What Jinn is

What Jinn does, and the teams it suits.

Getting started with Jinn

Set it up and take one real meeting all the way through.