Description
When running agentcore create in corporate/enterprise environments that require proxy configurations or custom PyPI indexes, the generated pyproject.toml does not include the necessary settings for uv sync to succeed. The Python environment setup step fails because uv cannot reach the default package index or requires additional configuration (e.g., proxy settings, custom index URLs, trusted hosts) that cannot be injected before the install runs.
Use Case
Organizations behind corporate proxies or using private PyPI registries need to configure pyproject.toml with settings such as:
- Custom
[[tool.uv.index]] entries pointing to internal PyPI mirrors
- Proxy configuration
- Trusted host declarations
- Additional source repositories
Currently, agentcore create generates a fixed pyproject.toml and immediately runs uv sync, with no opportunity to customize the file beforehand. This causes the Python environment setup to fail in restricted network environments.
Proposed Solution
Add support for one or more of the following:
- A
--pyproject-extras flag (or config file option) that merges user-provided TOML settings into the generated pyproject.toml before uv sync executes.
- A
--skip-install flag (shared with the npm install skip) that creates the project scaffolding without running uv sync, allowing users to modify pyproject.toml before installing manually.
- A
--uv-index-url flag to specify a custom package index URL that gets written into the generated pyproject.toml.
- Support for a user-level or project-level config file (e.g.,
.agentcorerc) where Python-specific registry and proxy constraints can be defined.
Acceptance Criteria
Additional Context
This is a common blocker for enterprise teams operating behind corporate proxies or restricted networks. Combined with a --skip-install flag (also requested for package.json customization), this would significantly improve the onboarding experience for enterprise users.
Description
When running
agentcore createin corporate/enterprise environments that require proxy configurations or custom PyPI indexes, the generatedpyproject.tomldoes not include the necessary settings foruv syncto succeed. The Python environment setup step fails becauseuvcannot reach the default package index or requires additional configuration (e.g., proxy settings, custom index URLs, trusted hosts) that cannot be injected before the install runs.Use Case
Organizations behind corporate proxies or using private PyPI registries need to configure
pyproject.tomlwith settings such as:[[tool.uv.index]]entries pointing to internal PyPI mirrorsCurrently,
agentcore creategenerates a fixedpyproject.tomland immediately runsuv sync, with no opportunity to customize the file beforehand. This causes the Python environment setup to fail in restricted network environments.Proposed Solution
Add support for one or more of the following:
--pyproject-extrasflag (or config file option) that merges user-provided TOML settings into the generatedpyproject.tomlbeforeuv syncexecutes.--skip-installflag (shared with the npm install skip) that creates the project scaffolding without runninguv sync, allowing users to modifypyproject.tomlbefore installing manually.--uv-index-urlflag to specify a custom package index URL that gets written into the generatedpyproject.toml..agentcorerc) where Python-specific registry and proxy constraints can be defined.Acceptance Criteria
agentcore create --skip-installgenerates the full project scaffolding without executinguv sync.agentcore create --uv-index-url <url>(or equivalent syntax) configures the generatedpyproject.tomlwith the provided index URL beforeuv syncruns.pyproject.tomlwithout overwriting template defaults.agentcore create --help.uv syncstill runs by default.Additional Context
This is a common blocker for enterprise teams operating behind corporate proxies or restricted networks. Combined with a
--skip-installflag (also requested forpackage.jsoncustomization), this would significantly improve the onboarding experience for enterprise users.