Telegram companion

One private owner chat connected to your synthetic browser workspace.

Telegram is optional and disabled until the server operator privately configures the bot token and one allowed numeric Telegram user ID. Open Telegram settings in your own browser session, acknowledge the destination, generate a five-minute code and send /link CODE to your configured bot. Do not use someone else's code. No public form can change the allowed Telegram account.

Reports and reviews

/forecast and /plans run local deterministic tools. /draft INVOICE_ID USD 100 YYYY-MM-DD asks you to review an early-payment DRAFT; confirmation creates only that DRAFT. /snapshot LABEL first prepares a pending snapshot workflow. Its separate Approve button saves the exact reviewed forecast snapshot. Receipts, observed payments and consent are never inferred from generic approval; other workflow decisions require Web review.

Optional private model

Ordinary text uses a live translation only when the operator enables a private model and you complete /verify and /qualify checks using their potentially billed confirmation buttons. Your question and static task schema go to that provider; the ledger and attachments do not. Exact interpretations still need review and financial answers come from deterministic tools. Public visitor Web requests remain model-free. Model/provider availability is not guaranteed.

Notifications and limits

Use /alerts on to opt in to real Telegram messages about synthetic cash-gap and pending/action updates; /alerts off stops alerts. /status checks the link; /unlink or Web Disconnect revokes pending buttons. Only one browser workspace can be linked at a time. Pairing does not extend its 24-hour lifetime. Messages may be delayed or lost; an uncertain outbound send is not automatically retried. Check Web history before trying again. Telegram account/cookie compromise and host administrators remain outside this demo boundary.