View and change configuration with ConfigHub UIs

1. Start with the official GUI

You need: access to a ConfigHub organization containing configuration you are allowed to inspect. No saved configuration yet? Follow the official introductory tutorial first. A cluster is not needed just to browse stored configuration.

Use	When you want	Start
ConfigHub GUI — official main route	To view and operate on configuration with Enterprise Server or SaaS	Open your team’s ConfigHub server or SaaS instance and sign in
ConfigHub UI SDK	To adapt the interface to new use cases and plugins, including standalone, disconnected use	Choose this when building a custom interface; it is not required for this walkthrough
cub-commander — early experimental TUI	To try browsing, querying and comparing configuration in a full-screen terminal	Use the commands below
cub scout	To inspect what a cluster reports now	Use the separate Scout Guide

A Unit is a stored piece of configuration. A Space groups Units. A revision records a version of that configuration. These are intended settings; live observations answer a different question.

2. Find one configuration in the official GUI

Confirm the organization you are viewing.
Find a component or Space you recognize, then open one Unit. If you have no entries or lack permission, ask for a tutorial Space or access; do not create production data just to follow this Guide.
Read its configuration and revision. Identify the environment from its labels and relationships, rather than guessing from its name.

Your first result: you can name the configuration, the environment it belongs to and the revision you inspected. Keep the view read-only for now. Saving an edit changes stored configuration; it is a separate step from opening a Unit. For the next hands-on task, the official Make a Change tutorial shows editing the base, promoting and releasing as separate steps.

3. Optional: try the experimental terminal UI

Install the cub CLI and sign in to the same server and organization you intend to inspect. cub-commander is an early experimental terminal UI (TUI), not the main product interface. Its interface can change between versions.

cub auth login
cub plugin install confighub/cub-commander@v0.3.0
cub commander

Start at the browse by chooser. Follow Space → Unit, or the labels your organization provides. Open a row to inspect it. Use Ctrl+/ for help and Ctrl+Q to quit.

When two environments exist, mark one selection with m, mark the other with m, then press d to compare matching Units. Differences show intended configuration, not proof of what either cluster runs. Commander can also explain a query as a cub command.

Stop after inspection. On a Unit’s Data tab, e opens an editor and saving writes a revision. That is a write operation, not another viewing shortcut. Review the environment and diff before saving; promotion and release are separate operations with their own consequences.

4. Connect intended configuration to a live observation

This is optional. You need cluster read access and an explicit mapping from a ConfigHub Target ID to a kubeconfig context. Do not infer that mapping from a similar name.

Use Commander’s Resource Evidence tab

The documented v0.3.0 pairing uses Scout v2.10.0. Replace both placeholders with your confirmed Target ID and context; angle brackets are not literal values.

cub plugin install confighub/cub-scout@v2.10.0
cub commander --scout-binding '<target-id>=<kube-context>'

If Scout is already installed, follow the version-specific install and upgrade instructions rather than replacing a newer installation blindly.

Open a Resource and choose 3 Evidence. Check the identity, observation time and omissions. Press r to refresh; revisiting a tab does not refresh its snapshot. Missing bindings or unavailable evidence are not a health verdict. This view is neither a desired/live diff nor proof of successful delivery.

5. Make your next step deliberate

For a first managed change, continue with the official change tutorial. To understand deployment and promotion first, use Deploy and manage with ConfigHub. To investigate the live side, return to Scout.

The official GUI is the main product route. The UI SDK is for adapting that interface to new use cases and plugins; it can also run standalone and disconnected. Disconnected use does not provide a live server or cluster view. The experimental TUI and CLI offer other ways to work with the ConfigHub model; their features and permissions can differ. Source review for this Guide: Commander v0.3.0 and the official tutorial. No new authenticated UI or live-cluster acceptance is claimed here.