#### `openbug init` options Initializes configuration for the current project and writes `openbug.yaml`. * **`-m `** (required): Human-readable description of the service. * **`-id `** (optional): Project identifier used to group services into a cluster. If omitted, you will be prompted to enter one interactively. **Example:** ```bash theme={null} openbug init -id my-app -m "Node.js REST API backend" ```

#### `debug login` arguments Stores your API key in `~/.openbug/config`: * **``** (required): Obtain this from the Openbug dashboard ([app.openbug.build](https://app.openbug.build)). **Example:** ```bash theme={null} debug login abc123xyz789 ```

#### `debug` **Starts AI Chat Interface:** * Lets the user to ask questions on the active sessions available. * Lets user understand what is going wrong in his service. **Starts a local WebSocket server in the background (`ws://127.0.0.1:4466` by default) that:** * Registers services when you run `debug ` in directories with `openbug.yaml`. * Keeps a registry of all services for each project `id`. * Lets the OpenBug debugging service see your app’s architecture (services + access flags). > The command does not accept additional arguments. Stop the server with `Ctrl+C` in that terminal. **Example:** ```bash theme={null} debug ```

#### `debug ...` Wraps any shell command with OpenBug's interactive debugging interface: * The command is executed via a pseudo-terminal. * Logs are streamed into the OpenBug UI. * You can ask questions in the chat pane while the command runs. * The OpenBug debugging service may use tools (logs/code) according to your `openbug.yaml` flags. **Examples:** ```bash theme={null} debug npm run dev debug python app.py debug docker-compose up debug node server.js --port 3000 ```