Advanced on BMC

Chrome Profiles

Mon, 01 Jan 0001 00:00:00 +0000

BMC can open the AWS console in a dedicated, isolated Chrome profile per AWS account. Each profile has its own cookies and session — no cross-account contamination.

Enable #

{
 "console": {
 "chrome_profiles": true,
 "chrome_binary": "google-chrome"
 }
}

For Brave or Chromium:

{
 "console": {
 "chrome_profiles": true,
 "chrome_binary": "brave-browser"
 }
}

How it works #

On first use for a profile, BMC:

NixOS / home-manager

Mon, 01 Jan 0001 00:00:00 +0000

Installing BMC #

NixOS (configuration.nix) #

{
 inputs.bmc.url = "github:wearetechnative/bmc";

 outputs = { nixpkgs, bmc, ... }: {
 nixosConfigurations.myhost = nixpkgs.lib.nixosSystem {
 modules = [
 {
 environment.systemPackages = [
 bmc.packages.${system}.bmc
 ];
 }
 ];
 };
 };
}

home-manager #

{
 inputs.bmc.url = "github:wearetechnative/bmc";

 home.packages = [ inputs.bmc.packages.${system}.bmc ];
}

Shell integration with home-manager #

bmc install-shell-integration prints snippets instead of writing files when it detects a managed shell config. Add them manually:

Migration from bash version

Mon, 01 Jan 0001 00:00:00 +0000

If you were using the previous bash-based version of BMC, here is what changed and how to migrate.

Steps #

Install the new binary (same name: bmc)
Run bmc install-shell-integration — replaces the source bmc profsel pattern
Create ~/.config/bmc/config.json — replaces ~/.config/bmc/config.env
Run bmc doctor to verify setup

Breaking changes #

Old	New
`source bmc profsel`	`eval "$(bmc profsel)"` — handled automatically by the shell wrapper
`~/.config/bmc/config.env`	`~/.config/bmc/config.json`
`bmc gencompletions`	`bmc completion bash\|zsh` (Cobra built-in)

Config migration #

Old config.env: