See what your
agent can do.

A meeting brief, a better follow-up, a file you couldn’t find. Follow the conversation and inspect the messages behind each answer.

Start with a task you recognise.

These worked conversations show how you could use WireCat with your own agent. Choose a task, follow the exchange and inspect the commands or source messages behind the answer. Copy a request to try it with your own conversations.

Choose a task

Prepare for a call

An agenda assembled from the relevant chats

Use tg cli, gather context for tomorrow’s Atlas call: decisions, risks and questions.

Your agent uses the connected tools

tg chats list --search "Atlas"

Tool output · JSON

{
  "items": [
    {
      "id": "101",
      "title": "Atlas · team",
      "kind": "group"
    },
    {
      "id": "102",
      "title": "Atlas · design",
      "kind": "group"
    }
  ],
  "hasMore": false
}

1 more call

tg review --chat "Atlas · team" --since-time 7d

Tool output · JSON

{
  "chats": [
    {
      "title": "Atlas · team",
      "messages": [
        {
          "id": "48210",
          "senderName": "Anna",
          "text": "We’re launching on Friday.",
          "timestamp": "2026-10-02T09:00:00Z"
        },
        {
          "id": "48211",
          "senderName": "Marco",
          "text": "Anna needs the final copy by Thursday.",
          "timestamp": "2026-10-02T09:00:00Z"
        },
        {
          "id": "48212",
          "senderName": "Tom",
          "text": "Tom needs staging access.",
          "timestamp": "2026-10-02T09:00:00Z"
        }
      ],
      "more": false
    }
  ],
  "skipped": [],
  "partial": false
}

We’re aiming for Friday’s launch. Here’s what the project group has agreed:

Launch: Friday. The scope of the first release is agreed.
Copy: Anna needs the final version by Thursday.

Blocking the launch

Tom: needs staging access to test payments.

For the call

Agree who will provide access and when testing will be finished. I also found the design group — I can check it and your direct messages with the people involved.

Source messages

Anna #48210Atlas · team · Telegram · Oct 2, 2026

We’re launching on Friday.

Marco #48211Atlas · team · Telegram · Oct 2, 2026

Anna needs the final copy by Thursday.

Tom #48212Atlas · team · Telegram · Oct 2, 2026

Tom needs staging access.

Check the design group and my DMs with Tom too. He may have sent the results there.

Your agent uses the connected tools

tg review --chat "Atlas · design" --since-time 7d

Tool output · JSON

{
  "chats": [
    {
      "title": "Atlas · design",
      "messages": [
        {
          "id": "48210",
          "senderName": "Anna",
          "text": "The design is ready. We’re still waiting for the final copy.",
          "timestamp": "2026-10-02T09:00:00Z"
        }
      ],
      "more": false
    }
  ],
  "skipped": [],
  "partial": false
}

3 more calls

tg chats list --search "Tom"

Tool output · JSON

{
  "items": [
    {
      "id": "503",
      "title": "Tom",
      "kind": "private"
    }
  ],
  "hasMore": false
}

tg messages list 503 --limit 30

Tool output · JSON

{
  "items": [
    {
      "id": "48210",
      "senderName": "Tom",
      "text": "Test payments work. I still need access to production.",
      "timestamp": "2026-10-02T09:00:00Z"
    }
  ],
  "hasMore": false
}

tg search messages "Atlas" --chat 503 --language legacy

Tool output · JSON

{
  "items": [
    {
      "id": "48210",
      "senderName": "Tom",
      "text": "Test payments work. I still need access to production.",
      "timestamp": "2026-10-02T09:00:00Z"
    }
  ],
  "hasMore": false
}

The design group and your DMs fill in the picture:

Design: the layout is ready; final copy is the last dependency.
Tom, in your DMs: test payments work. He still needs access to production.

The remaining risk

Payment testing is partly done — only the production check is blocked. Focus the call on that, rather than starting from scratch.

Source messages

Tom #48210Tom · Telegram · Oct 2, 2026

Test payments work. I still need access to production.

Make a 20-minute agenda covering risks, owners and deadlines. Don't send anything.

Your agent uses the connected tools

tg messages context 503 48210 --before-n 2 --after-n 2

