room_header — Claude Code prompt: setup and installation
The room_header prompt for Claude Code sets the context at the start of a meeting room. It passes along the title, start time, language, and assistant role.
MIT ★ 395 updated 2026-11-16
.claude/commands/room_header.mdWhat room_header does
The prompt builds the meeting room’s opening message and places context in a persona-context block. It includes the uploaded meeting’s title, the calendar hint from the message source, the start date and time in the user’s time zone, the language, and the role. Calendar location and invitees are added when present in the calendar context.
The selected role controls the assistant’s behavior. A participant may answer aloud; a listener displays answers on screen; the notes role records topics and highlights. In notes mode, the assistant asks no questions until the role changes. A calendar entry matched from the knowledge base does not replace the hint from the message source.
To install it in Claude Code, place the file at .claude/commands/room_header.md. The prompt tells the assistant to produce no text when the meeting starts.
What it helps with
- pass the uploaded meeting title and calendar hint to the assistant
- add the start time in the user’s time zone
- set the meeting room’s language and assistant role
- switch between note-taking and participant or listener behavior
Example prompts for the agent
- Set up the context for a meeting room.
- Set the meeting room to notes mode in English.
- Configure the meeting room for the participant role.
How to install room_header
Manually: put the files in place
.claude/commands/room_header.mdHow to use
Paste the text at the start of a chat or into project instructions
Questions about room_header
How do I install room_header in Claude Code?
Create .claude/commands/room_header.md and put the prompt contents in that file.
What does room_header do?
It prepares the meeting room’s opening context with its title, start time, language, and assistant role. In notes mode, the assistant records topics and highlights without asking questions until the role changes.
How does room_header behave with different roles?
A participant may answer aloud, a listener displays answers on screen, and the notes role records topics and highlights.
Source text
room_header.md · MIT
{{- /* The first message of a meeting's room (docs/assistant/meeting-minutes.md "Its first message"), message source
meeting: the upload's title and calendar hint (never the knowledge base's matched calendar item), the date and start
time in the user's zone, the language and the role (notes, #8851: no questions come until it changes). Every text through ctx. */ -}}
The meeting is starting. Write nothing now.
<persona-context kind="context" title="{{attr .Title}}" url="">
Title: {{ctx .Title}}
{{with .Calendar}}{{with .Title}}Calendar: {{ctx .}}
{{end}}{{with .Location}}Where: {{ctx .}}
{{end}}{{with .Attendees}}Invited: {{range $i, $a := .}}{{if $i}}, {{end}}{{ctx $a}}{{end}}
{{end}}{{end}}Started: {{.Started}}
Language: {{.Language}}
Role: {{if eq .Role "participant"}}participant: answers may be said aloud{{else if eq .Role "notes"}}notes: you keep the topics and highlights only, and nobody asks you anything until the role changes{{else}}listener: answers are shown on screen only{{end}}
</persona-context>
© nwverse · MIT · nwverse/persona