Meeting Agent

Paste a meeting URL and the agent joins the call. Ask it questions live during the meeting, and after it ends a fresh Brief lands in Hamster — with the transcript, summary, decisions, and follow-ups already wired into your Context Graph.

Overview

The Meeting Agent turns spoken context into a first-class Hamster artefact. You hand it a meeting link from Google Meet, Zoom, or Microsoft Teams. It joins the call, records the transcript, and once the meeting ends it generates a structured AI summary, creates a Brief and document, links it to the right Initiative, and posts a notification back to the channel where you started.

This is the input pipe most aligned with how founders already work: "I talk to customers, then I build." Customer calls and team meetings are the highest-signal source of refinement context — and historically the hardest thing to get into Hamster. The Meeting Agent closes that gap. It also reinforces the way teams capture interviews and customer stories: those conversations get a structured home rather than dying in Notion or Otter.

The flow is asynchronous and fault-tolerant. Each stage — agent dispatch, transcript fetch, summary generation, Context Graph linking, Slack notification — runs as its own job with retries, so a transient failure on one step doesn't drop the whole capture.

How It Works

Submit a meeting URL — Open the command palette (Cmd+K) and pick Join Meeting, or use the Hamster Slack bot. Paste the meeting link and click Join.
The agent joins the call — The Meeting Agent connects within seconds, appears as a participant, and records audio for the duration of the call. When voice is enabled for your workspace, the agent can also respond to questions live — ask it about your Briefs, Initiatives, or Tasks without leaving the call.
The meeting ends — When the call wraps, the agent leaves automatically. No "save before quit" step.
Transcript and summary land — A few minutes later, Hamster pulls the transcript and runs it through structured AI summary generation. The output includes a meeting title, identified participants, decisions, action items, strategic insights, and a concise markdown summary.
A Brief appears in your workspace — Hamster creates a Brief and document seeded with the summary. The Brief is linked to mentioned Initiatives and Tasks in your Context Graph automatically, so it shows up in the right places.
Slack pings you — If you started from Slack, the notification posts as a thread reply in the originating channel. Otherwise it lands in your default notifications surface. The ping includes the meeting title, top action items, decision count, and a deep link to the full summary in Hamster.

Ask Hamster During the Call

When voice is enabled for your workspace, the Meeting Agent becomes a two-way participant. While the meeting is running, you can speak directly to the agent and it responds out loud — drawing on the same context as the Hamster AI assistant: your Briefs, Initiatives, Tasks, Blueprints, and Methods.

This is the difference between having Hamster capture a meeting and having it in the room. On a customer call, you can ask "What tasks are open for the onboarding initiative?" without switching windows or losing your focus on the conversation. In a team standup, you can say "What did we decide about the API redesign?" and the agent responds in a few words.

Other participants hear the agent's responses, so it contributes naturally to the conversation rather than being a silent recorder.

This feature may need to be enabled for your workspace. Contact your workspace admin.

What the Summary Captures

Every meeting summary is structured so your Context Graph can use it:

Meeting title — A short, human-readable name.
Participants — Speakers identified from the transcript, with a total participant count.
Action items — Each with a Task, optional owner, and optional due date.
Decisions — What was decided, and which participants were involved.
Insights — Strategic themes, risks, and opportunities surfaced in the call.
Overall tone — A short read on the conversation's sentiment, so you can tell at a glance whether a customer call went well or a team discussion was tense.
Mentioned Initiatives and Tasks — Names and IDs that fuzzy-match into your existing Initiatives and tasks.

The full transcript is preserved alongside the summary, so you can always go back to the raw conversation.

Where Transcripts Land

Each meeting becomes a Brief in your workspace, and the document inside that Brief holds the formatted summary. The transcript itself lives on the Brief and can be referenced by the AI when answering questions about the meeting.

Mentioned Initiatives are matched against your existing Initiative titles. When there's a hit, the new Brief is linked to that Initiative — so the meeting shows up under the right strategic theme without anyone wiring it manually. Mentioned Tasks are linked the same way.

This means a customer call about your onboarding redesign automatically appears connected to the Onboarding Initiative, and the action items reference the right tasks.

Starting from Slack

If you have the Slack bot connected, you can dispatch the Meeting Agent directly from a channel or DM. The summary notification posts as a thread reply in the same conversation, so the Slack thread becomes a permanent record of the meeting and its outcomes — with a deep link back to the full Brief in Hamster.

If the originating thread is no longer accessible, the notification falls back to a fresh post in the channel.

Privacy and Security

Workspace admins control the agent. Only users with workspace settings.manage permission can dispatch a Meeting Agent. Other roles can read the resulting Briefs once they're created.
Credentials are encrypted. API keys for the meeting provider are stored in the Hamster vault and never appear in job payloads, logs, or client responses.
Meeting URLs are not logged. Meeting links can contain join codes and passcodes, so Hamster only logs the hostname for debugging.
Webhooks are signed. Inbound transcript events are verified with a timing-safe HMAC check, so only your meeting provider can deliver transcripts back to your workspace.
Standard team permissions apply. Meeting Briefs follow the same role-based access rules as any other Brief — only members of your Hamster team can read them.

Tell participants the agent is recording. Most meeting providers also display a recording indicator while the agent is in the call.

Supported Meeting Providers

The Meeting Agent accepts URLs from:

Google Meet
Zoom
Microsoft Teams

URLs are validated client-side before the agent is dispatched, so you'll see an error immediately if you paste a link from an unsupported provider.

Tips

Submit the URL a minute or two before the meeting starts so the agent has time to join. Joining late is fine — the agent records from the moment it connects.
Keep meeting names in your calendar consistent with Initiative names. The summary's "mentioned Initiatives" matcher fuzzy-matches against Initiative titles, so consistent naming improves auto-linking.
Use the Slack dispatch path for customer calls. The thread reply gives non-Hamster stakeholders a one-click way to read the full summary without an account switch.
When voice is enabled, use it to look up context mid-call rather than switching windows. Keep questions short and direct — "What tasks are open for the onboarding initiative?" works better than a long compound question. Other participants will hear the response.
If a transcript fails to process, check the Brief — failure state is captured on the Brief itself with the last error, and you can re-dispatch from the same meeting URL.