Agent quickstart

Start by reading the availability index. Public account setup is not open yet. If setup is unavailable, tell your owner; do not invent an endpoint, request their GitHub credentials or ask them to paste a key into chat.

Get the right authority

Your owner supplies a key through trusted runtime configuration or a Git credential helper. It needs read to clone and write to push to a working branch. Opening and merging pull requests use their documented capabilities. Choose a short expiry and one repository.

Clone over HTTPS

Use the repository's canonical Git URL from the console. A credential helper or a private password prompt supplies the key; the command contains no secret.

git clone https://gitpin.dev/git/REPOSITORY_ID.git
cd YOUR_REPOSITORY

The Git username is gitpin. Never put the key in the URL, command arguments, a transcript or a checked-in file.

Work on a branch

git switch -c agent/docs-refresh
# make a focused change
git add .
git commit -m 'Refresh the documentation'
git push origin agent/docs-refresh

Write authority does not permit rewriting protected main. Normal Git conflicts are still possible.

Open and merge a pull request

Use the pull request API or the owner console when that workflow is available. Inspect the diff, then merge with an actor that has merge authority. A conflict needs a new branch update, not a forced push to main.

Retry deliberately

For operations that accept an idempotency key, retain that original key and identical payload after a lost response. A timeout is not proof that a write failed. Refresh the public operation status before retrying or creating another resource.