You can now store scripts to set up orbs outside of your repository. Amp can store pre-clone and pre-setup scripts in your project settings and access them when spawning an orb.
The pre-clone setup script gives Amp anything it needs before it clones the repository:
- Install Git extensions that fetch files during checkout.
- Configure certificates for an internal Git server.
- Configure a network proxy needed to reach the Git server.
- Connect the orb to a private network with Tailscale (known issue: use
TAILSCALE_API_KEY, OIDC is not yet working with pre-clone scripts). - Install a credential helper required by the Git server.
The pre-setup script lets you work with orbs when you aren't ready to commit setup files to the repository. Amp agents and Puck can access the scripts and set them for you. Give Puck this prompt, or start a thread for the project with this prompt:
Amp will then inspect the repository and decide which work belongs before or after the clone. It will write and test the scripts, then save them in the project settings.
The scripts are also available on the project settings page, where you can review or edit them by hand.