# What is context switching in an agent workflow?

Canonical: https://perched.fyi/glossary/context-switching/
Updated: 2026-10-23

Context switching means moving your attention between tasks, projects or apps. In an agent workflow, one common example is leaving your work to check whether a terminal needs you.

## A check is different from a review

A status check asks whether something changed. A review asks what happened and whether it is correct. Keeping those questions separate can make your workflow easier to organize.

Perch puts supported states at the screen edge so a routine check does not always require opening the agent. When a decision or result needs attention, you still read it in context.


## Keep the useful switches

Switching to inspect a diff, understand a request or verify a result is part of development. Perch does not claim that all switching is waste or promise a measured productivity gain.

Clear session names and short local notes can help preserve the detail you will need after an interruption. Keep lasting project decisions in your normal documentation.


## Related reading
- [Reduce the checking loop around your coding agents](https://perched.fyi/blog/reduce-agent-context-switching/)
- [Keep the next prompt beside your coding agents](https://perched.fyi/guides/sticky-notes/)