Telegram bot
Makion ships with a built-in Telegram bot: a mobile front-end to your own Makion server. From the bot you can pick a project, choose a role, send a task with text or attachments, watch the answer stream in, receive files the agent produces, approve and apply items in the autonomous ship queue, and manage Support / Consult requests β most of what the desktop app does for day-to-day work.
The bot runs on the same server as the desktop backend and maps your Telegram account to the same Makion developer identity used for sign-in. There are no separate accounts: your projects, roles, chat history and permissions are exactly the same on both.
The bot cannot open the SAP connection itself. The SAP connector tunnel is attached from the desktop app; from the phone you can see its status and drive runs, but establishing the tunnel is a desktop action. See Systems.
Start and link the bot#
The bot is the same one used for Telegram QR sign-in. To use it:
- Open your organization's Makion bot in Telegram and send
/start(or/menu). Your administrator can point you to the right bot. - The bot maps your Telegram account to a Makion developer. If you have no role yet, it says so β ask your administrator to grant you a role and project access, exactly as on the desktop. See Users & access.
- Once you have access, the main menu appears with an always-visible button keyboard above the input.
Log in to the desktop from the bot#
The bot can also complete a desktop sign-in without scanning a QR code. On the desktop sign-in screen a QR code is shown; instead of scanning it, tap π Log in on the computer in the bot (or send /login). The bot confirms the desktop's pending sign-in and the app logs in on its next poll.
Who can use it#
Identity and permissions match the desktop model exactly:
- The first person to open the bot becomes the superadmin.
- Everyone after that starts with no access until a superadmin grants them a role. Until then the bot politely says so.
- You see only the projects you belong to; a superadmin sees all projects.
Commands#
Every command is also listed in Telegram's own / menu next to the input, so you never have to memorize them.
| Command | What it does |
|---|---|
/start, /menu |
Open the main menu and the button keyboard. |
/login |
Confirm a pending desktop sign-in (the QR alternative). |
/projects |
Choose a project. |
/mode |
Choose a role for the agent. |
/chats |
List and resume the project's recent chats. |
/clear |
Clear the current chat's history and context. |
/cancel |
Stop the task that is currently running. |
/requests |
Open the Support / Consult requests menu. |
/shipqueue |
Open the autonomous ship-queue review. |
/support |
Send a one-message report to Makion support. |
/help |
Show a short help card. |
/admin |
Open the admin menu (superadmin only; project admins see only the per-project engine switch). |
Menu buttons#
The main menu shows a persistent button keyboard so the common actions are one tap away. Tapping a button runs its action instead of sending the label as a task.
| Button | What it does |
|---|---|
| π Projects | Pick a project. After picking, the role list opens automatically. |
| π Mode | Pick a role (see Roles in the picker). |
| π Chats | List the project's recent chats; tap one to resume it, or start a new chat. |
| π Clear chat | Clear the current chat's history and context. |
| π Log in on the computer | Confirm a pending desktop sign-in. |
| π SAP | Show whether a SAP connector is attached for this project. |
| β Help | Show the help card. |
| π Ship-queue | Review, approve, and apply the autonomous agent's proposals (see Ship queue). |
| π Requests | Create and manage Support / Consult requests (see Support & Consult requests). |
| π Support | Describe a problem in one message; it is sent to Makion support. |
| βοΈ Admin | Open the admin menu. Shown only to a superadmin. |
Sending a task#
Just send a text message β it is treated as a task for the agent, run against the selected project with the selected role. You can attach context first:
- Attach a document or photo, then send the task text. The file goes into the task workspace as an attachment (up to about 20 MB per file).
- Produced files the agent creates during the run come back to the chat as documents.
The answer streams into a single message, updated live as the agent works, with a ticking "working" footer so a long step never looks stalled. Long answers are split across messages. If a run goes completely silent for several minutes β almost always a stuck call to the AI model β the bot stops it on its own and tells you to try again. Send /cancel to stop a run yourself.
Conversation history, the resumed engine session, and the last-used role are the same records the desktop uses (scoped to your developer identity Γ project), so you can start a task on your phone and continue it on the desktop, and vice versa.
Roles in the picker#
The π Mode picker groups roles the same way the desktop does, under π Development, πΌ Consulting, and π Support. A π lock marks a role that can change SAP (a write role); a role with no lock is read-only. This mirrors how roles work: read-only roles are physically handed only read tools, so they cannot change SAP regardless of the wording of your task.
If you are allowed to create projects, β New project appears in the project list and prompts for a name.
The ship queue on your phone#
The π Ship-queue menu is the human review gate for Autonomous mode, on your phone. It lists the autonomous agent's proposals and drives the exact same approve-and-apply flow as the desktop β nothing in the queue has touched SAP until a human applies it.
| Action | What it does |
|---|---|
| Tap a proposal | Open it to see its requirement, rationale, and payload. |
| β Approve | Record approval for a pending proposal. Does not write to SAP. |
| β Reject | Record rejection. Does not write to SAP. |
| π Delete | Remove a proposal from the queue. |
| π Apply | Write one approved proposal to SAP through the attached connector. |
| π Apply all | Write and activate every approved proposal, in the two-phase process, after a confirmation. |
| π§Ή Clear rejected | Remove all rejected proposals. |
| π§Ή Clear not-applied | Remove every proposal that has not been applied. |
| π Runs | List recent autonomous runs and open one to see its steps and summary. |
| π Refresh | Reload the queue. |
An apply streams its progress into a live message and reports an honest final summary (written, skipped, or failed with SAP's own reason). Applying is the only action that writes to SAP, and it requires an attached connector β see the Security model.
Support & Consult requests#
The π Requests menu manages the Support / Consult request lifecycle from the phone, using the same rules as the desktop Requests queue.
| Action | What it does |
|---|---|
| β New request | Create a request: pick π Support or πΌ Consult, set impact and urgency, then send a title (with optional details). |
| Tap a request | Open it to see its status, body, findings, and notes. |
| π¬ Investigate (read-only) | Start a read-only investigation of the request; reopen it later to read the findings. |
| π Note | Add a note to the request. |
| π To triage / βΈ Put on hold | Move the request through its lifecycle (a hold asks for a reason). |
| β Approve / β Reject / βΈ Park | Record a decision. Approve and reject ask for a close code and notes. Project admins only. |
The admin menu#
βοΈ Admin surfaces the configuration actions that are otherwise phone-inaccessible. A superadmin sees all of them; a project admin sees only the per-project Engine switch. Every action runs through the same permission gates as the desktop.
| Action | What it does |
|---|---|
| π§ Engine | Change the AI engine for the current project. |
| π€ Model | Change the global model (superadmin). |
| β¬οΈ Server update | Check for and trigger a server self-update, after a confirmation (superadmin). |
| 𧩠Retro proposals | Review, approve, or reject learn-from-mistakes proposals (superadmin). See Retro. |
| π‘ Security audit | Run the read-only security audit and see its findings (superadmin). |
What the bot deliberately cannot do#
The bot covers day-to-day work, but a few things stay on the desktop by design:
- Open the SAP connection. The SAP connector tunnel is attached from the desktop Systems tab. The π SAP button only reports whether a connector is attached; a task or an apply that writes to SAP needs that desktop connector to be live.
- Manage members, roles, and project access. Granting roles and adding people to projects is a desktop action. See Users & access.
- Edit methodology and knowledge. Base rules, per-role methodology, and knowledge-base files are edited on the desktop Methodology tab.
- Set engine credentials. Adding an API key or completing a subscription login for an engine is done on the desktop.
Language#
The bot interface is bilingual (Ukrainian / English) and follows your Telegram language, defaulting to English.
Related pages#
- Sign in & projects β the desktop sign-in the bot can complete.
- How roles work β read-only vs write, and the π lock in the picker.
- Autonomous mode β the ship queue the bot lets you approve and apply.
- Requests β the Support / Consult lifecycle.
- Security model β why applies need a connector, and how writes are gated.