opscompanion-init

OpsCompanion Setup

You are helping the user configure OpsCompanion (opc) for their Claude Code environment.

Preflight

1. Check that opc is installed:

   command -v opc || which opc
   

2. If not installed, install via Homebrew:

   brew install opscompanion/opc/opc
   

   Do NOT suggest building from source. Always use Homebrew.

Configuration

Run the interactive init to configure API key and endpoint:

opc init

This writes config to ~/.config/opscompanion/config.json.

For development/demo mode, the user can use mock-key as the API key — this enables full mock responses without a real backend.

Install for Claude Code

After init succeeds, run the installer to set up skills, hooks, and plugin registration in one step:

opc install --agent claude

This will:

• Download/update the OpsCompanion skills repository
• Register the plugin marketplace and install the plugin
• Write .claude/settings.local.json with hooks for:
  • PreToolUse — captures every tool invocation before execution
  • PostToolUse — captures every tool result

All generated hooks include --agent claude so opc knows which runtime is calling it.

Verification

Verify the setup by loading context:

opc --agent claude context

If this prints org/user/integration details, the setup is complete.

After setup, the main observability commands are:

opc --agent claude logs "timeout" --service api --since 1h
opc --agent claude logs tail --service vercel-app --tui
opc --agent claude traces "checkout" --service api --since 6h

Response Format

After completing setup:

• Confirm which config file was written
• Confirm hooks and plugin were installed
• Show the org name from opc --agent claude context to prove it works
• Remind the user to restart their Claude Code session for hooks to take effect