Configuring Standup Schedules: Intervals, Fixed Times, and Day Selection

Choosing the Right Schedule Mode

Remocode offers two scheduling modes for standup reports, and picking the right one depends on how your team works. This guide walks through both options and the additional settings that fine-tune your reports.

Interval Mode: Continuous Progress Snapshots

Interval mode triggers a standup report every N minutes. The default is 10 minutes, which gives you frequent check-ins without overwhelming your Telegram feed.

When to use interval mode:

• ●Solo development sessions where you want a running log of progress
• ●Debugging marathons where you need to track when things go wrong
• ●Time-boxed sprints where you want granular visibility into agent activity

You can increase the interval to 30 or 60 minutes for less frequent updates, or decrease it to 5 minutes during critical phases when you need near-real-time awareness.

Fixed Time Mode: Traditional Standup Cadence

Fixed time mode lets you specify exact times for reports. Common configurations include:

• ●09:00 — morning summary of overnight agent activity
• ●12:00 — midday progress check before lunch
• ●17:00 — end-of-day wrap-up for team sharing

You can add as many fixed times as you need. Some teams add a 15:00 check to catch afternoon blockers early. Others use a single end-of-day report to keep things minimal.

Day Selection: Weekdays and Beyond

By default, standup reports run on weekdays (Monday through Friday). The day selection interface provides checkboxes for each day of the week, letting you customize the schedule.

Common configurations:

• ●Weekdays only — standard for most teams
• ●Monday through Saturday — for teams with Saturday sprints
• ●Every day — useful if you run agents overnight or on weekends
• ●Custom selection — perhaps Tuesday through Thursday for a part-time project

Day selection applies to both interval and fixed time modes. If you select only Monday, Wednesday, and Friday, reports will only fire on those days regardless of your time settings.

Custom Report Prompts

The default prompt instructs the AI to analyze terminals like a scrum master, producing structured output with status, progress, and issues. But you can customize this prompt to match your team's reporting style.

Examples of custom prompts:

• ●Focus on blockers only: *"Report only terminals that are in Error or Blocked state. Skip Active and Idle panes."*
• ●Technical detail: *"Include file names being modified and specific error messages. Be verbose."*
• ●Executive summary: *"Provide a one-line summary per pane. Keep the total report under 10 lines."*

Custom prompts give you control over report verbosity and focus. A team lead might want high-level summaries, while a developer debugging a tricky issue might want every error captured.

Filtering: Assigned Panes vs. All Panes

You can choose whether standup reports cover all panes or only assigned ones. Assigned panes are terminals you've labeled with project or task descriptions using the pane assignment feature.

Filtering to assigned panes is useful when you have utility terminals — shell sessions, log viewers, documentation browsers — that would add noise to your reports. By assigning only your coding agent panes, you get focused reports on actual development work.

Combining Settings for Your Team

Here's a practical configuration for a remote team:

• ●Mode: Fixed times at 09:00 and 17:00
• ●Days: Monday through Friday
• ●Filter: Assigned panes only
• ●Prompt: Default scrum master style

This gives the team a morning and evening digest of AI agent progress across all assigned tasks, delivered straight to Telegram. Team members can review asynchronously without scheduling a meeting.

Adjust these settings as your workflow evolves. The goal is a standup system that provides value without adding overhead.