Tool output · JSON

{
  "items": [
    {
      "id": "48210",
      "senderName": "Tom",
      "text": "Test payments work. I still need access to production.",
      "timestamp": "2026-10-02T09:00:00Z"
    },
    {
      "id": "48211",
      "senderName": "Tom",
      "text": "I need access to production.",
      "timestamp": "2026-10-02T09:00:00Z"
    }
  ],
  "hasMore": false
}

20-minute agenda

0–7 min: production access — who will grant it, and when can Tom finish testing?
7–12 min: final copy — who will get it to Anna by Thursday?
12–17 min: if we run out of time, do we reduce scope or move the launch?
17–20 min: record an owner and deadline for each action.

Draft ready, based on the project group, design group and your DMs with Tom. Nothing has been sent.

Source messages

Tom #48210Tom · Telegram · Oct 2, 2026

Test payments work. I still need access to production.

Tom #48211Tom · Telegram · Oct 2, 2026

I need access to production.

Try a task like this with your own conversations.

Find recommendations

A comparison that uses the surrounding messages

Use tg cli, find SQL course recommendations across Telegram and MAX. I want exercises and feedback.

Your agent uses the connected tools

tg search messages "SQL" --source all --limit 10 --language legacy

Tool output · JSON

{
  "items": [
    {
      "id": "48210",
      "chatId": "601",
      "chat": "Analytics · community",
      "messenger": "tg",
      "date": "2026-10-02T09:00:00Z",
      "text": "Took a SQL workshop: weekly exercises and feedback from the instructor.",
      "timestamp": "2026-10-02T09:00:00Z",
      "senderName": "Daria"
    },
    {
      "id": "67210",
      "chatId": "701",
      "chat": "Team · learning",
      "messenger": "max",
      "date": "2026-10-02T12:00:00Z",
      "text": "The SQL video course helped with basics, but nobody reviewed my work.",
      "timestamp": "2026-10-02T12:00:00Z",
      "senderName": "Alex"
    }
  ],
  "hasMore": false
}

Two recommendations from different messengers

Workshop: reviewed exercises — closer to your requirements.
Video course: self-paced learning; feedback is not confirmed.

Found messages in a Telegram community and a MAX work chat. I’ll check the context of the reviews.

Source messages

Daria #48210Analytics · community · Telegram · Oct 2, 2026

Took a SQL workshop: weekly exercises and feedback from the instructor.

Alex #67210Team · learning · MAX · Oct 2, 2026

The SQL video course helped with basics, but nobody reviewed my work.

Read the messages around those recommendations. I want feedback on mistakes, not just videos.

Your agent uses the connected tools

tg messages context msg:telegram/900001/601/48210 --before-n 1 --after-n 1

Tool output · JSON

{
  "items": [
    {
      "id": "48210",
      "chatId": "601",
      "chat": "Analytics · community",
      "messenger": "tg",
      "date": "2026-10-02T09:00:00Z",
      "text": "Took a SQL workshop: weekly exercises and feedback from the instructor.",
      "timestamp": "2026-10-02T09:00:00Z",
      "senderName": "Daria"
    },
    {
      "id": "48211",
      "chatId": "601",
      "chat": "Analytics · community",
      "messenger": "tg",
      "date": "2026-10-02T09:00:00Z",
      "text": "The workshop reviews mistakes. Don’t expect advanced topics.",
      "timestamp": "2026-10-02T09:00:00Z",
      "senderName": "Daria"
    }
  ]
}

1 more call

max messages context msg:max/900001/701/67210 --before-n 1 --after-n 1

Tool output · JSON

{
  "items": [
    {
      "id": "67210",
      "chatId": "701",
      "chat": "Team · learning",
      "messenger": "max",
      "date": "2026-10-02T12:00:00Z",
      "text": "The SQL video course helped with basics, but nobody reviewed my work.",
      "timestamp": "2026-10-02T12:00:00Z",
      "senderName": "Alex"
    },
    {
      "id": "67211",
      "chatId": "701",
      "chat": "Team · learning",
      "messenger": "max",
      "date": "2026-10-02T12:00:00Z",
      "text": "Easy to watch at your own pace; I had to find practice exercises elsewhere.",
      "timestamp": "2026-10-02T12:00:00Z",
      "senderName": "Alex"
    }
  ]
}

