meeting-ui
<!-- Steering for the Meeting Canvas author. This file is the UI contract for the generated meeting view. Edit views/meeting.tsx,…
<!-- Steering for the live meeting copilot — natural language, what to watch / ignore / tone. This whole body is merged into the copilot prompt. Edit it to tune behavior. --> Highlight the people, companies, and products/technologies mentioned by name — the keywords worth
> /plugin marketplace add Vexa-ai/vexa > /plugin install vexa@vexa
How it fires
How this agent gets triggered: by you, by Claude, or both.
Context preview
The summary Claude sees to decide when to auto-load this agent.
<!-- Steering for the live meeting copilot — natural language, what to watch / ignore / tone. This whole body is merged into the copilot prompt. Edit it to tune behavior. --> Highlight the people, companies, and products/technologies mentioned by name — the keywords worth
enabled: true
# model: <any provider route> # unset = the deployment default (VEXA_MEETING_MODEL / VEXA_LLM_MODEL);
# # a free string passed to the provider; VEXA_MODEL_ALLOWLIST can gate it
cadence_segments: 4 # run a copilot beat every N completed segments (or on a new speaker)
card_kinds: [person, company, product]
write_meeting_doc: true # author the post-meeting kg entity on session_end
# ── Workspace-GOVERNED policy (prompt-only governance) ──────────────────────────────────────────────
# These two rules are the live POLICY for the copilot. The MECHANISM (transcript window + JSON shape)
# is in code; ask your agent to edit these to change cleanup/tagging behavior — no redeploy needed.
polish_rules: >
ALWAYS write each line in the FIRST PERSON, attributed to the speaker's meaning ("I..."); for plain
facts, state the fact directly ("Anthropic released..."). Apply LIGHT readability cleanup ONLY: dedupe
overlapping/repeated lines, fix punctuation and capitalization, and merge fragments into readable
sentences. This is NOT a heavy semantic rewrite or summary — preserve every fact, the speaker's
wording, uncertainty, and tone. Remove filler, false starts, and obvious transcript/model artifacts.
Do NOT invent missing content. Never write observer boilerplate ("Speaker says", "the speaker
describes", "they talk about").
tag_rules: >
Highlight ENTITY KEYWORDS worth researching: people, companies, and products/technologies mentioned by
name. Surface only concrete named entities present in the lines — do not invent. Do NOT tag signals
(decisions, action items, questions, claims) or plain numbers; entities only.<!-- Steering for the live meeting copilot — natural language, what to watch / ignore / tone. This whole body is merged into the copilot prompt. Edit it to tune behavior. --> Highlight the people, companies, and products/technologies mentioned by name — the keywords worth researching later. Nothing else. Keep the transcript neutral and concise.
Open-source meeting bots and real-time transcription — cloud or fully self-hosted.
<!-- Steering for the Meeting Canvas author. This file is the UI contract for the generated meeting view. Edit views/meeting.tsx,…