Rant Mode: save and retry extracted tasks

What it is: you talk for up to 9½ minutes about everything you need to do; myScribe transcribes it, pulls out tasks, sub-tasks and even new projects, and shows you a review screen before anything is saved.

Where: the Rant button in the New Task modal, the Rant action on a project dashboard, or the keyboard shortcut Ctrl/⌘ + Shift + R.

How to use:

1. Start the rant. A recording sheet opens with a live waveform and a timer.
2. Talk. Say deadlines and times out loud ("by Friday", "at 2:30") and name people.
3. Stop. Three progress steps run: Uploading → Transcribing → Extracting.
4. The Review Your Rant screen opens. Every extracted task is pre-ticked, with editable Title, Priority, Due Date, Time, Assignee and Project, plus its sub-tasks (each with their own date and time). You can untick, edit, delete, add sub-tasks, and create a brand-new project inline.
5. Create N Tasks saves the selected results. Wait for confirmation. If saving fails, the review stays open with an explanation and keeps the unsaved results. Retry after checking your connection and team access. Confirmed tasks are removed from the retry list; any failed subtasks remain linked to their saved parent, so retry does not recreate the parent.

Nothing is saved until you press Create. Closing or Cancel discards the remaining review items, not tasks already confirmed saved. Close and editing controls are unavailable while a save is in progress.

What actually happens behind the scenes: the audio is uploaded to temporary storage, transcribed, then sent to the AI with your existing project names, your name and your teammates' names as context. The temporary audio file is deleted as soon as the transcript comes back: rants are never saved as recordings. The AI is deliberately biased toward guessing a project rather than leaving it blank, because you can correct it on the review screen.

Gotchas

• Hard cap of 9 minutes 30 seconds. It auto-stops at the limit and still saves what you said.
• If nothing intelligible was captured you get "No speech was detected"; if the AI finds nothing actionable you get "No tasks found in your rant".
• First-person = you. "I need to…" assigns the task to you. To assign to someone else, say so explicitly.
• If you are currently filtered to one project in the sidebar, the AI is told to default everything to that project.
• Assignee is matched to teammates by first/display name; unmatched names are kept as plain text, so the task shows a name chip that is not linked to an account.
• New projects the AI proposes are created only for tasks you keep ticked.

Plan: not gated. Any plan can use Rant Mode.

2.6 Automatic extraction from meetings

What it is: after any recording is transcribed, myScribe reads the transcript and creates tasks with owners, due dates, priorities and a timestamp back to the moment they were said.

Where the results appear: the recording's Actions tab, and in the normal Tasks list/board/calendar alongside everything else.

What it actually does

• Runs automatically for every transcription route: in-app recording, uploaded file, meeting-bot recording and the iOS shortcut import. Nobody has to press anything.
• It is given your team roster plus each member's name aliases (Assignees, named speakers, and name aliases) so "Izzy" resolves to the right account.
• A teammate is linked only when the meeting names them. Meeting voices start out as anonymous labels ("Speaker A"), so myScribe will not guess which teammate a voice belongs to. A task goes to a teammate's account only when that teammate's name or alias is said in the transcript, they are named in the recording's speakers, or a speaker is linked to them. Otherwise the task keeps the speaker label or name, with no account linked. Tasks for you, the person who recorded, can always be linked to your account.
• It sets an execution order (a project-manager's view of what must happen first) which is deliberately different from the order things were said. The Actions tab lets you flip between Order and Mention sorting.
• It assigns each task a project (the AI's explicit pick → the recording's own project → a keyword match on the title) and a company inherited through the project/folder chain (Projects, folders and companies).
• It de-duplicates: re-running extraction adds only genuinely new tasks and reports "N duplicates skipped".
• When tasks go to a linked teammate, myScribe tells that person once per recording, through the bell, push and email (their Task Assignments switches apply). It waits until the meeting's AI title is ready. The email gives the title, when the meeting started and how long it ran, who else spoke (when the speakers have names), the first few tasks, and the account email it was sent to. Nobody outside your team is notified, and you are never notified about tasks from your own recording.

Regenerating: Actions tab → Regenerate. If the recording has more than one named speaker you are first asked to confirm the speaker mapping. Regeneration adds to what is already there: it never wipes your edits.

Limits and gotchas

• The AI is tuned to over-extract. Expect roughly 5–15 tasks from a normal meeting, including small throwaway commitments. Deleting extras is expected behaviour, not a fault.
• A task spoken to someone who is not on your team gets no account link: just a name chip you can link later.
• Extraction is not plan-gated. There is a feature flag for it in the plan table, but no code anywhere checks it, so every plan including free/pay-as-you-go gets automatic task extraction.
• Regeneration is plan-gated: free and pay-as-you-go get 5 regenerations per type per month; Pro, Pro w/ AI Employee, legacy Pro and Enterprise are unlimited. Hitting the cap shows a warning and opens the upgrade page: it is not an error.

Timestamps are rewound 10 seconds so you land just before the moment. If the AI names a time past the end of the recording, the jump falls back to the start rather than to a point that does not exist.