Meeting transcription and agent memory

Every surface the ruling changes, in the order someone meets them. A design mock: nothing here is persisted, captured, transcribed or wired to a real meeting.

What was decided

The ruling, in the order the surfaces below implement it.

  • §1, 2, 3Two settings, inherited organisation → workspace → organiser. “AI agents in meetings (live)” defaults on. “Agents remember meetings” defaults off; the organisation may set it on and lock it; workspace admins may disable what is not locked; the organiser decides per meeting within what is allowed. DMs and groups follow organisation policy.
  • §4, 5Live mode is silent: no prompt, no banner, no consent dialog. The meeting info panel states “AI assistance on”. One transcript per meeting, captured once, ephemeral — agents answer live from it and it is gone at meeting end.
  • §6Remember mode keeps one compacted memory belonging to the meeting, which belongs to the chat or channel. Participant-readable, organiser-deletable; agents read it by access and never hold private copies.
  • §7The organiser can delete that memory.
  • §8Explicit recording implies transcribing, and keeps the raw transcript with the meeting under the same access rule.
  • §2A workspace can be created as, or converted to, confidential; all AI in it — agent turns and transcription — is forced through the confidential door. Non-confidential transcription goes to our own endpoint as a first-party processor.
  • §5Personal agents are never in the participant list; coworker agents may be, if the call is in a channel that houses them.

1. Organisation settings · Tomorrow

Implements: Two settings, inherited org → workspace → organiser. Live defaults on, remember defaults off, and the org may set remember on and lock it.

AI in meetings

AI agents in meetings (live)Agents can answer from what is being said while the meeting runs. The transcript is discarded when the meeting ends.
Agents remember meetingsAfter the meeting, one compacted memory is kept with the meeting, readable by its participants.

2. Workspace settings · Product

Implements: Workspace admins may disable what the org allows. A workspace can be created as, or converted to, confidential — which forces every AI call in it through the confidential door.

AI in meetings

AI agents in meetings (live)Agents can answer from what is being said while the meeting runs.Inherited from Tomorrow · On
Agents remember meetingsOne compacted memory kept with the meeting after it ends.Turned off by Tomorrow, so this workspace cannot turn it on

Confidentiality

This workspace isStandard

Product is standard.

AI calls in this workspace go to our own endpoint as a first-party processor. Converting sends them through the confidential door instead.

…and the same property at creation time

The new workspace starts standard and can be converted later.

3. Scheduling a meeting

Implements: The organiser decides per scheduled meeting, within what the org and workspace allow.

Q3 roadmap review

This meeting is in

Agents can answer from what is being said. The transcript is discarded when the meeting ends.

Turned off by Tomorrow for every workspace, so it cannot be turned on here.

4. Meeting info panel

Implements: Live mode is silent — no prompt, no banner, no consent dialog. The info panel is the one place it is stated.

Meeting info

AI

AI assistance on

Agents can answer from what is being said during this meeting. Nothing is kept once the meeting ends.

No prompt, no banner and no consent dialog appear in the meeting itself. This panel is the single statement, which is what the ruling asks for.

5. During the meeting

Implements: One transcript per meeting, captured once, ephemeral; agents answer live from it; personal agents are never in the participant list.

Participants

  • CanOrganiser
  • Alex
  • Jordan
  • Riley
  • Roadmap botCoworker agentLives in #product

Can's personal Holoh is answering questions in this meeting and is deliberately absent from this list: a personal agent is never a participant. The coworker agent is listed because this call is in a channel that houses it.

Transcript

Ask about this meeting

Can10:05

Recap this meeting so far.

Holoh10:05

Two of four roadmap items shipped last week. The remaining two are blocked on the import path, and Riley said they would take it this week. About 12 seconds of audio were missing.

Answered from this meeting's own transcript.

6. After the meeting, in the chat

Implements: One compacted memory belonging to the meeting, which belongs to the chat or channel: participant-readable, agents read it by access.

#product · Q3 roadmap review

Reading as
Alex09:58

Starting now — joining the call.

Nothing was kept: this meeting ran without “Agents remember meetings”.

7. Deleting the memory

Implements: Organiser-deletable.

What the organiser is asked

This meeting kept no memory, so there is nothing to delete.

This meeting kept no memory, so the question is never asked. Turn on “Agents remember meetings” to see it in the state it is actually asked in.

What is left behind

A tombstone stays in the conversation. Shared content vanishing without trace reads as a bug to the people who saw it, and it hides that an organiser acted.

Preview — not in the conversation yet

The meeting memory was deleted by Can.

Open question for sign-off: tombstone, or remove it silently? The ruling does not say. This mock shows a tombstone.

8. When the meeting is recorded

Implements: Explicit recording implies transcribing, and keeps the raw transcript with the meeting under the same access rule.

Compacted memory

What remember mode keeps
  • Two of four roadmap items shipped last week; the other two are blocked on the import path.
  • Riley is taking the import path this week.
  • The scheduling change waits for the next cycle.
  • About 12 seconds of audio were missing.

What survives the meeting: 4 lines. Who said what is gone.

Raw transcript

What recording additionally keeps — same access rule

10:01 Alex: Thanks for joining — let's start with where the roadmap stands.

10:02 Jordan (uncertain attribution): Two of the four items shipped last week.

— missing audio, about 12 seconds —

10:04 Riley: The remaining two are blocked on the import path.

10:05 Riley: I'll take the import path this week.

10:06 Alex: Then the scheduling change waits for the next cycle.

Every word that was heard, attributed and timestamped, and an explicit marker wherever audio was missing.

Recording is the only mode that keeps the raw text. Live mode keeps nothing; remember mode keeps the 4 lines on the left. Both panels show the artifacts themselves so they can be compared — neither is a render of one viewer's screen, and the access rule is the same for both: only the meeting's participants can read either.
Surface