What to check first

Start with the workshop: a participant confirms feedback on mistakes. Keep the video course as a self-paced alternative.

These reviews don’t establish the current syllabus, price or availability. Ask the organizers about assignment reviews and course level.

Source messages

Daria #48211Analytics · community · Telegram · Oct 2, 2026

The workshop reviews mistakes. Don’t expect advanced topics.

Alex #67211Team · learning · MAX · Oct 2, 2026

Easy to watch at your own pace; I had to find practice exercises elsewhere.

Try a task like this with your own conversations.

Follow up with context

A reply that reflects what has already happened

Use tg cli, find who needs my reply, what I promised and what I’m waiting on from others.

Your agent uses the connected tools

tg review --since-time 7d --all --unanswered

Tool output · JSON

{
  "chats": [
    {
      "title": "Atlas",
      "messages": [
        {
          "id": "48210",
          "senderName": "Anna",
          "text": "Marco: please confirm the budget.",
          "timestamp": "2026-10-02T09:00:00Z"
        },
        {
          "id": "48211",
          "senderName": "Marco",
          "text": "Customer: when is delivery?",
          "timestamp": "2026-10-02T09:00:00Z"
        }
      ],
      "more": false
    }
  ],
  "skipped": [],
  "partial": false
}

1 more call

tg review --since-time 7d --all

Tool output · JSON

{
  "chats": [
    {
      "title": "Atlas",
      "messages": [
        {
          "id": "48210",
          "senderName": "Anna",
          "text": "You: I’ll send Anna the invoice by Friday.",
          "timestamp": "2026-10-02T09:00:00Z"
        },
        {
          "id": "48211",
          "senderName": "Marco",
          "text": "Tom: I’ll send the design on Wednesday.",
          "timestamp": "2026-10-02T09:00:00Z"
        },
        {
          "id": "48212",
          "senderName": "Tom",
          "text": "Customer: Friday works for me.",
          "timestamp": "2026-10-02T09:00:00Z"
        }
      ],
      "more": false
    }
  ],
  "skipped": [],
  "partial": false
}

On your list

Anna: an invoice by Friday — that’s today.
Marco: a budget decision.
Customer: delivery confirmation.

Waiting on others

Tom: promised the design by Wednesday. I’ll check the other chats before drafting a reminder.

Ready to resolve

The delivery date is already agreed. The budget needs your decision; I won’t assume it’s approved.

Source messages

Anna #48210Atlas · Telegram · Oct 2, 2026

You: I’ll send Anna the invoice by Friday.

Marco #48211Atlas · Telegram · Oct 2, 2026

Tom: I’ll send the design on Wednesday.

Tom #48212Atlas · Telegram · Oct 2, 2026

Customer: Friday works for me.

Find Tom’s chat and check whether he already sent the design. Draft replies to the customer, Anna and Tom.

Your agent uses the connected tools

tg chats list --search "Tom"

Tool output · JSON

{
  "items": [
    {
      "id": "503",
      "title": "Tom",
      "kind": "private"
    }
  ],
  "hasMore": false
}

2 more calls

tg messages list 503 --limit 30

Tool output · JSON

{
  "items": [
    {
      "id": "48210",
      "senderName": "Tom",
      "text": "Here’s the first design draft. I’ll finalise it after your feedback.",
      "timestamp": "2026-10-02T09:00:00Z"
    }
  ],
  "hasMore": false
}

tg search messages "design" --chat 503 --language legacy

Tool output · JSON

{
  "items": [
    {
      "id": "48210",
      "senderName": "Tom",
      "text": "Here’s the first design draft. I’ll finalise it after your feedback.",
      "timestamp": "2026-10-02T09:00:00Z"
    }
  ],
  "hasMore": false
}

To the customer

Delivery is still set for Friday, as agreed. Please let me know if there’s a particular time that works best for you.

To Anna

Hi Anna! I’ll send the invoice today, as agreed.

To Tom

Tom, thanks for the first draft! When can you send the final version with our feedback incorporated?

