channel-message-flows

You can preview Telegram channel message UX by running a node script with parameters for channel selection, target chat ID, and flow type. This replays deterministic send, edit, and delete sequences to validate how agent messages will look and evolve in real channel flows.

Yes, you can test working-thought progress formatting and timing cadence using fixture-driven flow variants like working-final and thinking-final. These predefined flows simulate message sequences to validate your agent's formatting and timing behavior.

You target a specific Telegram chat or thread by passing the chat ID as the target parameter and including optional account or thread targeting arguments when executing the node command for your selected flow.

This approach is limited to Telegram-only workflows and requires node execution of the repo script from the root directory. It does not support other messaging platforms and relies on predefined fixture-based flow variants for testing.

Yes, this tool supports simulating draft edits and message deletions by exercising realistic send, edit, and delete message sequences against your configured Telegram channel target to validate the complete message UX lifecycle.

The best way to validate final durable output text is by selecting a fixture flow like working-final or thinking-final, which tests the progression from intermediate message states to the final durable text delivered to your Telegram channel.