Git credentials for coding sessions
Found this helpful? Share it:
Found this helpful? Share it:
A coding agent delivers through ordinary git and provider command-line tools on
the computer you selected. There is no GitHub or GitLab connection to configure
in idapt. You have two ways to authenticate, and the first is usually already
done.
If these already succeed for the operating-system user the agent runs as, nothing else is needed. Tell the agent to use the existing setup.
git fetch
gh auth status # or: glab auth statusThe agent leaves that configuration intact: it does not replace a remote, a credential helper, a signing key, or a provider profile unless you ask it to.
Not sure which user the commands run as? The skill states it when it confirms the environment, and the computer's Dashboard lists the allowed users.
Use a workspace credential when the token should not be stored on the computer, for example on a shared machine or a short-lived cloud computer.
Open the workspace Credentials page and create a credential holding the provider token.
Name it for the job, such as github-push-token. Never paste the value into
Chat.
In the coding chat, name the credential and the single command that needs it.
Check the push or pull-request URL the agent reports when the command finishes.
idapt resolves the value on the server and injects it into that one command's environment. The agent receives the name, not the value, and output redaction removes matches from what comes back.
Give the token the narrowest provider scope and the shortest lifetime the task allows. Workspace roles and management live in Credentials.
Ask for injection into a one-shot command only. Do not ask the agent to write a token into a repository file, a remote URL, a shell profile, a command argument, a persistent terminal, a tmux session, or Git configuration. A persistent session does not receive credential injection at all.
Redaction is not a sandbox. A command that receives a credential can use it, log it, or send it somewhere. Repository hooks and dependency install scripts run with the same environment, so inject a credential only into a command and a project you trust.
With either method the agent can:
git status, branches, remotes, and diffs.gh or glab.When the provider CLI is missing, it pushes the branch and returns the URL for you to open the request yourself.
Related articles
Start coding with idapt Code
Point a normal idapt Chat at a paired or cloud computer and have it read the project, change code, run the tests, and report what it did.
Use idapt Code safely
Pick the right machine, grant the two capabilities coding needs instead of full control, and know what an agent command can still reach.
Credentials
Store API keys and app connections once, then let your commands, functions, and agents use them without pasting a key into a chat.
Computer commands and files
Run commands through the daemon and browse remote files with the built-in file manager.
Terminal and SSH
Open a shell on any of your computers from the browser or your own terminal, with no SSH keys to set up.
Was this helpful?