Manual overrides

Adjust the day. Keep the automation.

Quick overrides let you protect focus, start early, work later, or finish for the day. They can update Slack and your workday boundaries immediately while leaving the calendar and schedule rules underneath intact.

Get started

Automation handles the plan. Real days still need exceptions.

Calendar and schedule rules should run the normal day. But focus can begin unexpectedly, work can start early or finish early, and a late task can extend the evening. Those moments need fast control without dismantling the automation underneath.

Focus needs a meaningful stopping point

Sometimes an hour is right. Other times focus should run only until the current event ends, the next calendar block begins, or the workday finishes.

Finishing early should not leave work switched on

When the real work is done, waiting for a preset boundary keeps Slack and after-hours behavior out of step with reality.

One exception should not require a rebuild

Starting early, working late, taking a short break, or pausing automation should change the current state—not force you to edit the standing rules.

Automation still handles the normal day.

Overrides handle the exception happening now.

Control should not create cleanup.

Fast exceptions without breaking the automation

Choose an intentional state for the moment and let ModePilot handle the connected Slack and boundary behavior. The underlying calendar and schedule rules stay intact, ready to take over again.

Focus until the right stopping point

Start protection now for 30 minutes or an hour, or align it with the current event, an upcoming calendar block, or the end of your workday.

  • Apply focus immediately
  • Protect the current block
  • Keep base rules intact
Quick controlsStart focusTake a breakEnd workday

Start early or keep working later

Open a temporary work session before scheduled hours, or extend the day once when work continues beyond the expected finish.

  • Keep work active longer
  • Move the boundary once
  • Avoid changing the schedule
Extend workday

+60 minutes

Boundary applied

Switch off cleanly when you finish early

Trigger the normal end-of-day behavior immediately and return to the standing schedule at the next work window.

  • Switch off immediately
  • Clear active signals
  • Return next work window
Quick controlsStart focusTake a breakEnd workday

Take a short, intentional pause

Set a temporary recovery state without editing the calendar or changing the rules for the rest of the day.

  • Set a temporary break
  • Update availability cleanly
  • Resume when ready
Quick controlsStart focusTake a breakEnd workday

Keep the same controls close at hand

See the current ModePilot state and use the same quick overrides from the Linux system tray, without leaving the task to open a browser.

  • See the current mode
  • Use controls from the tray
  • Avoid a browser detour

Handle a change of plan with a quick override

Overrides are not the story for the whole product. They matter because exceptions are real and they should be handled quickly without breaking the base model.

Example 01

Post-meeting focus

What changesA meeting ends and urgent follow-up needs attention immediately.
ModePilot responseThe user activates a temporary focus override.
ResultFocus and interruption protection start without editing the calendar or opening Slack.
Urgent follow-up gets protected immediately, while the calendar stays untouched.
01Post-meeting focus
What changesA meeting ends and urgent follow-up needs attention immediately.
ModePilot responseThe user activates a temporary focus override.
ResultFocus and interruption protection start without editing the calendar or opening Slack.
Urgent follow-up gets protected immediately, while the calendar stays untouched.
02Early finish
What changesThe working day ends before the scheduled boundary.
ModePilot responseThe user chooses to end the workday now.
ResultEnd-of-day behavior starts immediately instead of waiting for the schedule.
Your work signals switch off when you finish.
03Temporary pause
What changesAutomatic changes should stop for a short period.
ModePilot responseThe user pauses automation without changing the standing configuration.
ResultManual control takes over temporarily while the wider system remains ready to resume.
Automation steps aside now and is ready when you return.
04Recovery break
What changesAn unplanned break becomes necessary during the day.
ModePilot responseThe user applies a short break override that reflects the current state.
ResultAvailability stays honest even though the calendar did not predict the change.
An unexpected break becomes visible without rearranging your calendar.

Exception handling without collapsing back into manual upkeep

Manual control is useful when it is surgical. It becomes a problem only when it turns into the main operating model again.

All-manual behavior

Manual · Rigid · Outdated fast

  • Requires repeated Slack babysitting and context switching.
  • Breaks the benefit of having a calendar-driven system at all.
  • Makes every exception feel like starting from scratch.

Targeted overrides

Adaptive · Contextual · Always current

  • Handle the exception quickly while the standing automation model remains intact.
  • Keep fast controls close to the real work moment.
  • Let the calendar and schedule take back over once the exception ends.

Frequently asked questions

Handle the change. Keep your usual rules.

Make the adjustment you need now. ModePilot returns control to your calendar and schedule when the override ends.

Get started

Google Calendar setup comes first. Slack can be connected later.