Check MeetCap with doctor

meetcap doctor checks your meeting library, the two permissions, speech recognition, and disk space. It prints one line for each check. A line with OK needs nothing from you. A line with Needs attention tells you what to do.

Run doctor

1. Open Terminal.

2. Run this command.

   meetcap doctor

If Terminal can’t find the command, run ~/.local/bin/meetcap doctor.

When everything is fine, the result looks like this:

Library: OK. /Users/you/Library/Mobile Documents/com~apple~CloudDocs/MeetCap
Permissions: Microphone: allowed.
Permissions: System audio: allowed.
Speech recognition: OK. The one this library uses is downloaded.
Model files: OK. All 5 are downloaded.
The models take 494 MB, in /Users/you/Library/Application Support/MeetCap/models. To free the space, delete that folder. Meetings still record without it, but there are no transcripts until meetcap models get downloads the models again.
Recordings folder: OK. /Users/you/Library/Application Support/MeetCap/audio
Disk: OK. 353.1 GB free.

What doctor changes

Doctor mostly only checks. It also does two things that your settings call for:

• If you set Keep recordings for in Settings › Storage, it clears recordings older than that.
• It starts writing the summaries and minutes that finished meetings are still waiting for, and doesn’t wait for them. The text goes to the AI you chose, as after any meeting. If you chose Your agent, when you ask it, doctor only says how many are waiting.

What each line means

These lines are always there:

Line	What it checks	If it needs attention
Library	Your meeting library is there, and MeetCap can save to it.	Do what the line says. If there’s no library yet, finish first-time setup.
Permissions	One line each for the microphone and system audio.	See Permissions.
Speech recognition	The speech recognition this library uses is downloaded.	Run meetcap models get.
Model files	Every file that speech recognition needs is downloaded and complete. The line after it says where the files are and how much space they take.	Run meetcap models get. It downloads only the files that are missing or damaged.
Recordings folder	MeetCap can save recordings in this computer’s recordings folder.	If the line says it’s a file, move that file somewhere else. If MeetCap can’t save there, fix the folder’s permissions.
Disk	The disk that recordings go to has at least 2 GB free. Recording doesn’t start with less.	Free up space. To clear old recordings, go to Settings › Storage.

If this computer has recordings, a line also says how much space they take and how far back they go.

These lines appear only when they apply:

Line	What it means	What to do
Library settings	A setting in the library’s config.json can’t be used. The line names it.	Change or remove that setting.
Language	The library’s language setting can’t be used, so MeetCap uses another language for now.	Choose a language in Settings › General.
Downloads	A download didn’t finish and left files behind.	Run meetcap models get. It clears those files first.
Download sources	Where the files came from, and any source that failed.	If it needs attention, check your internet connection and run meetcap models get again.
Voices on file	The voices MeetCap remembers come from another version of speech recognition, so it can’t recognize those people now.	Run meetcap models get.
Glossary	A speech recognition file is missing or damaged. Recognition doesn’t favor your glossary’s spellings, but recording works as usual.	Run meetcap models get.
Model list	This copy of MeetCap is incomplete.	Install MeetCap again.
Agent for summaries and minutes	Shown if you chose Your agent, run by MeetCap. It checks that the agent is on this computer and new enough.	Install or update the agent, or choose another one in Settings › Minutes.
Local model	Shown if you chose This computer. It checks that the local model is downloaded and complete, and says how much disk space it uses.	Run meetcap models get --local.
Summaries and minutes waiting	Summaries and minutes that finished meetings are still waiting for.	Nothing, unless an item has failed 3 times. MeetCap then stops trying it by itself. To try again and see why it failed, run the command in the line.

Report a problem

If something isn’t working, you can send us a report from MeetCap.

1. Right-click the MeetCap icon in the menu bar, then choose Report a Problem. You can also choose it from the Help menu.
2. Describe what happened.
3. Click Send.

The report includes diagnostics that help us find the cause. Diagnostics never include recordings, transcripts, minutes or names. To review them before you send, click Show details.

If the report can’t be sent, MeetCap saves it as a file. Email the file to us from the feedback page.

To save diagnostics without sending a report, choose Save Diagnostics from the same menu.

In Terminal, use meetcap feedback and meetcap diagnose.

Send the result with a problem report

If you report a problem on GitHub, the form asks for the output of meetcap doctor:

1. Run meetcap doctor.
2. Copy everything it prints, and paste it into the form.

The output of meetcap doctor shows folder paths on your computer. Delete any that you don’t want to share. Issues are public, so don’t attach recordings or paste transcript text.