A clear path forward
How can my environment install private packages securely?
Give the environment approved access to your private packages, then ask Agent to use them in the build. Git repo access alone does not grant access to private npm or Python packages.
A package registry is the service that stores those packages. It needs its own access setup. That is why fetching code can work while a package sign-in fails.
- Ask Agent which package service and access the build needs. Use a development credential with only the required package-access permissions.
- For a one-off package installation in your private chat, enter the credential through Agent’s secure secret form. A chat-scoped secret is not automatically available in another chat or a reusable environment build.
- For reusable builds, have your administrator configure an approved secrets manager or workload identity and the required registry permissions. Ask Agent to configure package authentication without printing or saving credential values, then test installation in a fresh build.
Connecting a secrets manager does not load its values into your app on its own. Tell Agent which approved project or secret path to use. Never place secret values in chat, Git, logs or the saved image. See environment secrets for setup choices.
Was this page helpful?
Still stuck? Try troubleshooting with Agent.
Still stuck? Try troubleshooting with Agent.
Copy this prompt and paste it into Agent. For a project issue, open the project where it happens first. Add what happened and anything you've already tried. Don't include passwords, API keys, database connection strings or payment-card details.
Copying does not open Agent or send a support request. Agent availability and usage depend on your account.
Can't open your project, or need another kind of help? Get help.