Tom already sent a draft in your DMs, so saying he hasn’t sent anything would be wrong. All three replies are drafts.

Source messages

Tom #48210Tom · Telegram · Oct 2, 2026

Here’s the first design draft. I’ll finalise it after your feedback.

Send Tom that draft asking about the final design. Hold the other replies.

Your agent uses the connected tools

tg messages send 503 "Tom, thanks for the first draft! When can you send the final version with our feedback incorporated?"

Tool output · JSON

{
  "chatId": "503",
  "messageId": "48221",
  "status": "sent"
}

Sent to Tom

Asked about the final design in the direct chat we found. The customer and Anna replies remain drafts. The budget decision stays with you.

Source messages

Marco #48211Atlas · Telegram · Oct 2, 2026

Tom: I’ll send the design on Wednesday.

Tom #48212Atlas · Telegram · Oct 2, 2026

Customer: Friday works for me.

Tom #48210Tom · Telegram · Oct 2, 2026

Here’s the first design draft. I’ll finalise it after your feedback.

Try a task like this with your own conversations.

Get a morning briefing

Priorities from messages and a transcribed voice note

Use tg cli, show who is waiting for my reply and which updates from my subscriptions are worth reading.

Your agent uses the connected tools

tg inbox

Tool output · JSON

{
  "chats": [
    {
      "title": "Marco",
      "messages": [
        {
          "id": "48210",
          "senderName": "Marco",
          "text": "Approve the budget by 11:00 or the contractor cannot start.",
          "timestamp": "2026-10-02T09:00:00Z"
        }
      ],
      "more": false
    },
    {
      "title": "Anna",
      "messages": [
        {
          "id": "48211",
          "senderName": "Anna",
          "text": "The meeting moved to 19:30. Please confirm.",
          "timestamp": "2026-10-02T09:00:00Z"
        }
      ],
      "more": false
    },
    {
      "title": "Mum",
      "messages": [
        {
          "id": "8812",
          "senderName": "Mum",
          "text": "Voice note, 0:42",
          "timestamp": "2026-10-02T09:00:00Z"
        }
      ],
      "more": false
    }
  ],
  "skipped": [],
  "partial": false
}

1 more call

tg review --chat "Tech news" --since-time 1d --all

Tool output · JSON

{
  "chats": [
    {
      "title": "Tech news",
      "messages": [
        {
          "id": "48210",
          "senderName": "Anna",
          "text": "The coding tool has been updated.",
          "timestamp": "2026-10-02T09:00:00Z"
        },
        {
          "id": "48211",
          "senderName": "Marco",
          "text": "A practical guide to a new search approach is out.",
          "timestamp": "2026-10-02T09:00:00Z"
        }
      ],
      "more": false
    }
  ],
  "skipped": [],
  "partial": false
}

Needs your attention today

Before 11:00 — Marco: approve the budget so the team can continue.
This evening — Anna: the meeting moved to 19:30; she needs your confirmation.
No deadline — Mum: a 42-second voice note.

From your news channels

Coding tools: an update to the development workflow.
Search: a practical guide with examples.

I can show the details and original messages for each item, or filter the news to work-related topics.

Source messages

Marco #48210Marco · Telegram · Oct 2, 2026

Approve the budget by 11:00 or the contractor cannot start.

Anna #48211Anna · Telegram · Oct 2, 2026

The meeting moved to 19:30. Please confirm.

Mum #8812Mum · Telegram · Oct 2, 2026

Voice note, 0:42

Anna #48210Tech news · Telegram · Oct 2, 2026

The coding tool has been updated.

Transcribe Mum’s voice note and tell me what needs doing today.

Your agent uses the connected tools

tg messages transcribe "Mum" 8812

Tool output · JSON

{
  "messageId": "8812",
  "text": "My appointment is tomorrow. Please confirm today whether you can drive me there.",
  "timestamp": "2026-10-02T09:00:00Z",
  "senderName": "Mum"
}

Mum needs an answer today

Her appointment is tomorrow; confirm whether you can drive her. The voice note is transcribed. No reply has been sent.

Source messages

Mum #8812Mum · Telegram · Oct 2, 2026

My appointment is tomorrow. Please confirm today whether you can drive me there.

