Summary

Promotes the deployment/agent configuration model classes out of the heavy ADK (agentex.lib.sdk.config) into a new canonical, hand-authored namespace agentex.config.* that ships in the slim agentex-client wheel. REST-only consumers can now import these models without installing the ADK runtime (temporalio / fastapi / litellm / …). Back-compat shims at the old paths keep existing imports working.

Deployment-models analog of #371 (which did this for protocol types). Tracking: AGX1-292.

Downstream: egp-api-backend (SGP-5970) currently hand-copies these models in agentex_sdk_deployment_models.py because importing them required the full ADK. This promotion lets it drop the copy.

What moved

Promoted to agentex.config.* (pure pydantic models):

ConfigBaseModel (agentex/config/_base.py) inlines the ConfigDict(from_attributes=True, populate_by_name=True) the former model_utils.BaseModel provided — the behavior-preserving swap #371 established. DeploymentConfig / InjectedSecretsValues' nested class Config: validate_by_name = True is folded into it (redundant with populate_by_name; keeping both model_config and a nested Config on one class raises in pydantic v2).

The promoted agent_configs.py / local_development_config.py validators are also modernized from the deprecated pydantic-v1 @validator to @field_validator, so the new public surface emits no PydanticDeprecatedSince20 warnings for importers.

environment_config split

The module mixed pure models with a yaml-loading from_yaml. The model classes (incl. AgentEnvironmentsConfig with its accessors/validators) are promoted; the from_yaml/yaml loading stays in lib as the load_environments_config free function (+ load_environments_config_from_manifest_dir) so the promoted models stay slim-safe.

Back-compat delta: the promoted AgentEnvironmentsConfig no longer carries a .from_yaml() classmethod. The two in-repo callers (validation.py + the manifest-dir helper) and the loader tests are repointed to load_environments_config; an external caller via the lib path would switch to the free function.

agent_manifest split (same pattern)

egp-api-backend needs the AgentManifest model (it validates manifest dicts; it does its own yaml parsing and never touches an agentex loader). So the model is promoted to agentex.config.agent_manifest, while the yaml loader and Docker build-context machinery stay in lib:

• AgentManifest.from_yaml() → load_agent_manifest() free function in lib (7 callers repointed).
• AgentManifest.context_manager() → build_context_manager() free function in lib (2 callers); BuildContextManager stays in lib.
• AgentManifest.load_environments_config() method dropped; its 1 caller uses the existing load_environments_config_from_manifest_dir.

Back-compat delta: like AgentEnvironmentsConfig, the promoted AgentManifest drops from_yaml/context_manager/load_environments_config methods (all CLI-internal; no examples/tutorials use them). The AgentManifest type is still re-exported from the lib path.

Left in lib (CLI/build machinery)

agent_manifest.py (loader + BuildContextManager), validation.py, project_config.py — they use yaml / jinja2 / subprocess / tar and are CLI-only.

Shims

Back-compat re-export shims at the old agentex.lib.sdk.config.{agent_config,build_config,deployment_config,local_development_config,environment_config} and agentex.lib.types.{credentials,agent_configs} paths. In-repo lib consumers are repointed to the canonical agentex.config.* paths, so the shims are purely external-facing.

⚠️ Stainless dashboard action required

