Ops Console Install
Open source · macOS

A local console on top of Claude Code.

Ops Console watches how your services are doing in Datadog. When a route fails, the agent reproduces it in a scratch copy of your code and writes a report. You review it. Only then does the agent fix the code and open a pull request. It never merges.

curl -fsSL https://raw.githubusercontent.com/narrowananth/ops-console/main/install.sh | sh

Needs macOS 13.5 or later, Apple silicon or Intel. No sudo.

From a failing route to a pull request

The agent does the legwork. You decide at each step that changes something.

  1. Watch

    Monitor scans each Service's logs through Datadog and raises an Alert for every kind of failure it finds.

  2. Verify

    You start a Verification. The agent follows the log through the code, replays the request and tests with mock data, in a scratch copy. Your checkout stays untouched.

  3. Review

    You read the Report: the steps, the replayed request, the root cause and the proposed fix. Confirm it or dismiss it.

  4. Fix

    After you confirm, the agent changes the code on a branch and runs the tests. The console pushes the branch and opens the pull request. You merge.

What's in it

One local app instead of a dozen tabs and terminals.

Monitor

Datadog health for each Service, its Alerts, and the Verifications and Fixes that follow.

Workspace

Sessions with the agent, each in its own git worktree. A Browser panel, a Terminals dock, pull request review and the files the agent wrote for you.

Playbooks

Write the rules and ordered steps the agent follows for each task. The built-in Playbooks are read-only, and you can copy and edit them.

Connections

Databases the agent may use, each with an Access Level that is enforced when its server launches. PROD is always marked.

Claude accounts

Add several Claude accounts, see each one's usage, and let the console switch when one nears its limit. CLIProxy works too.

Dev tools

Ask a question in plain words and have the agent query your databases and queues, scoped to the Connections you choose.

Connect once, sign in in your browser

Each Connector signs in on its own and keeps its token in the macOS Keychain.

  • Datadog
  • Jira
  • GitHub
  • GitLab
  • Bitbucket
  • Slack
  • Sentry
  • Shopify
  • slashdocs
  • Google Docs
  • Google Sheets
  • Google Drive

How Connectors work

Google Docs, Sheets and Drive

Sign in to Google once in Ops Console and every Claude account you use can read your Docs and Sheets and search your Drive, with or without CLIProxy. Docs and Sheets can be edited. Drive is read-only. Ops Console touches a file only when the agent calls a Google tool, and your Google data is never sent to the project. See the privacy policy and the Google guide.

Built so the agent can't surprise you

  • It never merges a pull request. Every run denies the merge commands and tools.
  • A Verification writes only in a scratch copy. Nothing reaches your checkout or a database.
  • Every run's commands go through the macOS sandbox, which has no switch to turn it off.
  • PROD Connections are read-only for the agent, and a write to PROD asks for your approval in every Access mode.
  • Log text is data, never an instruction.
  • The server listens on 127.0.0.1 only, and secrets stay in the Keychain.

Read how each rule works

Free and open

Ops Console is released under the MIT License. It has no accounts, no telemetry and no server of ours in the loop: it runs on your Mac. Read the code, run it from source, or send a change.