What should I tackle first in the next 15 minutes?

Your agent uses the connected tools

tg messages context "Marco" 48210 --before-n 2 --after-n 2

Tool output · JSON

{
  "items": [
    {
      "id": "48210",
      "senderName": "Marco",
      "text": "The budget needs approval before 11:00 or the contractor can’t start.",
      "timestamp": "2026-10-02T09:00:00Z"
    }
  ],
  "hasMore": false
}

Your first 15 minutes

Budget first: open Marco’s request and make a decision — the contractor is waiting on it.
Then the meeting: confirm 19:30 with Anna.
After that: confirm whether you can drive Mum tomorrow.

I’ve kept the news in a separate list for later. None of it needs immediate action.

Source messages

Marco #48210Marco · Telegram · Oct 2, 2026

The budget needs approval before 11:00 or the contractor can’t start.

Anna #48211Anna · Telegram · Oct 2, 2026

The meeting moved to 19:30. Please confirm.

Mum #8812Mum · Telegram · Oct 2, 2026

My appointment is tomorrow. Please confirm today whether you can drive me there.

Try a task like this with your own conversations.

Review a group

The proposed actions are visible before you approve them

Use tg cli, I’m an admin of the Community group. Show violations of its rules and a proposed action plan. Don’t delete anything yet.

Your agent uses the connected tools

tg chats list --search "Community"

Tool output · JSON

{
  "items": [
    {
      "id": "301",
      "title": "Community",
      "kind": "group"
    }
  ]
}

3 more calls

tg chats rules show 301

Tool output · JSON

{
  "items": [],
  "rules": {
    "links": "delete",
    "consent.delete": "ask"
  }
}

tg messages list 301 --limit 20

Tool output · JSON

{
  "items": [
    {
      "id": "48210",
      "chatId": "301",
      "chat": "Community",
      "date": "2026-10-02T14:00:00Z",
      "text": "We help small teams launch websites and set up advertising. Portfolio and details: https://example.com/services",
      "timestamp": "2026-10-02T14:00:00Z",
      "senderName": "Alex"
    },
    {
      "id": "48211",
      "chatId": "301",
      "chat": "Community",
      "date": "2026-10-02T14:00:00Z",
      "text": "We can take on two more projects this week. If your business needs leads, here are our packages: https://example.com/pricing",
      "timestamp": "2026-10-02T14:00:00Z",
      "senderName": "Alex"
    },
    {
      "id": "48212",
      "chatId": "301",
      "chat": "Community",
      "date": "2026-10-02T14:00:00Z",
      "text": "Will there be a recording of the meeting?",
      "timestamp": "2026-10-02T14:00:00Z",
      "senderName": "Daria"
    }
  ]
}

tg chats moderate 301 --dry-run --max-actions 2

Tool output · JSON

{
  "items": [
    {
      "messageId": "48210",
      "action": "delete",
      "outcome": "planned"
    },
    {
      "messageId": "48211",
      "action": "delete",
      "outcome": "planned"
    }
  ]
}

A plan for your review

Two promotional messages violate the saved link rule. The proposal is to delete only those messages.

The question about a recording follows the rules. No members will be removed. This is a preview; no actions have been taken.

Source messages

Alex #48210Community · Telegram · Oct 2, 2026

We help small teams launch websites and set up advertising. Portfolio and details: https://example.com/services

Alex #48211Community · Telegram · Oct 2, 2026

We can take on two more projects this week. If your business needs leads, here are our packages: https://example.com/pricing

Delete only those two promotional messages for everyone. Keep the question and all members.

Your agent uses the connected tools

tg messages delete 301 48210 48211 --for-everyone --allow-dangerous

Tool output · JSON

{
  "items": [],
  "deleted": [
    "48210",
    "48211"
  ]
}

Two messages deleted

Only the selected messages were deleted. The recording question and all members remain. No other actions from the plan were run.

Source messages

Alex #48211Community · Telegram · Oct 2, 2026

We can take on two more projects this week. If your business needs leads, here are our packages: https://example.com/pricing

Daria #48212Community · Telegram · Oct 2, 2026

Will there be a recording of the meeting?

Try a task like this with your own conversations.

Answer a customer

