mait.sh1.69.2

Private beta: features and content may change. No warranty; use at your own risk.

Docs / Launcher and command-line tools

AIDC Credentials Bridge

Let workspace Git, Docker and kubectl use authorized sign-ins supplied through compatible sharing.

For workspace owners and developers diagnosing access to private repositories, registries and clusters.

Read from the top for the basics; the later sections go deeper.

Beta

What it doesBasics

  • Live Git and Docker credential sharing
  • Mounted Docker credentials when deliberately supplied
  • Kubernetes connection configuration and on-demand credentials
  • Local session credential management and presence diagnostics

First useBasics

  1. Use the helper supplied for the intended Linux workspace with compatible launcher sharing and the required client.
  2. Run aidcx-credhelper version and aidcx-credhelper probe inside that environment.
  3. Check the intended account and connection settings, then perform an authorized read-only operation on the actual repository, registry or cluster.
  4. Treat an empty answer, zero helper exit or present socket as an intermediate result; require the remote service to accept the intended account.
  5. Remove only temporary trial state through its owner; use issuer-side revocation when access must end.

CommandsAdvanced

$ aidcx-credhelper version
$ aidcx-credhelper probe

Problems and fixesHelp

All AIDC Credentials Bridge problems and fixes →

Good to knowHelp

  • The helper does not log in remotely or grant service permissions; verify an authorized operation with the intended account.
  • Probe reports presence, not provider health. Previously obtained Git and Docker answers can remain in memory during an outage.
  • Stopping sharing or clearing local state does not revoke credentials at their issuer. Kubernetes needs live sharing and a correctly verified cluster connection.