Back

# bam-client (official repo)

* Repo: https://github.com/jito-labs/bam-client.git

The BAM client is the validator-side software that integrates with BAM Nodes.

Mallet uses this in two ways:

1. **CLI knowledge extraction**: capture flags and subcommands per version.
2. **Runtime observability**: surface connection state, throughput, and reconnect cadence.

## Why this matters for Mallet

* Mallet's **CLI Matrix** should become a *generated artifact* (not a hand-maintained guess).
* Mallet's **BAMauto** wants to map observable symptoms → actionable fixes.

## Current status

In this sandbox snapshot, Mallet ships a **versioned CLI knowledge schema** and placeholders for automated extraction.
The next step is to wire a pipeline that:

* pulls `bam-client` tags/releases
* runs `--help` for `bam-client` and the validator binaries
* parses the output into `packages/cli-matrix/data/*`