A support reply based on the messages this bot received

Use tg cli, check Anna’s order questions received by the sales bot and draft replies.

Your agent uses the connected tools

tg bot list

Tool output · JSON

{
  "items": [
    {
      "name": "sales",
      "configured": true
    }
  ]
}

1 more call

tg sales bot messages list 501 --limit 10

Tool output · JSON

{
  "items": [
    {
      "id": "48210",
      "text": "Delivery agreed for Friday. Address confirmed.",
      "timestamp": "2026-10-02T09:00:00Z",
      "senderName": "sales"
    },
    {
      "id": "48211",
      "text": "When is delivery? Can you move it to tomorrow?",
      "timestamp": "2026-10-02T09:00:00Z",
      "senderName": "Anna"
    }
  ],
  "source": "local"
}

Draft for Anna

Delivery is agreed for Friday and your address is confirmed. I’ll check with the team whether we can move it to tomorrow and get back to you.

Your decision is needed

The customer requests a date change. No promise: it was not confirmed in the messages received by the bot. Nothing sent yet.

Source messages

sales #48210sales · Anna · Telegram · Oct 2, 2026

Delivery agreed for Friday. Address confirmed.

Anna #48211sales · Anna · Telegram · Oct 2, 2026

When is delivery? Can you move it to tomorrow?

Send that reply from sales. I’ll check the date change myself.

Your agent uses the connected tools

tg sales bot messages send 501 "Delivery is agreed for Friday and your address is confirmed. I’ll check with the team whether we can move it to tomorrow and get back to you."

Tool output · JSON

{
  "chatId": "501",
  "messageId": "48212",
  "status": "sent"
}

Anna received the reply

The agreed date is confirmed; the date change stays with you. Context came only from messages previously received by this bot on this computer.

Source messages

sales #48210sales · Anna · Telegram · Oct 2, 2026

Delivery agreed for Friday. Address confirmed.

Anna #48211sales · Anna · Telegram · Oct 2, 2026

When is delivery? Can you move it to tomorrow?

Try a task like this with your own conversations.

Collect the latest files

One current document set from several conversations

Use tg cli, find the current Atlas contract, invoices and presentation. Check project groups and direct messages.

Your agent uses the connected tools

tg chats list --search "Atlas"

Tool output · JSON

{
  "items": [
    {
      "id": "101",
      "title": "Atlas · team"
    },
    {
      "id": "102",
      "title": "Atlas · design"
    }
  ],
  "hasMore": false
}

1 more call

tg search messages "contract OR invoice OR presentation" --chat "Atlas · team" --language legacy

Tool output · JSON

{
  "items": [
    {
      "id": "48210",
      "senderName": "Anna",
      "text": "Atlas presentation v2.",
      "timestamp": "2026-10-02T09:00:00Z"
    },
    {
      "id": "48211",
      "senderName": "Marco",
      "text": "Invoice for the first phase.",
      "timestamp": "2026-10-02T09:00:00Z"
    },
    {
      "id": "48212",
      "senderName": "Tom",
      "text": "Contract — initial draft.",
      "timestamp": "2026-10-02T09:00:00Z"
    }
  ],
  "hasMore": false
}

In the project group

Presentation: version v2.
Invoice: for the first phase.
Contract: an initial draft.

Before putting the set together

I should check Anna’s DMs and the design group for newer files.

Source messages

Anna #48210Atlas · team · Telegram · Oct 2, 2026

Atlas presentation v2.

Marco #48211Atlas · team · Telegram · Oct 2, 2026

Invoice for the first phase.

Tom #48212Atlas · team · Telegram · Oct 2, 2026

Contract — initial draft.

Check Anna's DMs and the design group. Use the latest versions, but keep the old ones too.

Your agent uses the connected tools

tg chats list --search "Anna"

Tool output · JSON

{
  "items": [
    {
      "id": "501",
      "title": "Anna",
      "kind": "private"
    }
  ],
  "hasMore": false
}

2 more calls

tg search messages "contract" --chat 501 --language legacy

Tool output · JSON

{
  "items": [
    {
      "id": "48210",
      "senderName": "Anna",
      "text": "Final Atlas contract. Payment terms updated.",
      "timestamp": "2026-10-02T09:00:00Z"
    }
  ],
  "hasMore": false
}

