Ops Console Install

Data flow

This page says what moves between your Mac, Anthropic's API and each Connector, and that none of it reaches an Ops Console server. The project runs no server your installation talks to. The privacy policy has the short version.

Who calls the service

  • The console's own calls. A Scan, a Health check, a Recheck, a pull request list and a Pull request opening go from the daemon on your Mac to the service. No model turn is involved. What comes back stays on your Mac.
  • The agent's calls. An MCP Server tool, the output of a run_integration command and a file the agent reads each return their result to the agent, and that result goes on to Anthropic's API as part of the run.

Samples and Reports the console stores reach Anthropic only when a Verification or a Fix puts them in a prompt. This holds for the records of a Log folder too: the daemon reads the folder on your Mac, and the agent never does.

By route

RouteConnectorsWho calls the serviceWhere the result goes
CLI the daemon callsDatadog (pup), GitHub (gh), GitLab (glab), Bitbucket (bkt), slashdocsThe daemon, for the console's own reads. For the agent, the daemon runs the command it asks for through run_integration: a read at once, a write after your Approval unless the Session is in full mode or you chose not to be asked again.A console read stays on your Mac. A command the agent asked for returns its output to the agent, so it goes to Anthropic's API.
MCP Server Claude Code callsJira, Slack, Sentry, Shopify, GitHub, Datadog, and Bitbucket through AtlassianClaude Code, from your Mac, with the sign-in the Connector holdsThe agent, then Anthropic's API
Log folderOpenTelemetry logsThe daemon, which reads the folder on your Mac as you, read only. No service is called.A console read stays on your Mac. The records reach Anthropic's API only as Samples in a prompt. The agent never reads the folder.
Google bridgeGoogle Docs, Google Sheets, Google DriveThe bridge the console ships, which calls the product's REST API when the agent calls a Google toolThe agent, then Anthropic's API. The agent never sees the refresh token, which stays in your Keychain.

Secrets stay in your Keychain and are read at the moment of use.

Anthropic's API

With the console's own Claude accounts, the agent's prompts, the files it reads and every tool result go to Anthropic's API under the active Claude account, and Anthropic handles them under its own terms.

With CLIProxy as the Claude account hub, they go to a CLIProxy server on your Mac, which sends them on to the providers you configured. The address must be a loopback address.

Claude Code, which the console runs, has its own traffic to Anthropic and its own settings. The console sets no opt-out for it and makes no promise about it. Anthropic's terms and your Claude Code settings decide.

Production data

Rows the agent reads from a PROD Connection are part of what goes to Anthropic's API. The Access Level of a Connection limits what the agent may do with it.

The project's servers

None of the above goes to the project. The only requests tied to the project go to GitHub: the update check asks for the latest release, when the console checks for a new version and when you run ops-console update, and an update downloads from it. GitHub sees those requests. The app never calls opsconsole.org, which is a static site.

See Safety for what keeps the server local, and the privacy policy for what is stored on your Mac and how to remove it.

Edit this page on GitHub