# Step-by-step scenarios (/en/docs/max/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: `max guide`[↗](/llms.mdx/docs/max/commands-personal/content.md#max-guide "Command reference: max guide") lists them and `max guide <name>`[↗](/llms.mdx/docs/max/commands-personal/content.md#max-guide "Command reference: max guide") prints one.

Commands that use an account start with your profile, the name you gave the account at login: `max <profile> …`.

## Let an agent read MAX on a timer [#let-an-agent-read-max-on-a-timer]

Get a summary of what needs your answer every morning, from an agent that cannot send.

1. ```sh
   max schedule command sync-chats --every 2h -- messages sync --all
   ```

   keeps every chat's history in the local store up to date, so the agent reads it offline

2. ```sh
   max schedule agent morning claude "run the daily follow-up review: max skill show follow-ups" --at 08:30
   ```

   starts the agent at 08:30 with MAX_READ_ONLY=1, so it reads and drafts and never sends

3. ```sh
   max schedule list
   ```

   when each schedule runs next and how its last run went

What to look at:

* the last run's status for both schedules
* the agent's kept answer, and the notification that it is ready

The agent runs under the lock, so any send it tries is refused before MAX is reached. Remove a schedule with
`max schedule remove <name>`[↗](/llms.mdx/docs/max/commands-personal/content.md#max-schedule-remove "Command reference: max schedule remove").

In the terminal: `max guide agent-on-a-timer`[↗](/llms.mdx/docs/max/commands-personal/content.md#max-guide "Command reference: max guide")



## Catch up after a day away [#catch-up-after-a-day-away]

Know who waits on you and what you promised, without opening every chat.

1. ```sh
   max review 'date>1d' --unanswered 4h
   ```

   questions to you that nobody answered for four hours, across every chat

2. ```sh
   max inbox --new
   ```

   other people's messages that arrived since your last check, each one once

3. ```sh
   max tasks list
   ```

   questions, requests and promises the review kept, oldest first

What to look at:

* who asked first and how long ago
* tasks whose source message is a promise of yours

`review`[↗](/llms.mdx/docs/max/commands-personal/content.md#max-review "Command reference: max review") and `inbox`[↗](/llms.mdx/docs/max/commands-personal/content.md#max-inbox "Command reference: max inbox") read MAX and save what they read, so `tasks list`[↗](/llms.mdx/docs/max/commands-personal/content.md#max-tasks-list "Command reference: max tasks list") and later searches work from the local
store. Add `--offline` to any of them to read only what is already saved.

In the terminal: `max guide catch-up`[↗](/llms.mdx/docs/max/commands-personal/content.md#max-guide "Command reference: max guide")

## Find what someone said [#find-what-someone-said]

Get back a message, a file or a voice note when you remember only a word or the person.

1. ```sh
   max search all "invoice"
   ```

   messages, notes, the text of files and voice transcripts in one search, best match first

2. ```sh
   max contacts timeline Anna
   ```

   everything one person wrote or was mentioned in, newest first, from the store

3. ```sh
   max messages context Team 1234
   ```

   the message a hit points to, with what came either side of it

What to look at:

* the chat and the time of each hit
* the msg locator, to cite it or to open the message

A search finds only what the store holds. Run `max messages sync --all`[↗](/llms.mdx/docs/max/commands-personal/content.md#max-messages-sync "Command reference: max messages sync") once, or `max schedule command`[↗](/llms.mdx/docs/max/commands-personal/content.md#max-schedule-command "Command reference: max schedule command") on a timer,
so older history is there to find.

In the terminal: `max guide find-what-was-said`[↗](/llms.mdx/docs/max/commands-personal/content.md#max-guide "Command reference: max guide")



## Post as your bot [#post-as-your-bot]

Send a message to a group as your bot, through MAX's official Bot API, not from your own account.

1. ```sh
   max bot auth set
   ```

   checks the bot's token with MAX and keeps it; type it at the hidden prompt or pipe it on stdin

2. ```sh
   max bot chats list
   ```

   the chats this bot has seen on this machine, to pick the one to write to

3. ```sh
   max bot messages send Team "the release is out"
   ```

   sends the message as the bot; without the text it is read from stdin

What to look at:

* which bot `bot auth set`[↗](/llms.mdx/docs/max/commands-bot/content.md#max-bot-auth-set "Command reference: max bot auth set") names, before anything is sent
* the message id the send returns, to edit or pin it later

A bot needs its own token from MAX; your personal login is not used. `max bot recipients add`[↗](/llms.mdx/docs/max/commands-bot/content.md#max-bot-recipients-add "Command reference: max bot recipients add") limits which chats the
bot may write to.

In the terminal: `max guide post-as-a-bot`[↗](/llms.mdx/docs/max/commands-personal/content.md#max-guide "Command reference: max guide")

## Works with other tools [#works-with-other-tools]

These Memo scenarios also use `max`:

* [One person across every tool](/llms.mdx/docs/memo/scenarios/content.md#person-brief): `memo guide person-brief`