agentex.config is hand-authored and must be protected from codegen regen the same way agentex.protocol / adk/** are. That protection lives in the Stainless dashboard keep_files, not this repo (confirmed: no .stainless config exists locally; the pyproject.toml comments document keep_files: ["adk/**"] as dashboard config, and #371 added agentex.protocol with no repo-side codegen change).

Action: add src/agentex/config/** to the dashboard keep_files. Until that lands, codegen can clobber the new directory. This intersects the open codegen-conflict PR stainless-sdks/agentex-sdk-python#44 — flagging rather than silently resolving.

Verification (local)

• Slim-safety (decisive): uv build --all-packages --wheel → all agentex/config/* files ship in agentex_client-*.whl and are absent from the ADK wheel. Installed only the slim wheel in a clean venv (6 deps: httpx, pydantic, anyio, distro, sniffio, typing-extensions — no temporalio/fastapi/litellm/yaml/ddtrace) and imported every promoted model: OK.
• ./scripts/lint (ruff + pyright + import agentex) and ./scripts/check-slim-deps pass. (The lone pyright error is httpx_aiohttp in untouched generated _base_client.py — pre-existing, unrelated.)
• Old agentex.lib.* imports still resolve via shims with class identity preserved — pinned by new tests/test_config_shims.py.
• Full ./scripts/test (3.12) locally: 918 passed, 1376 skipped (skips are the API-endpoint tests requiring the prism mock server; all runnable tests pass, including the new shim tests).

Test plan

• ./scripts/test (3.12) passes locally; CI to confirm across 3.12 / 3.13 + ruff/pyright/slim-deps.
• Slim wheel contains agentex/config/*; importable with only the 6 slim deps.
• Old agentex.lib.sdk.config.* / agentex.lib.types.* imports keep working via shims.

🧑‍💻🤖 — posted via Claude Code

Greptile Summary

This PR promotes deployment/agent configuration Pydantic model classes from the heavy ADK namespace (agentex.lib.sdk.config.*, agentex.lib.types.*) into a new slim-safe agentex.config.* package so REST-only consumers can import them without pulling in the full ADK runtime. Back-compat shims at all original module paths preserve class identity for existing imports.

• New agentex.config.* package: pure-pydantic models for AgentConfig, BuildConfig, DeploymentConfig, AgentManifest, AgentEnvironmentsConfig, TemporalConfig, CredentialMapping, etc., backed by ConfigBaseModel with from_attributes=True / populate_by_name=True to preserve prior behaviour.
• Method extraction: yaml-loading logic and Docker build machinery extracted to free functions (load_agent_manifest, build_context_manager, load_environments_config) in agentex.lib.sdk.config.*, keeping the promoted models slim-safe; all internal callers repointed.
• Shim tests added (tests/test_config_shims.py) to assert symbol parity and class-object identity across both import paths.

Confidence Score: 5/5

Safe to merge — the refactor is well-contained, all internal callers are repointed, and shim tests verify class-object identity and config preservation across both import paths.

The structural split is clean: pure pydantic models land in the slim wheel, yaml-loading and Docker build machinery stay in lib, and every public class is re-exported from its original path with the same object identity. The new shim tests directly assert the contracts that could break. The only observations are a missing ticket number on an existing TODO and a minor question about whether the Temporal leaf-type classes intentionally drop from_attributes=True — neither affects runtime correctness for current callers.

src/agentex/config/agent_configs.py — uses plain pydantic.BaseModel instead of ConfigBaseModel for the Temporal config types; worth a quick confirmation that this is intentional.

Important Files Changed

Fix the following 2 code review issues. Work through them one at a time, proposing concise fixes.

---

### Issue 1 of 2
src/agentex/config/agent_configs.py:23
The `TODO` comment lacks a ticket number. The team's convention is to include a Linear/Jira ticket reference so the cleanup work is trackable by searching for the ID.

```suggestion
# TODO(AGX1-???): Remove this class when we remove the agentex agents create
```

### Issue 2 of 2
src/agentex/config/agent_configs.py:1-7
**`ConfigBaseModel` not used for `TemporalConfig` / `TemporalWorkerConfig` / `TemporalWorkflowConfig`**

These classes use plain `pydantic.BaseModel` rather than `ConfigBaseModel` (which carries `from_attributes=True` and `populate_by_name=True`). All other promoted models in this PR use `ConfigBaseModel` to preserve the behaviour of the old `model_utils.BaseModel`. Worth confirming this is intentional and that no downstream consumers rely on either config flag for these specific types.

Reviews (3): Last reviewed commit: "refactor(config): promote deployment-con..." | Re-trigger Greptile