caricamentoβ¦
caricamentoβ¦
The provider is the team's brain β and the only thing you pay for
Three are supported and tested. Pick one β you can switch later in a couple of commands.
The setup wizard already asks for your provider and runs the sign-in. If you ran jht setup, you're likely done. To do it (or redo it) by hand:
jht providers list # claude | codex | kimi
jht providers use kimi # set the active one
jht providers update kimi # install its CLI inside the containerThese are subscriptions, not API keys: you log into your provider account through a browser device-flow, the same way their own CLI does. The wizard launches this for you; to force a clean login:
jht oauth-login # opens the provider's device-flow login in a TTYFollow the on-screen URL + code, confirm in the browser, and the credentials are stored inside the container (never in git).
jht providers current # active provider + model
jht providers check # confirm the CLI is installed and reachable
jht doctor # full health check β must exit 0Change your mind any time:
jht providers use claude && jht providers update claude
jht team stop --all && jht team start # reload the teamThese docs are the essentials. For the full detail, the exact flags and the code itself, read the source: AI-AGENT-INTEGRATION.md β