> ## Documentation Index > Fetch the complete documentation index at: https://docs.tiro.ooo/llms.txt > Use this file to discover all available pages before exploring further. # Tiro Prompt Library > Prompts that turn what you captured in Tiro into real output through Claude Code, Codex, and Claude Desktop. Copy any of them and paste as is. Treat Tiro not as just a meeting recorder but as **the thing that feeds your AI agent**, and the story changes completely. Here are prompts, grouped by situation, that let an agent read what you said out loud, organize it, and act on it. Use the copy button on the right of each code block and paste it as is. Replace bracketed placeholders like `` or `` with your own. MCP and CLI are **included on every plan at no extra cost**. They work during your free trial too. ## Connect Tiro first Before any prompt works, connect Tiro to your agent once. Both routes are a single paste, after which the agent installs and signs in on its own. | Route | Where you use it | Guide | | ------------ | ------------------------------------------------------------ | ------------------------------------------------------------- | | **Tiro CLI** | Coding agents with a shell (Claude Code, Codex, and similar) | [Install the CLI with one prompt](/en/developers/cli/install) | | **Tiro MCP** | Claude Desktop, ChatGPT, Cursor, VS Code, and similar | [Install MCP with one prompt](/en/developers/mcp/install) | *** ## If you have meetings often Once meeting records pile up, they become an asset right away. ### Use the Tiro CLI in Claude Code and Codex **Extract action items and run them** ``` Read my most recent meeting note in Tiro and list everything we said we would look into and every piece of data we said we would pull. Then start working through them in this repository, easiest first. ``` **Apply meeting decisions to the code** ``` Read today's meeting note in Tiro and find every behavior change we agreed on. For each change, find the files in this repository that need editing and show me the list, then make the edits one at a time as I approve them. ``` **Check what you dropped** ``` Pull all of my meeting notes from the last month in Tiro and extract everything I said I would do. Keep only the items you cannot find a trace of in this repository's commit history or issues. ``` ### Use Tiro MCP in Claude Desktop and ChatGPT **Build reporting material** ``` Find all of my meeting notes from the last 2 weeks in Tiro and put the recurring issues and the still-unresolved items into a table. Then write a one-page summary I can report from. ``` **Draft a weekly update** ``` Find all of my meeting notes from this week in Tiro and draft a weekly update. Use three columns: done, next week, blocked. Tag each item with the meeting it came from, and do not add anything that was not said in a meeting. ``` **Trace how a decision moved** ``` Find every meeting in Tiro where pricing came up and lay out, in order, how the decision changed over time. Mark which meeting each item came from. ``` **Turn a customer meeting into a proposal outline** ``` Find the meeting note in Tiro and separate the problems the customer described from what we offered. Then outline a proposal from that. Do not invent requirements the customer never mentioned. ``` **Draft the follow-up email** ``` Find today's customer meeting note in Tiro and draft the follow-up email. Include everything we committed to and every deadline, and do not write anything as settled that we did not settle. If that note already has a share link, add it at the end of the email. ``` MCP can **look up a share link that already exists**. Creating one is done in the app or through the [API](/en/developers/fundamentals/api-overview). **See who took on what** ``` Find all of my meeting notes from this week in Tiro and organize what each attendee took on. Group the items with no clear owner under "unassigned". ``` *** ## If you rarely have meetings Tiro earns its place even without meetings. The point is to **say things out loud instead of typing them**. ### Turn videos and talks into raw material Play a video on your desktop app and let Tiro capture it. Tiro picks up the sound coming out of your computer, so you can do something else while it records. Say your own thoughts out loud as you go and the video and your commentary land in the same note. Capturing your computer's sound requires the **desktop app**. On Mac, grant the system audio recording permission once. See [Recording video call and media audio](/en/guide/recording/system-audio) for details. **Separate the video's points from your own** ``` Use the Tiro CLI to pull the note I just recorded, then separate the claims made in the video from the comments I added along the way. Then propose 3 experiments worth trying, based on my comments. ``` **Read several videos as one topic** ``` Use the Tiro CLI to pull all of my notes from the past week, then collect the claims that repeat across videos and the ones that contradict each other. For each contradiction, tell me which side has the stronger evidence. ``` **Turn what you watched into writing** ``` Use the Tiro CLI to pull the notes I recorded today, then draft a blog post built around the comments I added. Use the video content as background only, and keep my point of view in the lead. ``` ### Code by talking Turn Tiro on and let the ideas spill out. It feels odd the first time, then it clicks. Brainstorming flows far better than it does while typing, and you get many more ideas out. This only needs your microphone, so you can try it **on the web with nothing installed**. **Build what you just said** ``` Use the Tiro CLI to pull the note I just talked through, drop the duplicates, and group what is left by topic. Pick the one most worth building and prototype it in this repository. ``` **Turn rambling into a spec** ``` Use the Tiro CLI to pull my latest note and write up what I said as feature requirements. Anything I did not say but that still needs a decision, pull out separately as an open question. Do not fill gaps with guesses. ``` **Talk your way through a stuck problem** ``` Use the Tiro CLI to pull my latest note. Read how I understand this problem and point out any assumption of mine that is wrong or unverified. Then confirm or refute each one against the code in this repository. ``` ### Digest lectures, podcasts, and audiobooks ``` Use the Tiro CLI to pull the note I recorded yesterday and write it up as a concept summary someone new to the subject could follow. Flag separately anything I seem to have glossed over without understanding. ``` ### Build up research notes Say each thought out loud as it comes while you read, and later an agent pulls the scattered notes into one thread. No repository needed, so this works even if you never touch code. **Gather everything you have said on one topic** ``` Use the Tiro CLI to find every note from the last 30 days that mentions "". Across those notes, separate what I said repeatedly from where my thinking changed, and tag each item with the date of the note it came from. ``` **Keep only the questions you have not answered** ``` Use the Tiro CLI to pull all of my notes from the last month and extract only the questions I raised and never answered. Drop the ones already resolved, and sort what remains from easiest to answer. ``` ### Draft content Something you said once can be reused in several shapes. Hand over a batch of notes and the agent finds the threads worth pulling. **Find story ideas across scattered notes** ``` Use the Tiro CLI to pull all of my notes from the last 2 weeks and pick 3 topics that could each become a single piece of writing. For each topic, show me which note and which passage you based it on. ``` **Outline a series quoting only what you said** ``` Use the Tiro CLI to pull every passage about "" from my notes in the last 2 weeks, then outline a 3-part series. Quote my own words from the notes exactly as they appear, and do not invent anything I did not say. ``` ### Run your own retrospective ``` Use the Tiro CLI to pull all of my notes from the last 2 weeks and extract the worries I kept returning to and the things I never settled. Do not judge them, just show me what is there. ``` *** ## What makes prompts work better **Name the note and the results improve.** If the agent keeps grabbing the wrong note, run `tiro notes list --limit 5` to see the list first and point it at a specific note. The full command reference is in the [CLI quickstart](/en/developers/cli/quickstart). **If you want to block guessing, say so.** Adding one line, "if it is not in the note, do not make it up, mark it as not in the note", makes the output far more trustworthy. **Narrowing the time range sharpens the answer.** Phrases like "the last 2 weeks", "yesterday", or "this month" shrink the pool of notes the agent digs through, so fewer irrelevant ones slip in. Registering names, companies, and jargon before you record makes names come out far more accurate. See [Note context](/en/guide/recording/context) and [Wordbook](/en/guide/recording/wordbook). ## Frequently asked questions **Do I need a paid plan to use these prompts?** No. MCP and CLI are included on every plan at no extra cost, and they work during your free trial. **Can I use these without a coding agent like Claude Code?** Yes. Connect MCP to Claude Desktop or ChatGPT and most of the "If you have meetings often" prompts on this page work as is. Only the prompts that edit a repository need a coding agent. **The agent says it cannot find my notes.** Check that the connection is still live. Then narrow the scope by putting a time range or a note title directly in the prompt, which resolves most cases. If it still fails, see the search options in the [CLI quickstart](/en/developers/cli/quickstart). **Can the agent listen to the original audio?** The agent only receives the transcribed text. To work with the audio file itself, use the [API](/en/developers/fundamentals/api-overview). ## See also * [API · MCP · CLI](/en/guide/notes/api-mcp-cli) * [MCP tool reference](/en/developers/mcp/tools/overview) * [CLI quickstart](/en/developers/cli/quickstart) * [CLI guide for AI agents](/en/developers/cli/agent-guide)