Automation, Scheduling & Channels

Automation is what turns the app into a runtime

If DreamCreator only handled manually triggered work, it would still be a desktop tool. Scheduled jobs, notification delivery, channel access, and operational controls are what make it behave like a runtime.

The point is not “more settings.” The point is that repeated work can keep happening without requiring the same manual step every time.

What a scheduled job is made of

Based on the current product structure, a scheduled job usually includes:

• schedule: when it runs, using cron, every, or at
• session target: whether it runs in the main session or an isolated one
• wake mode: whether it runs immediately or waits for the next heartbeat
• payload: whether it emits a system event or triggers an agent turn
• delivery: whether results stay silent, are announced, or are delivered outward

So a scheduled job is closer to an operating rule than a simple timer.

Gateway controls decide how work runs

As the number of assistants and jobs grows, stability is shaped by runtime controls: concurrency, heartbeat behavior, tool permissions, loop detection, context boundaries, and related execution settings.

That makes the gateway layer operationally important, not just technical background.

Channel access keeps the same assistant available beyond the desktop

DreamCreator currently supports Telegram and is moving toward Feishu and WeChat. The point of channel access is not to replicate the whole desktop UI on a phone. It is to keep follow-up work moving when you are away from the desktop.

Typical uses include:

• receiving results or failure notices
• triggering lightweight actions from mobile
• continuing with the same assistant context outside the desktop

Channel configuration is more than a token field

Using Telegram as an example, real configuration often includes:

• pairing or allow lists
• group policies and group allow lists
• custom commands and menu sync
• notification and failure routing

That is why channel access should be understood as exposing the runtime to an external surface, not merely connecting a chat app.