Bringing Observability to the Command Line: The gcx CLI Tool for Developers and Agents

Introduction: The Changing Landscape of Development

As coding practices evolve, so must the tools we use to monitor and respond to system issues. Modern engineers spend significant time in the terminal, and agentic coding platforms like Cursor and Claude Code have become essential for daily tasks. While these tools accelerate code generation, they fail to address the context switching that occurs when developers must leave the command line to use separate observability tools. Additionally, a visibility gap persists: agents can interact with your local code but remain blind to production realities—latency spikes, SLO breaches, or real-time performance issues. This disconnect means agents generate code based on assumptions rather than actual system behavior.

Introducing gcx: Grafana Cloud CLI

To bridge this gap, Grafana Cloud has launched the public preview of gcx, a powerful CLI tool that brings observability directly into your terminal—and into the agentic coding environment running inside it. With gcx, developers can detect and resolve incidents in minutes instead of hours, without ever leaving their command line.

From Greenfield to Full Observability in Minutes

gcx is designed to handle the heavy lifting. Most services begin with zero instrumentation, alerts, or SLOs—a common starting point that gcx treats as an opportunity rather than a roadblock. Simply point your agent at the service and ask it to bring everything up to standard. gcx exposes the necessary primitives across the full observability lifecycle:

Instrumentation

Wire OpenTelemetry into your codebase directly from the terminal. Validate that metrics, logs, and traces are flowing correctly, and confirm data is landing in the appropriate backends—all without leaving the command line.

Alerting, SLOs, and Synthetics

Generate alert rules based on the signals your service actually emits. Define an SLO against real latency or availability indicators and push it live. Stand up synthetic probes so that users are never the first to report an outage. Everything is manageable from your terminal via gcx.

Frontend Observability, Application Observability, and Kubernetes Monitoring

Onboard a Faro-instrumented frontend by creating the app and managing source maps for readable stack traces. Similarly, onboard backend services and Kubernetes infrastructure using the Instrumentation Hub—all through gcx.

Everything as Code

Pull dashboards, alerts, SLOs, and checks as editable files. Modify them locally with your agent, then push the changes back. When a human needs to intervene, open a deep link directly into Grafana Cloud. This approach transforms what used to be a multi-day ticket into a single agent-driven session.

Why This Matters for AI Agents

The true power of gcx emerges when you give your agents access to it. Without production context, an agent is limited to pattern-matching on source files, guessing at the correct solution. With gcx, the same agent can read the current state of the running system—latency, error rates, SLO compliance—and make informed decisions based on actual data. This closes the loop between code and reality, enabling agents to write code that responds to real-world conditions.

Conclusion

The gcx CLI tool marks a significant step forward in integrating observability into modern development workflows. By bringing Grafana Cloud directly to the terminal—and empowering agents with production awareness—gcx reduces friction, accelerates incident response, and ensures that code is always built with accurate system insights. Whether you're starting from a greenfield project or enhancing an existing service, gcx provides the tools to achieve full observability in minutes, not days.