Telegram

You can work with Eggent from Telegram just as from the browser: write tasks in text or by voice, send files, get answers and schedule results. Chats from Telegram are visible in the web app too.

#Two ways to connect

#The cloud's shared bot

If you signed up through @eggentai_bot, it is already linked to your workspace. Just write to it. /login there answers with a button that opens the workspace in a browser already signed in.

If you signed up on the website, ask the agent to connect Telegram (the Morning brief in Telegram card does it as its first step). It gives you a link to the bot: open it in Telegram and press Start, and the chat is linked to your workspace. The link works once and for 30 minutes. If this Telegram account is already linked to another workspace, the bot asks you to open the link a second time to move it. While the agent works you see a draft in the chat: first what the agent is busy with ("Thinking…", "Searching the web", "Reading a file"), then the answer as it is written. The finished answer arrives as a normal message.

#Your own bot

The easiest way is the Your own Telegram bot card on the new-chat screen: the agent walks you through it. By hand:

1. In Telegram, open @BotFather, send /newbot, choose a name and username and copy the token.
2. In Eggent, open Settings → Messengers.
3. In 1. Bot Token, paste the token and press Activate Bot.
4. Eggent picks the connection mode. In the cloud it works right away; on your own server without a public HTTPS address it uses Long Polling.
5. Open your bot in Telegram and press Start.

#Who can write to your bot

The bot answers only people on its allowlist. To let someone in (yourself included, the first time):

1. In Settings → Messengers → Access Control, press Generate Access Code. Or ask the agent: "give me an access code for a colleague".
2. The person opens the bot and sends /code <code>.
3. The code works once. After it the person is on the allowlist.

The user_id list can be edited by hand in the same block.

#What you can send

• Text — as in the web chat.
• Voice messages — transcribed inside the workspace and passed to the agent as text. See Voice.
• Files and photos — saved to the chat's attachments; the agent sees them. A caption goes in as the message.
• Files — an answer that made files says so at the end. Send /files to get them in this chat: up to three go one by one, more come as one archive.
• @project task — a message that starts with @ and a project's name hands the task to that project; its answer comes back here and you stay in the same chat. See Projects.
• "stop", "cancel", "enough" — on its own, stops the current work. Any other message sent during work is taken into the current task. They reach the work at once, even if it has been going for a long time: they do not wait for it to finish.

Bot commands:

The bot works only in private messages. It does not answer in groups.

#Which chat a message goes to

Telegram is one thread, while the workspace keeps many chats. Where your message lands:

• A reply (Reply on a message from the bot) continues the chat that message came from: this morning's report, or an answer from last week. Telegram shows the quoted message, and the agent gets it too.
• Any other message continues the chat that wrote to you last. When a scheduled report arrives, your next message is about the report and goes to its chat.
• When the conversation moves, the message says where: its last line is 💬 and the chat's name.
• /chats lists the recent chats. Tap the /c_… command under one to continue it there. /new starts a fresh chat. The work a project did for another chat is marked ↪️.
• Or ask the agent: "go back to the chat about the price list", "what did yesterday's report say?". It can find, read and switch between chats.

A chat keeps its project: when the conversation moves into a chat from a project, the next messages run in that project.

#The agent writes on its own

Ask, and the agent sends a message or a file to Telegram: the result of a long task, a reminder, a scheduled report. Images go as photos with a caption, everything else as documents.

A scheduled report comes from the task's own chat and says so in its last line, so answering it continues the report. See Schedules.

#Posting to a channel

Your own bot can post to a channel:

1. Add the bot to the channel as an administrator allowed to post messages.
2. Ask the agent: "post this with the picture to @mychannel".

This works in a schedule too: "every day at 10:00 post to @mychannel from the content plan".

#An answer that seems stuck

While the agent works, the draft shows what it is doing. If nothing happens for a minute and a half, the draft says it is still going and how to stop it: send /reset. That stops the work, drops a question it was waiting on, and keeps the conversation and everything already done; write again to carry on.

You do not have to notice: Eggent stops a turn that has gone completely quiet by itself — after about 3 minutes while it is getting ready, 6 minutes of waiting for the model, or 20 minutes inside one command that prints nothing. It tells you what happened, and your messages are saved. A command that waits for an answer on a run nobody can answer on — in Telegram, for instance — is given an empty answer instead of waiting for ever.

#If the bot is silent

• Check Settings → Messengers: the bot is active, the status says "Running" or the webhook is set up.
• Make sure you are writing in private messages and your user_id is on the allowlist (or send /code).
• If the token was changed in @BotFather, paste the new one and press Activate Bot again.
• The bot does not drop long tasks: the draft shows the agent is still working.