tg search messages "presentation" --chat "Atlas · design" --language legacy

Tool output · JSON

{
  "items": [
    {
      "id": "48210",
      "senderName": "Anna",
      "text": "Atlas presentation v3, with updated designs.",
      "timestamp": "2026-10-02T09:00:00Z"
    }
  ],
  "hasMore": false
}

Latest versions

Document	Version	Found in
Contract	Final	Anna’s DMs
Invoice	First phase	Atlas · team
Presentation	v3	Atlas · design

Version history

The contract draft and presentation v2 are listed separately. Nothing is being deleted.

Source messages

Marco #48211Atlas · team · Telegram · Oct 2, 2026

Invoice for the first phase.

Anna #48210Atlas · design · Telegram · Oct 2, 2026

Atlas presentation v3, with updated designs.

Check the remaining invoices and download the current files into an Atlas folder. Don’t send anything.

Your agent uses the connected tools

tg search messages "invoice" --chat 501 --language legacy

Tool output · JSON

{
  "items": [
    {
      "id": "48213",
      "senderName": "Anna",
      "text": "The second-phase invoice hasn’t been issued yet.",
      "timestamp": "2026-10-02T09:00:00Z"
    }
  ],
  "hasMore": false
}

3 more calls

tg messages download 501 48210 --output-dir ./Atlas

Tool output · JSON

{
  "files": [
    {
      "path": "Atlas/contract-final.pdf"
    }
  ]
}

tg messages download 101 48211 --output-dir ./Atlas

Tool output · JSON

{
  "files": [
    {
      "path": "Atlas/invoice-phase-1.pdf"
    }
  ]
}

tg messages download 102 48210 --output-dir ./Atlas

Tool output · JSON

{
  "files": [
    {
      "path": "Atlas/presentation-v3.pdf"
    }
  ]
}

In the Atlas folder

contract-final.pdf — the final contract.
invoice-phase-1.pdf — the first-phase invoice.
presentation-v3.pdf — the current presentation.

The second-phase invoice has not been issued. Older versions stay in chat history. Files are downloaded; nothing was sent to the customer.

Source messages

Marco #48211Atlas · team · Telegram · Oct 2, 2026

Invoice for the first phase.

Anna #48210Atlas · design · Telegram · Oct 2, 2026

Atlas presentation v3, with updated designs.

Use max cli, find the current Atlas contract, invoices and presentation. Check project groups and direct messages.

Your agent uses the connected tools

max chats list --search "Atlas"

Tool output · JSON

{
  "items": [
    {
      "id": "101",
      "title": "Atlas · team"
    },
    {
      "id": "102",
      "title": "Atlas · design"
    }
  ],
  "hasMore": false
}

1 more call

max search messages "contract OR invoice OR presentation" --chat "Atlas · team" --language legacy

Tool output · JSON

{
  "items": [
    {
      "id": "48210",
      "senderName": "Anna",
      "text": "Atlas presentation v2.",
      "timestamp": "2026-10-02T09:00:00Z"
    },
    {
      "id": "48211",
      "senderName": "Marco",
      "text": "Invoice for the first phase.",
      "timestamp": "2026-10-02T09:00:00Z"
    },
    {
      "id": "48212",
      "senderName": "Tom",
      "text": "Contract — initial draft.",
      "timestamp": "2026-10-02T09:00:00Z"
    }
  ],
  "hasMore": false
}

In the project group

Presentation: version v2.
Invoice: for the first phase.
Contract: an initial draft.

Before putting the set together

I should check Anna’s DMs and the design group for newer files.

Source messages

Anna #48210Atlas · team · MAX · Oct 2, 2026

Atlas presentation v2.

Marco #48211Atlas · team · MAX · Oct 2, 2026

Invoice for the first phase.

Tom #48212Atlas · team · MAX · Oct 2, 2026

Contract — initial draft.

Check Anna's DMs and the design group. Use the latest versions, but keep the old ones too.

Your agent uses the connected tools

max chats list --search "Anna"

Tool output · JSON

{
  "items": [
    {
      "id": "501",
      "title": "Anna",
      "kind": "private"
    }
  ],
  "hasMore": false
}

