Get the agent's decisions in Telegram
Connect your own Telegram chat to a workspace: the agent's decisions as it makes them, each bill waiting for approval with a link to review it that never approves anything, what is safe to spend and waiting, and invoices sent to the bot.
Connect your own Telegram chat to a workspace, and the chat tells you what the agent decided, a minute after it decides, and which bills wait for approval, each with a link to review it. You can ask it what is safe to spend and what waits for a person, and send it an invoice to add as a payable. The bot never approves or pays anything: what the agent stopped is still decided in Vestiarion, behind your sign-in.
1.Connect your chat
Open Settings in your workspace. Every member sees a Telegram card at the top, under Notifications, whatever their role.
- Choose Connect Telegram. The card gives you an Open Telegram button. The link works once, for 10 minutes.
- Choose Open Telegram. Telegram opens a chat with the Vestiarion bot. Press Start.
- The bot answers that the chat is connected to your workspace, and lists what you can ask. Back in Vestiarion, the card now says which Telegram account is connected, and since when.
If the bot answers "This link was already used or has expired.", choose Connect Telegram again for a new link. A link connects one chat to your membership of one workspace; the ledger records telegram_connected with your Telegram username masked.
The bot works only in a private chat with you. Added to a group, it answers "I only work in a private chat" and shows nothing, so a workspace's payments never reach people who are not its members.
2.What the chat receives
After each cycle, the chat gets one message listing what the agent decided since the last one: what it paid, scheduled, released or received, what it stopped, and the early payment it negotiated: the offers it made, a supplier's answer or counter, its answer to that, and an offer it withdrew. Each decision says why, and links to where you see it in Vestiarion: a milestone's opens its own row on Contractors. The bills it held or flagged for a person, or asked details for, and that still wait, end the message, each with a link to review it. A payment that has not confirmed 15 minutes after it was submitted to Circle is posted within minutes, without waiting for a cycle.
Acme · the agent decided 3 things
✅ Paid Centronex 0.35 USDC · 26 s after it was added; Circle confirmed it on Arc testnet.
DeepSeek decided, as the written policy would. Checks passed: purchase order and goods, the 2.00 USDC limit, screening.
Arc testnet transaction · How it decided
2 bills wait for approval:
⏸ 3.00 USDC · Jiren · held: Code stopped it: it is above the counterparty's payment limit. · Review
⏸ 1,250.00 USDC · Northwind Hosting · flagged: The bank details on the invoice differ from the ones on file. · needs two approvals, an accountant can co-sign · Review
Opening a link never approves anything.- ✅ marks what was done; Arc testnet transaction opens the payment on the explorer, or Arc mainnet transaction for a workspace on Arc mainnet.
- A payment Circle has not confirmed yet has neither mark: it says it was submitted and waits for Circle.
- ⏸ marks what the agent stopped. The bills that still wait for approval come last, under how many wait, one line each: the amount and its currency, the payee, whether the agent held or flagged it or it is waiting for details, why, and Review, the bill's own link.
- When a check in code stopped a bill, such as its payment limit, the payee lock or the cash a payment needs, the line says what stopped it, as its row on Bills & receivables does: "Code stopped it: it is above the counterparty's payment limit." A bill the agent held itself gives the first sentence of the agent's reason, even while cash is short. When Vestiarion cannot read what stopped a bill, the line gives the agent's sentence too; the bill's card on Approvals says the rest.
- A bill above the workspace's figure for two approvals says "needs two approvals". While an owner lets accountants co-sign, it says "needs two approvals, an accountant can co-sign".
- Only bills that still wait are listed there. A message lists at most ten bills, as many as fit, then "…and 3 more in Approvals", with a link to Approvals, for the rest.
- A stopped bill that is not listed there keeps its own place among the decisions, as the agent decided it, with Decide in Approvals, which opens its card, or Add details for one it asked details for. That is a bill a person approved, rejected or returned before the message went out, or every stopped bill when Vestiarion could not check which still wait.
- ⚠️ marks a warning that is not yours to decide, such as the cash running short.
- In shadow mode, a payment held for your verdict keeps its own place among the decisions and links Give your verdict, where you agree or disagree with it.
- When the wallet will run short, the chat is told how much, by when and what the agent is doing about it, and told again only when that changes. See When the cash will run short.
- A chat is told only about decisions made after it was connected. A busy cycle's message says how many more decisions are in the console.
In these messages and in /waiting, every value that comes from a bill or from the agent, such as a payee's name or the agent's reason, is shown as plain text. Hidden direction and zero-width characters are removed, so no name can make a line read as another bill's. A web address, an @name or a /command inside one is broken up so Telegram does not turn it into something you can tap: acme.com reads acme[.]com, and the @ or / is shown in its wide form. The only links are the ones Vestiarion adds. A wallet address is shortened to its first and last four characters.
Review a bill
Review opens the bill's card on Approvals in Vestiarion. The link carries no token: you sign in as usual, and the card shows what you can do with your role. Opening a link never approves anything. You decide the bill there, with Approve and pay, Reject or Return to agent, under every check Vestiarion makes. A bill waiting for details opens on Approvals too, where an owner or admin adds them with Add details.
3.Ask it
| Ask | What you get |
|---|---|
/today | Safe to spend today, what is due in the next 30 days, how many payments wait for a person, and what the agent pays next |
/waiting | Each payable or milestone waiting for a person, why it waits, and a link: Review for a payable, Contractors for a milestone, which opens its own row there. A payable a check in code stopped says what stopped it, such as "Code stopped it: the operating wallet did not hold the cash it needs."; the rest give the first sentence of why the agent stopped them. A bill asked for details says it is waiting for details. In shadow mode, a payment held for your verdict says it waits for your verdict, with Give your verdict |
/ledger | Whether the signed ledger is intact, checked the way Verify hash chain checks it |
/workspaces | Your connected workspaces, to switch between them |
/disconnect | Stops this workspace's decisions coming to the chat |
/help | What the bot does, and what it never does |
You can also ask in plain words, in English or Vietnamese: "what is held?", "còn tiêu được bao nhiêu?". A model only picks which of the questions above you asked; the answer is always read from your workspace and written by code, so no figure comes from the model.
4.Send it an invoice
An owner or admin can send the bot an invoice: a PDF, an .eml or .txt file of at most 4 MB, or the invoice's text pasted into the chat. The bot reads it the way From a document on Bills & receivables reads one, and shows every field it read, with what to check and the model's note, marked as The model's note: it can be wrong.
When it read a counterparty already in the workspace, an amount and a due date, three buttons follow:
- Add, goods received adds the payable with the goods or services marked received.
- Add, not received yet adds it without. The agent then asks for the goods to be received before it pays.
- Cancel answers "Not added." and adds nothing.
After Add, the bot says the payable was added. The agent usually decides within a minute, and its decision will be sent here, to the same chat. A draft can be added once, within an hour; after that the bot says "This draft was already used or has expired." Send the invoice again to read it anew.
The bot does not read photos: it asks you to Send the invoice as a PDF, or paste its text. When it cannot add an invoice from the chat, because no counterparty in the workspace matches its vendor or it has no amount or due date, it says what is missing and links to Bills & receivables, where you can add it by hand. An approver, an accountant or a viewer who sends an invoice is told "Only an owner or admin can add invoices."
The invoice is added exactly as one added on Bills & receivables: the ledger's create_invoice entry names you, and adds via: "telegram" and the hash of the document. The document itself is not stored. Its USDC moves on Arc, on the workspace's network, only when the agent pays it, under every check it applies to any payable.
5.More than one workspace
Connect each workspace from its own Settings. One chat can hold several: decisions come from all of them, each message headed with its workspace's name. Commands and invoices go to one of them at a time. Send /workspaces to see them as buttons, the active one marked ✓, and tap another to switch; the bot answers "Commands and invoices now go to" that workspace.
6.Disconnect
Choose Disconnect on the Telegram card, or send /disconnect in the chat. Either stops the workspace's decisions coming to the chat, and the ledger records telegram_disconnected. If you block the bot in Telegram, Vestiarion disconnects the chat at its next message. If someone removes you from the workspace, your chat's connection goes with your membership.
For the person who runs the deployment
The bot is one Telegram bot for the whole deployment, made with @BotFather. Set TELEGRAM_BOT_TOKEN, TELEGRAM_WEBHOOK_SECRET and TELEGRAM_BOT_USERNAME, then run npm run telegram:setup -- https://<your deployment> once to register the webhook and the command menu. Without all three, the Telegram card does not show and the webhook answers 404. The webhook accepts only requests that carry the secret Telegram was given.