Import from Teams or Meet

Bristlenose can list the meetings you recorded in Microsoft Teams or Google Meet and fetch the recordings straight into a project, instead of you downloading them one at a time and dragging them in.

Importing from a meeting platform is a macOS app feature. The command line doesn't offer it.

Zoom isn't offered yet.

Sign in

The first time you open the import window it shows Not signed in. Click Sign in with Microsoft or Sign in with Google and finish in your browser. Bristlenose never sees your password.

Some organisations require an administrator to approve a new application before anyone in the tenant can use it. If that applies to yours, the sign-in won't complete until they do — the window says so rather than failing silently.

Choose how far back to look

Window sets the period — the last 30 days, or whatever you pick. Meeting recordings expire, so a wider window is not always a longer list.

Filter narrows the list as you type, matching the meeting title, the organiser, and the people who were in the meeting — the last two where your account can see them. Matching on title depends on your meetings being named usefully: a call titled "Chat with Sarah" won't match a filter of "interview".

Read the list

Each row is a meeting. The columns are Meeting, Scheduled, Recorded, Size, Expires, and Status. Columns with no data on your account are dropped rather than left empty — Google Drive has no per-file expiry, so Meet shows no Expires column at all, and Scheduled needs calendar access your tenant may not grant.

The footer shows the arithmetic: how many meetings are in the window, how many recordings you can fetch, how many are already imported, and how many were organised by someone else. If Bristlenose stopped paging before it reached the end of the window it says Partial list rather than presenting a short list as a complete one.

Status is where a recording tells you it can't be fetched — Needs access, Not recorded, Someone else, and others. Recording permissions explains each one and what to do about it.

Choose where it goes

Project picks the destination. New Project… makes one; the recordings you import are copied into that folder.

Import

Tick the recordings you want and click Import. Rows download a few at a time, each showing its own progress, and Stop halts one row without abandoning the others. A row that fails can be retried without re-fetching the ones that succeeded.

Bristlenose checks that what arrived is what was promised — the byte count against the size the platform reported, and the file's own signature — so a truncated download is reported rather than analysed as though it were complete.

What happens next

When the batch finishes, Bristlenose starts the analysis: incremental if the project has been analysed before, a fresh run if not.

It deliberately doesn't start one when a run is already going for that project, when the last run failed, or when nothing landed. In those cases the files are still in the folder and the project's row in the sidebar shows a count of new files, so you can start the run yourself when you're ready.

Transcripts

The import fetches the recording, not the platform's transcript. Bristlenose transcribes locally as it would for any other recording.

If you want to use the platform's own transcript instead, download it yourself and put it in the project folder next to the recording — a .docx or .vtt sharing the recording's name is picked up as that session's transcript, and transcription is skipped. See Supported files.

Manage the accounts you've connected

Settings ▸ Accounts lists the accounts you have signed in to, and disconnects any of them. Disconnecting makes Bristlenose forget the sign-in and stop listing your recordings; recordings you have already imported stay in your projects.

What leaves your machine

The import window shows attendee names and email addresses so you can tell one session from another. It does not write them to disk — close the window and they are gone. Only the recording is kept.

If your project folder is inside a synced folder — iCloud Drive, OneDrive, Dropbox — recordings you import will sync there too, which may not be where your client expects their material to sit. The privacy policy covers this in full.