# Buildkite CLI browse command

The `bk browse` command allows you to open Buildkite resources in a web browser from the command line.

Open Buildkite resources in your web browser. Without arguments, the pipeline for the current project is resolved and opened, with its builds list filtered to the current git branch.

```bash
bk browse [<build>] [flags]
```

## Arguments

| Argument | Description |
| --- | --- |
| `[<build>]` | Build number, org/pipeline/number slug, or build URL to open. Omit to open the pipeline page. |

## Flags

| Flag | Description |
| --- | --- |
| `-b`, `--branch=STRING` | Filter the pipeline builds list to this branch. Defaults to the current git branch. |
| `-n`, `--no-browser` | Print destination URL instead of opening the browser. |
| `-p`, `--pipeline=STRING` | The pipeline to use. This can be a {pipeline slug} or in the format {org slug}/{pipeline slug}. |
| `-s`, `--settings` | Open the pipeline's settings page. |
| `--all-branches` | Open the pipeline builds list without a branch filter. |
| `--debug` | Enable debug output for REST API calls |

## Examples

Open the current project's pipeline, filtered to the current branch:

```bash
bk browse
```

Open build #420 on the current project's pipeline:

```bash
bk browse 420
```

Open a build on a specific pipeline:

```bash
bk browse 420 -p monolith
```

Open a build by slug (bypasses project pipeline resolution):

```bash
bk browse my-org/my-pipeline/420
```

Open the pipeline settings page:

```bash
bk browse -s
```

Filter the pipeline builds list to a specific branch:

```bash
bk browse -b main
```

Open the pipeline builds list across all branches:

```bash
bk browse --all-branches
```

Print the URL instead of opening a browser:

```bash
bk browse 420 -n
```