What it shows
Operations lives in the right panel (CmdShiftO), beside the Code agent, or in its own window. It reads the services your project uses and you're signed in to (its hosts, its CI on GitHub, its app store listings) and shows:
- Alerts, by level: critical, warnings and info;
- What it's watching: the hosts, CI and stores it found;
- What each service says about itself, and when it was last checked.
It only reports what the services report: it never invents issues. "Quiet" means every service replied with nothing open; if a host is missing, signed out or didn't answer, Operations says it couldn't fully check instead of showing all clear.
Refresh
Operations checks every five minutes by default and holds still in between, so you can read it. Refresh checks now. In Settings, Panels:
- Auto refresh on or off (off: only when you press Refresh);
- Refresh interval, in seconds (300 by default, 60 at least);
- which alert levels to show, and whether to list what's being watched.
Connecting services
Operations works from the sign-ins you already have (Deploy's hosts, GitHub). Tokens you add go into your computer's secure storage, never into a file or the chat. Connect cloud links the Piye web console for its extra checks: uptime, response time, certificates and security headers of your live addresses, every five minutes, with email alerts. See The web console.
The agent and Operations
The Code agent can read what Operations sees, so you can ask it "why is production failing?" and it starts from the real alerts. In Piye Studio, each project has an Operations tab.