docs(mantis): describe telegram desktop proof · openclaw/openclaw@2c124a1
obviyus
·
2026-05-11
·
via Recent Commits to openclaw:main
| Original file line number | Diff line number | Diff line change |
|---|
@@ -250,6 +250,17 @@ number is available. This lane is transcript-visual rather than logged-in
|
250 | 250 | Telegram Web proof: the Telegram Bot API gives stable live message evidence, but |
251 | 251 | Telegram Web login state is not required for normal Mantis automation. |
252 | 252 | |
| 253 | +`Mantis Telegram Desktop Proof` is the agentic native Telegram Desktop |
| 254 | +before/after wrapper. A maintainer can trigger it from a PR comment with |
| 255 | +`@Mantis telegram desktop proof`, from the Actions UI with freeform |
| 256 | +instructions, or through the generic `Mantis Scenario` dispatcher. The workflow |
| 257 | +hands the PR, baseline ref, candidate ref, and maintainer instructions to Codex. |
| 258 | +The agent reads the PR, decides what Telegram-visible behavior proves the |
| 259 | +change, runs the real-user Crabbox Telegram Desktop proof lane for baseline and |
| 260 | +candidate, iterates until the native GIFs are useful, writes paired |
| 261 | +`motionPreview` artifacts into `mantis-evidence.json`, uploads the bundle, and |
| 262 | +posts a 2-column PR evidence table when a PR number is available. |
| 263 | + |
253 | 264 | For human-in-the-loop Telegram desktop setup, use the scenario builder: |
254 | 265 | |
255 | 266 | ```bash |
|
| Original file line number | Diff line number | Diff line change |
|---|
@@ -340,6 +340,21 @@ telegram-live`) or directly from a pull request comment:
|
340 | 340 | @Mantis telegram scenarios=telegram-status-command,telegram-mentioned-message-reply |
341 | 341 | ``` |
342 | 342 | |
| 343 | +`Mantis Telegram Desktop Proof` is the agentic native Telegram Desktop |
| 344 | +before/after wrapper for PR visual proof. Start it from the Actions UI with |
| 345 | +freeform `instructions`, through `Mantis Scenario` (`scenario_id: |
| 346 | +telegram-desktop-proof`), or from a PR comment: |
| 347 | + |
| 348 | +```text |
| 349 | +@Mantis telegram desktop proof |
| 350 | +``` |
| 351 | + |
| 352 | +The Mantis agent reads the PR, decides what Telegram-visible behavior proves the |
| 353 | +change, runs the real-user Crabbox Telegram Desktop proof lane on baseline and |
| 354 | +candidate refs, iterates until the native GIFs are useful, writes a paired |
| 355 | +`motionPreview` manifest, and posts the same 2-column GIF table through the |
| 356 | +Mantis GitHub App when `pr_number` is set. |
| 357 | + |
343 | 358 | - `pnpm openclaw qa mantis telegram-desktop-builder` |
344 | 359 | - Leases or reuses a Crabbox Linux desktop, installs native Telegram Desktop, configures OpenClaw with a leased Telegram SUT bot token, starts the gateway, and records screenshot/MP4 evidence from the visible VNC desktop. |
345 | 360 | - Defaults to `--credential-source convex` so workflows only need the Convex broker secret. Use `--credential-source env` with the same `OPENCLAW_QA_TELEGRAM_*` variables as `pnpm openclaw qa telegram`. |
|
此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。
