# Step-by-step scenarios (/en/docs/memo/scenarios) Each scenario is a common task in order: the commands to run, why each one runs and what to look at in the answer. The same scenarios are in the terminal: `memo guide` lists them and `memo guide ` prints one. ## What did we decide about X, across every source [#what-did-we-decide-about-x-across-every-source] Find the decision on one topic and the evidence for it in notes, mail, messages, meetings and documents, then record it once. 1. ```sh memo facts list kind:decision project:HRB ``` decisions already recorded for the project, each with the evidence it cites 2. ```sh memo search all venue ``` messages, mail and notes that mention the topic, ranked together 3. ```sh memo search meetings venue ``` what was said about it in meetings, with the passage to cite 4. ```sh drive search venue ``` Drive documents about it; drive commands start with your profile, as in drive personal search venue 5. ```sh memo ask "what did we decide about the venue?" --all ``` the cited evidence in one bundle, for you or your agent to read 6. ```sh memo facts add "The team day is at the harbour venue" --kind decision --evidence msg:telegram/1/77/42 --project HRB ``` keep the decision with its source, so the next search finds it first What to look at: * the newest decision and who made it * later messages or meetings that reverse it * whether the recorded decision cites the source you found In the terminal: `memo guide decision-trail` ## One person across every tool [#one-person-across-every-tool] Know everything about one person before a call — messages in tg and MAX, mail, notes, meetings and Drive documents — with a source for each line. 1. ```sh memo context telegram:Kai ``` their messages, mail, notes and open tasks in one answer, each with a link to its source; email:[kai@example.com](mailto:kai@example.com) finds them by address 2. ```sh memo facts list subject:"person:42" ``` decisions, promises and questions already recorded about them; the person reference comes from context's answer 3. ```sh memo memories list subject:"person:42" ``` preferences and summaries kept about them 4. ```sh memo search meetings Kai ``` meetings that mention them, with the passage to cite 5. ```sh tg contacts context Kai ``` shared Telegram chats, the last messages each way and where others mentioned them; tg, max and drive commands start with your profile, as in tg personal contacts context Kai 6. ```sh max contacts context Kai ``` the same for MAX 7. ```sh zm meetings context person:42 ``` what stored Zoom meetings say about them, through the identities linked to that person 8. ```sh drive search Kai ``` Drive documents that name them 9. ```sh memo ask "what is open with Kai?" --all ``` one cited evidence bundle across every account and the notes, ready to hand to your agent What to look at: * open tasks and promises, both ways * the last contact in each channel, and who wrote last * decisions recorded about them, and anything newer that contradicts one * documents worth rereading before the call memo joins what the store already holds; the other tools add what only they read. Every step reads — nothing is sent and nothing changes. In the terminal: `memo guide person-brief` ## Prepare for a meeting [#prepare-for-a-meeting] Walk into a recurring meeting knowing what was said last time, what is still open and what the project's documents say. 1. ```sh memo meetings prepare 85012345678 --source zoom --project HRB ``` earlier occurrences, their cues and the related messages and mail, each with a source 2. ```sh memo meetings actions list status:proposed --source zoom ``` follow-ups staged from earlier meetings that nobody reviewed 3. ```sh memo projects context HRB ``` the project's key documents first, then its notes, findings and open tasks 4. ```sh memo ask "what is still open for the Harbour kickoff?" --all ``` one cited bundle across every account and the notes, for your agent to draft an agenda from What to look at: * promises from the last occurrence and whether they were kept * open tasks with no owner * the time of the next meeting, which preparation does not verify In the terminal: `memo guide prepare-meeting` ## Set up memo [#set-up-memo] Get notes and mail into the local store, keep it fresh, and let your agent read it. 1. ```sh memo folders add ~/notes ``` gives your notes folder an id; memo never changes the files 2. ```sh memo sync --only notes ``` imports the notes now; mail accounts come from the mail.accounts setting 3. ```sh memo auto start ``` syncs notes and mail every 5 minutes from now on 4. ```sh memo doctor ``` where memo keeps its files and what needs attention; it connects to nothing 5. ```sh memo skill install --for all ``` teaches Claude Code, Codex and Gemini CLI how to use memo What to look at: * what doctor says needs attention * whether search by meaning is on, or words only In the terminal: `memo guide set-up` ## Start the day [#start-the-day] See what needs you today and what agents did overnight, without reading every chat or mailbox. 1. ```sh memo auto status ``` whether the timer synced notes and mail lately; a failed run is named here 2. ```sh memo tasks agenda ``` tasks overdue or due, chats where you owe an answer and chats where you wait for one 3. ```sh memo actions list status:proposed ``` replies and invitations agents proposed, waiting for your yes or no 4. ```sh memo facts list status:proposed ``` facts agents recorded that you have not confirmed 5. ```sh memo agents log --limit 20 ``` every tool call an agent made, never with its arguments What to look at: * the oldest unanswered chat * tasks due today * proposals to confirm or reject before an agent builds on them In the terminal: `memo guide start-the-day`