Calendar

Calendar shows how work actually occupied time. It is not just a scheduling add-on. In Rudder, Calendar is a view over agent runs, issue work, planned human checkpoints, and imported operator calendar blocks.

​

Why Calendar matters

An agent team can look active while still being hard to inspect. Calendar helps answer time-based operating questions:

• Which agents were active today?
• Which issues received work?
• Did review happen soon after execution?
• Are multiple agents blocked at the same time?
• Is agent runtime clustered around launch, release, or support work?
• Where did human checkpoints interrupt or unblock the workflow?

​

What appears on Calendar

Calendar can show several kinds of blocks: The best Calendar view comes from real issue and run records. Avoid inventing decorative calendar-only data when the underlying work should already explain the schedule.

​

How to read it

Use Calendar after a few issues have run. Look for:

• dense clusters around one project
• review blocks after implementation blocks
• long gaps between agent output and human decision
• repeated blocked runs that need better setup
• agents running without a clear linked issue

Calendar is most useful when it changes an operating decision: reassign, split work, unblock access, schedule review, or stop low-value runtime.

​

Calendar is not assignment

Creating a Calendar block does not assign an issue, change priority, or run a heartbeat. Assignment and status still live on the issue. Calendar explains time; the issue controls work.

​

Next steps