Skip to content

[Docs] Describe recent automation and Telegram behavior #2582

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
roomote-community wants to merge 1 commit into
base: develop
Choose a base branch
from
Draft

[Docs] Describe recent automation and Telegram behavior #2582

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions apps/docs/automations.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -169,9 +169,9 @@ Create arbitrary scheduled agent runs with:
has an explicitly verified account email

Each custom automation row summarizes its cadence, workspace target, report
destination, creator, and most recent run. Its runs also appear as Sessions in
the normal Session history. Blank slate runs do not clone repositories or
require source-control credentials.
destination, creator, next scheduled run, and most recent run. Its runs also

@roomote-community roomote-community Bot Sep 12, 2026

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This reads as though every custom automation row always includes a next-run value, but the UI renders it only when both nextRunAt and the scheduling timezone exist. Disabled/off or invalid schedules intentionally return no nextRunAt, so their rows omit it. Please qualify this as a next scheduled run when available to avoid promising metadata those rows do not display.

appear as Sessions in the normal Session history. Blank slate runs do not clone
repositories or require source-control credentials.

When creating an automation through Roomote chat, ask for **suggested tasks** or
**launchable follow-ups** if qualifying findings should become tasks that
Expand Down Expand Up @@ -209,8 +209,8 @@ the Session is what talks to the report destination.
Runs deliver to every custom-automation report destination: Slack, Discord,
Microsoft Teams, Telegram, or Email. Chat providers support a channel/chat or
a direct message to the automation owner; Email is private only. Each run keeps
a distinct Session, and the report links
back to that Session in the web app. The Session transcript shows the
a distinct Session, and each Email run starts a separate mail thread. The report
links back to that Session in the web app. The Session transcript shows the
automation's configured prompt and any delegated task cards, and its normal
composer lets a signed-in teammate continue the run from the dashboard. Replies
on chat providers continue the Session directly there, and replies to an Email
Expand Down
7 changes: 7 additions & 0 deletions apps/docs/providers/communications/telegram.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -128,6 +128,13 @@ naturally.
Telegram does not support native drafts in group chats, so groups use
Telegram's standard typing status and receive completed replies instead.

When Fast delegates coding work, Roomote posts one separate live task message
in the same chat or topic. It edits that message with compact, expandable
progress and settles it as completed, failed, stopped, or waiting for input
instead of posting a stream of status messages. **Open in Roomote** opens the
selected task inside its Session; the Session still sends the final result as a
normal reply.

Existing task chats and topics keep their active-task, `request_user_input`,
and resumable-snapshot behavior. If Fast cannot start a conversation, Roomote
says so in the chat instead of starting a task another way. Fast automation
Expand Down
Loading