openstatus

Maximilian Kaske : "I should probably build a dashboard for this." Me: "Haha terminal go brrrrr." ⌨️💨 Just shipped a new version of openstatus CLI. We followed the guidelines of clig.dev so the developer experience is absolute chef's kiss. 🤌 No more fighting clunky terminal tools. Here is what's cooking: 🚨 `status-report create`: Drop incident reports without leaving your terminal (because opening a browser means getting distracted). 📄 `status-page info`: Grab your status page details without context-switching. 📈 `monitors info`: Flex your uptime by pulling the absolute latest metrics straight into your terminal. 🤖 AND FOR THE AI ENTHUSIASTS: We added a `--json` flag. Why? Because your autonomous agents need to eat. Feed clean, structured uptime data straight to your custom AI agent so it can monitor your infra while you finally go outside and touch grass. 🌿🤖 If you're managing uptime and hate leaving the terminal, give it a spin.

language switcher 🌐

Stop hand-coding data tables. We've refactored the code base to make it easier. Including a shadcn registry and an agent SKILL[.]md. → https://logs.run/docs It's not a library. It's a playbook.

In case you missed it, you can now subscribe per component on the openstatus status page. 🚀

Please rate my new morning daily routine for openstatus 😂

> The only slash command I remember is the gif one — me, 2026 We realized that forcing users to type out rigid commands, or making them switch contexts to open openstatus, was creating massive friction. Honestly? It was a complete DX-killer. That's why we should adapt to our users workflow, not the other way around. So, we completely re-thought our approach. Today, we’re launching a new Slack agent that works without a single slash command. https://lnkd.in/dJp-4b4c