2 more calls

max search messages "contract" --chat 501 --language legacy

Tool output · JSON

{
  "items": [
    {
      "id": "48210",
      "senderName": "Anna",
      "text": "Final Atlas contract. Payment terms updated.",
      "timestamp": "2026-10-02T09:00:00Z"
    }
  ],
  "hasMore": false
}

max search messages "presentation" --chat "Atlas · design" --language legacy

Tool output · JSON

{
  "items": [
    {
      "id": "48210",
      "senderName": "Anna",
      "text": "Atlas presentation v3, with updated designs.",
      "timestamp": "2026-10-02T09:00:00Z"
    }
  ],
  "hasMore": false
}

Latest versions

Document	Version	Found in
Contract	Final	Anna’s DMs
Invoice	First phase	Atlas · team
Presentation	v3	Atlas · design

Version history

The contract draft and presentation v2 are listed separately. Nothing is being deleted.

Source messages

Marco #48211Atlas · team · MAX · Oct 2, 2026

Invoice for the first phase.

Anna #48210Atlas · design · MAX · Oct 2, 2026

Atlas presentation v3, with updated designs.

Check the remaining invoices and download the current files into an Atlas folder. Don’t send anything.

Your agent uses the connected tools

max search messages "invoice" --chat 501 --language legacy

Tool output · JSON

{
  "items": [
    {
      "id": "48213",
      "senderName": "Anna",
      "text": "The second-phase invoice hasn’t been issued yet.",
      "timestamp": "2026-10-02T09:00:00Z"
    }
  ],
  "hasMore": false
}

3 more calls

max messages download 501 48210 --output ./Atlas

Tool output · JSON

{
  "files": [
    {
      "path": "Atlas/contract-final.pdf"
    }
  ]
}

max messages download 101 48211 --output ./Atlas

Tool output · JSON

{
  "files": [
    {
      "path": "Atlas/invoice-phase-1.pdf"
    }
  ]
}

max messages download 102 48210 --output ./Atlas

Tool output · JSON

{
  "files": [
    {
      "path": "Atlas/presentation-v3.pdf"
    }
  ]
}

In the Atlas folder

contract-final.pdf — the final contract.
invoice-phase-1.pdf — the first-phase invoice.
presentation-v3.pdf — the current presentation.

The second-phase invoice has not been issued. Older versions stay in chat history. Files are downloaded; nothing was sent to the customer.

Source messages

Marco #48211Atlas · team · MAX · Oct 2, 2026

Invoice for the first phase.

Anna #48210Atlas · design · MAX · Oct 2, 2026

Atlas presentation v3, with updated designs.

Try a task like this with your own conversations.

Schedule messages

A message that arrives at the right time

Use tg cli, remind me in two hours to check the invoice and in six hours to resolve open questions.

Your agent uses the connected tools

tg messages send me "Check the invoice" --at-time 2h

Tool output · JSON

{
  "chatId": "me",
  "status": "scheduled",
  "sendId": "schedule-1"
}

1 more call

tg messages send me "Resolve open questions" --at-time 6h

Tool output · JSON

{
  "chatId": "me",
  "status": "scheduled",
  "sendId": "schedule-2"
}

Two reminders in Saved Messages

In two hours: check the invoice. In six: return to open questions. Telegram will deliver them even with your laptop off.

In one hour, ask Anna for the final copy and Tom for the payment status. Message each privately.

Your agent uses the connected tools

tg messages send "Anna" "Hi Anna! Please send the final copy." --at-time 1h

Tool output · JSON

{
  "status": "scheduled"
}

1 more call

tg messages send "Tom" "Hi Tom! Please send the payment-testing status." --at-time 1h

Tool output · JSON

{
  "status": "scheduled"
}

Private follow-ups scheduled

In one hour, Anna will get the request for final copy and Tom for payment status. Two private messages and your two reminders are ready.

Try a task like this with your own conversations.

See what youragent can do.

Start with a task you recognise.

Prepare for a call

Find recommendations

Follow up with context

Get a morning briefing

Review a group

Answer a customer

Collect the latest files

Schedule messages

See what your
agent can do.