pipecatcloud 0.7.1__tar.gz → 1.0.0__tar.gz

{pipecatcloud-0.7.1 → pipecatcloud-1.0.0}/.github/workflows/python-compatibility.yml

@@ -42,4 +42,4 @@ jobs:
       - name: Verify CLI loads
         run: |
           uv run python --version
-          uv run pcc --help
+          uv run python -c "from pipecatcloud.cli.entry_point import entrypoint_cli_typer"

{pipecatcloud-0.7.1 → pipecatcloud-1.0.0}/.github/workflows/tests.yml

@@ -33,9 +33,6 @@ jobs:
         run: |
           uv sync --group dev
 
-      - name: Test Docker commands
+      - name: Run tests
         run: |
-          uv run pytest tests/test_docker_commands.py -v
-
-      # Note: test_agent_sessions.py is excluded because it requires complex
-      # API mocking for CI. These tests can be run locally with proper auth.
+          uv run pytest -v

{pipecatcloud-0.7.1 → pipecatcloud-1.0.0}/CHANGELOG.md

@@ -5,6 +5,98 @@ All notable changes to **Pipecat Cloud** will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [1.0.0] - 2026-06-19
+
+### Added
+
+- New `pipecat cloud spend-limit` command group for managing the organization-level
+  spend cap:
+  - `pipecat cloud spend-limit show` prints the current limit, period spend, period
+    boundaries, and blocked state. Pass `--json` for machine-readable output.
+  - `pipecat cloud spend-limit set <amount>` sets a new limit. The amount is in
+    dollars with at most two decimal places (e.g. `50` or `12.34`). The
+    command prompts before setting the limit to `$0` or below current
+    spend; pass `-y/--yes` to skip the prompt.
+  - `pipecat cloud spend-limit clear` removes the limit, with the same confirmation
+    behavior.
+
+- Any CLI command that surfaces an HTTP 402 `SPEND_LIMIT_REACHED` error now
+  renders a wrapped remediation message that explains how to unblock new
+  sessions, instead of a generic API error panel.
+
+### Changed
+
+- **The agent `*SessionArguments` types are now thin subclasses of pipecat-ai's
+  runner argument types** (`SessionArguments`, `PipecatSessionArguments`,
+  `DailySessionArguments`, `WebSocketSessionArguments`, `SmallWebRTCSessionArguments`).
+  Because each is a subclass of the matching `pipecat.runner.types.*RunnerArguments`,
+  it interoperates with pipecat's runner machinery — `create_transport(args)` and
+  `isinstance(args, DailyRunnerArguments)` both work — so a bot's `bot()` may type
+  the argument as either the `*SessionArguments` type or the underlying
+  `*RunnerArguments` type.
+
+- **`pipecat-ai` is an optional dependency (`pipecatcloud[pipecat]`).** Only the
+  agent session-argument types need it; the SDK (`Session`, the API client) and the
+  CLI do not. The types are now lazily imported, so plain `import pipecatcloud`
+  works without pipecat-ai installed. *Migration:* if you use the `*SessionArguments`
+  types, install `uv add "pipecatcloud[pipecat]"` (or otherwise have pipecat-ai
+  in your environment); accessing them without pipecat-ai raises a clear `ImportError`.
+  This also removes the old standalone fallback `*RunnerArguments` definitions
+  (deprecated since 0.2.1); `pipecatcloud.agent` now imports the real types from
+  pipecat-ai.
+
+### Fixed
+
+- **`pipecatcloud` now exports `SmallWebRTCSessionArguments`** (the SmallWebRTC agent
+  session type), not `SmallWebRTCRunnerArguments`. The `SmallWebRTCSessionArguments`
+  dataclass existed but was unreachable from the top-level package, while a pipecat-ai
+  runner base type was exported in its place — inconsistent with the other transports'
+  `*SessionArguments` exports. `from pipecatcloud import SmallWebRTCRunnerArguments` no
+  longer works (import it from `pipecat.runner.types` if you need the base type).
+
+### Removed
+
+- **The standalone CLI** (`pcc` / `pipecatcloud` console scripts and `python -m
+  pipecatcloud`). Pipecat Cloud is no longer a directly-invocable CLI; its commands are
+  exposed through the **Pipecat CLI** as `pipecat cloud ...` (the same commands that have
+  been available there for some time). *Migration:* install the Pipecat CLI with
+  `uv tool install pipecat-ai-cli` and replace `pcc <command>` with
+  `pipecat cloud <command>` (e.g. `pcc auth login` → `pipecat cloud auth login`). The
+  Python SDK (`pip install pipecatcloud`) is unchanged.
+
+- **Legacy Krisp (the `--enable-krisp` flag and the `enable_krisp` config/API field).**
+  The legacy Krisp model is no longer supported anywhere — use **Krisp VIVA**
+  (`--krisp-viva-audio-filter`, or the `[krisp_viva]` section in `pcc-deploy.toml`).
+  Removed the `--enable-krisp` CLI flag, the `enable_krisp` field on the deploy config,
+  its `pcc-deploy.toml` key, and the `enableKrisp` API payload. A `pcc-deploy.toml` that
+  still contains `enable_krisp` will now error with a message pointing to `[krisp_viva]` —
+  remove it.
+
+- **`pipecat cloud deploy --min-instances` / `--max-instances`** (deprecated
+  since 0.4.x). Use `--min-agents` / `--max-agents`. The corresponding
+  `min_instances` / `max_instances` fields were removed from `ScalingParams`.
+
+- **Passing a Personal Access Token as a positional argument to `pipecat cloud auth use-pat`.**
+  The command now always reads the token from a secure hidden prompt (tokens on the
+  command line leak to shell history and process listings).
+
+- **The deprecated `pipecat cloud organization keys delete` alias.** Use
+  `pipecat cloud organization keys revoke`.
+
+## [0.7.2] - 2026-05-29
+
+### Fixed
+
+- `pcc deploy` no longer crashes with `AttributeError: 'NoneType' object has
+  no attribute 'get'` when a status poll hits a transient API error (e.g. a
+  502 from a briefly-unavailable API pod). The poll loop now checks for the
+  error before reading the status payload, and transient failures (5xx,
+  network blips, a not-yet-visible service) are retried for up to 5
+  consecutive attempts before giving up. A successful poll resets that
+  budget, so an isolated blip no longer surfaces as a traceback or fails an
+  otherwise-successful deploy. Non-transient errors (4xx, auth) still abort
+  immediately.
+
 ## [0.7.1] - 2026-05-14
 
 ### Fixed

{pipecatcloud-0.7.1 → pipecatcloud-1.0.0}/CLAUDE.md

@@ -4,10 +4,10 @@ Guidance for Claude Code working in this repo.
 
 ## What this is
 
-**Pipecat Cloud** is the Python SDK and `pcc` CLI for deploying and managing Pipecat voice agents on Pipecat Cloud infrastructure. It ships to PyPI as `pipecatcloud`. Users install it to authenticate, build and push container images, deploy agents, manage secrets and scaling, and open sessions against running agents.
+**Pipecat Cloud** is the Python SDK and CLI for deploying and managing Pipecat voice agents on Pipecat Cloud infrastructure. It ships to PyPI as `pipecatcloud`. Users authenticate, build and push container images, deploy agents, manage secrets and scaling, and open sessions against running agents. The CLI is not a standalone command — its commands are exposed through the Pipecat CLI as `pipecat cloud ...`.
 
 - Package root: `src/pipecatcloud/`
-- CLI entry points: `pcc` and `pipecatcloud` (also registered as a Pipecat CLI extension via the `pipecat_cli.extensions:cloud` entry point)
+- CLI: registered as a Pipecat CLI extension via the `pipecat_cli.extensions:cloud` entry point (surfaced as `pipecat cloud`). There is no standalone entry point — no `[project.scripts]` and no `__main__`; the CLI runs only through the Pipecat CLI.
 - Public docs: https://docs.pipecat.daily.co
 
 ## Toolchain
@@ -73,7 +73,7 @@ src/pipecatcloud/
     session_manager.py   SmallWebRTC support for non-Pipecat agents
 tests/                   Pytest suite, parallel to src/
 .github/workflows/       tests.yml, format.yml, publish-pypi.yml, publish-test.yml
-pcc-deploy.toml          Example deployment config consumed by `pcc deploy`
+pcc-deploy.toml          Example deployment config consumed by `pipecat cloud deploy`
 ```
 
 ## Testing conventions
@@ -81,12 +81,11 @@ pcc-deploy.toml          Example deployment config consumed by `pcc deploy`
 - Layout mirrors `src/`. New tests go in `tests/test_<module>.py`.
 - `tests/conftest.py` sets `PIPECAT_CONFIG_PATH` to an isolated temp file **before imports**, pre-populated with `token = "test-token"` and `org = "test-org"`. This prevents tests from reading or clobbering real credentials. Do not bypass it.
 - Async tests use `@pytest.mark.asyncio`. Mock async calls with `unittest.mock.AsyncMock`.
-- `tests/test_agent_sessions.py` is **skipped in CI** because it needs real auth or heavier mocking. Run it locally if you touch session code.
 - `pytest.ini` uses `--import-mode=importlib`. Some tests manually insert `src/` onto `sys.path`, which is expected.
 
 ## CI
 
-- `tests.yml` runs on push to main and PRs. It currently runs `uv run pytest tests/test_docker_commands.py -v` rather than the full suite, so green CI does not guarantee the whole suite passes. Run `uv run pytest` locally before opening PRs.
+- `tests.yml` runs the full suite (`uv run pytest -v`) on push to main and PRs.
 - `format.yml` runs `ruff format --diff` and `ruff check`. Both must pass.
 - `publish-pypi.yml` and `publish-test.yml` are manual dispatches that build and publish a specific git tag.
 

{pipecatcloud-0.7.1 → pipecatcloud-1.0.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: pipecatcloud
-Version: 0.7.1
+Version: 1.0.0
 Summary: Cloud hosting for Pipecat AI applications
 License: BSD 2-Clause License
 Project-URL: Website, https://docs.pipecat.daily.co/
@@ -34,7 +34,7 @@ Python module and CLI for interacting with [Pipecat Cloud](https://pipecat.daily
 
 ### Requirements
 
-- Python 3.10+
+- Python 3.11+
 - Docker and a Docker repository (e.g. Docker Hub)
 - Active [Pipecat Cloud](https://pipecat.daily.co)
   account
@@ -45,31 +45,30 @@ Documentation for Pipecat Cloud is available [here](https://docs.pipecat.daily.c
 
 ### Installation
 
-```shell
-pip install pipecatcloud
+The Pipecat Cloud CLI ships as part of the [Pipecat CLI](https://github.com/pipecat-ai/pipecat-cli) — its commands are available under `pipecat cloud`. Install the Pipecat CLI:
 
-pcc --version
-pcc --help
+```shell
+uv tool install pipecat-ai-cli
+```
 
-# Note: you can use `pcc` or `pipecatcloud` interchangeably
-pcc auth login
+```shell
+pipecat cloud --help
+pipecat cloud auth login
 ```
 
 ! All CLI commands have a `--help` flag that will display the command usage and options.
 
+To use Pipecat Cloud programmatically (without the CLI), install the package directly with `uv add pipecatcloud` and see [Usage in Python scripts](#usage-in-python-scripts).
+
 ## Usage
 
 1. Create an account at [Pipecat Cloud](https://pipecat.daily.co)
 
-2. Login to your account `pcc auth login`
-
-3. (Optional): Clone the quickstart repo [here](https://github.com/pipecat-ai/pipecat-quickstart)
-
-4. Build your agent `docker build --platform linux/arm64 -t your-agent-name .`
+2. Login to your account `pipecat cloud auth login`
 
-5. Push your Docker image to your repository `docker push your-repository/your-agent-name:0.1`
+3. Generate secrets `pipecat cloud secrets set`
 
-6. Deploy your agent `pcc deploy starter-agent your-repository/your-agent-name:0.1`
+4. Build and deploy your agent `pipecat cloud deploy`
 
 ### Usage in Python scripts
 
@@ -101,7 +100,7 @@ if __name__ == "__main__":
 
 ### SSL certificate errors on macOS
 
-If `pcc auth login` fails with an SSL certificate verification error, your Python
+If `pipecat cloud auth login` fails with an SSL certificate verification error, your Python
 installation may not have access to the macOS system certificate store. This is
 common with Python installed via pyenv, conda, or the python.org installer.
 

{pipecatcloud-0.7.1 → pipecatcloud-1.0.0}/README.md

@@ -11,7 +11,7 @@ Python module and CLI for interacting with [Pipecat Cloud](https://pipecat.daily
 
 ### Requirements
 
-- Python 3.10+
+- Python 3.11+
 - Docker and a Docker repository (e.g. Docker Hub)
 - Active [Pipecat Cloud](https://pipecat.daily.co)
   account
@@ -22,31 +22,30 @@ Documentation for Pipecat Cloud is available [here](https://docs.pipecat.daily.c
 
 ### Installation
 
-```shell
-pip install pipecatcloud
+The Pipecat Cloud CLI ships as part of the [Pipecat CLI](https://github.com/pipecat-ai/pipecat-cli) — its commands are available under `pipecat cloud`. Install the Pipecat CLI:
 
-pcc --version
-pcc --help
+```shell
+uv tool install pipecat-ai-cli
+```
 
-# Note: you can use `pcc` or `pipecatcloud` interchangeably
-pcc auth login
+```shell
+pipecat cloud --help
+pipecat cloud auth login
 ```
 
 ! All CLI commands have a `--help` flag that will display the command usage and options.
 
+To use Pipecat Cloud programmatically (without the CLI), install the package directly with `uv add pipecatcloud` and see [Usage in Python scripts](#usage-in-python-scripts).
+
 ## Usage
 
 1. Create an account at [Pipecat Cloud](https://pipecat.daily.co)
 
-2. Login to your account `pcc auth login`
-
-3. (Optional): Clone the quickstart repo [here](https://github.com/pipecat-ai/pipecat-quickstart)
-
-4. Build your agent `docker build --platform linux/arm64 -t your-agent-name .`
+2. Login to your account `pipecat cloud auth login`
 
-5. Push your Docker image to your repository `docker push your-repository/your-agent-name:0.1`
+3. Generate secrets `pipecat cloud secrets set`
 
-6. Deploy your agent `pcc deploy starter-agent your-repository/your-agent-name:0.1`
+4. Build and deploy your agent `pipecat cloud deploy`
 
 ### Usage in Python scripts
 
@@ -78,7 +77,7 @@ if __name__ == "__main__":
 
 ### SSL certificate errors on macOS
 
-If `pcc auth login` fails with an SSL certificate verification error, your Python
+If `pipecat cloud auth login` fails with an SSL certificate verification error, your Python
 installation may not have access to the macOS system certificate store. This is
 common with Python installed via pyenv, conda, or the python.org installer.
 

{pipecatcloud-0.7.1 → pipecatcloud-1.0.0}/pyproject.toml

@@ -19,12 +19,19 @@ dependencies = [
     "typer>=0.20.0,<1",
     "synchronicity>=0.11,<1.0.0",
     "toml~=0.10.2",
-    "questionary~=2.1.0"
+    "questionary~=2.1.0",
 ]
 
 [project.optional-dependencies]
+# The agent session-argument types (pipecatcloud.agent) subclass pipecat-ai's
+# runner argument types. pipecat-ai is optional so the SDK and CLI surface stay
+# lightweight — e.g. so the pipecat-base image doesn't pull pipecat-ai into its
+# layer (the bot provides it). Floor is 1.0.0; `session_id` on the base
+# RunnerArguments came later (v1.2.0) but is supplied by the SessionArguments
+# mixin for pipecat-ai in [1.0.0, 1.2.0).
 pipecat = ["pipecat-ai>=1.0.0"]
 
+
 [dependency-groups]
 dev = [
     "build~=1.4.0",
@@ -36,12 +43,10 @@ dev = [
     "ruff>=0.12.11,<1",
     "setuptools~=78.1.1",
     "setuptools_scm~=8.3.1",
+    # Needed to import/test pipecatcloud.agent (the optional pipecat surface).
+    "pipecat-ai>=1.0.0",
 ]
 
-[project.scripts]
-pcc = "pipecatcloud.__main__:main"
-pipecatcloud = "pipecatcloud.__main__:main"
-
 [project.entry-points."pipecat_cli.extensions"]
 cloud = "pipecatcloud.cli.entry_point:entrypoint_cli_typer"
 

{pipecatcloud-0.7.1 → pipecatcloud-1.0.0}/src/pipecatcloud/__init__.py

@@ -9,13 +9,6 @@ import sys
 
 from loguru import logger
 
-from pipecatcloud.agent import (
-    DailySessionArguments,
-    PipecatSessionArguments,
-    SessionArguments,
-    SmallWebRTCRunnerArguments,
-    WebSocketSessionArguments,
-)
 from pipecatcloud.exception import (
     AgentNotHealthyError,
     AgentStartError,
@@ -32,12 +25,38 @@ logger.remove()
 logger.add(sys.stderr, level=str(os.getenv("PCC_LOG_LEVEL", "INFO")))
 
 
+# The agent session-argument types subclass pipecat-ai's runner argument types,
+# so importing them pulls in pipecat-ai (an optional dependency). Resolve them
+# lazily (PEP 562) so plain `import pipecatcloud` — the SDK and CLI surface — does
+# not require pipecat-ai. Accessing one of these names imports pipecatcloud.agent,
+# which raises a clear ImportError if pipecat-ai is not installed.
+_LAZY_AGENT_EXPORTS = (
+    "DailySessionArguments",
+    "PipecatSessionArguments",
+    "SessionArguments",
+    "SmallWebRTCSessionArguments",
+    "WebSocketSessionArguments",
+)
+
+
+def __getattr__(name: str):
+    if name in _LAZY_AGENT_EXPORTS:
+        from pipecatcloud import agent
+
+        return getattr(agent, name)
+    raise AttributeError(f"module {__name__!r} has no attribute {name!r}")
+
+
+def __dir__():
+    return sorted(list(globals()) + list(_LAZY_AGENT_EXPORTS))
+
+
 __all__ = [
     # Agent classes
     "DailySessionArguments",
     "PipecatSessionArguments",
     "SessionArguments",
-    "SmallWebRTCRunnerArguments",
+    "SmallWebRTCSessionArguments",
     "WebSocketSessionArguments",
     # Session classes
     "Session",

{pipecatcloud-0.7.1 → pipecatcloud-1.0.0}/src/pipecatcloud/_utils/console_utils.py

@@ -13,6 +13,20 @@ from rich.panel import Panel
 from pipecatcloud.cli import PANEL_TITLE_ERROR, PANEL_TITLE_SUCCESS, PIPECAT_CLI_NAME
 
 
+def format_cents(cents: int | None) -> str:
+    """Render a cents value as a USD dollar string (e.g. 1234 -> "$12.34").
+
+    Uses integer arithmetic so the rendered value is exact for any in-range
+    integer, even values float-division would round (e.g. very large cent
+    counts where `cents / 100` loses precision).
+    """
+    if cents is None:
+        return "no limit"
+    sign = "-" if cents < 0 else ""
+    abs_cents = abs(cents)
+    return f"{sign}${abs_cents // 100}.{abs_cents % 100:02d}"
+
+
 class PipecatConsole(Console):
     def success(
         self,
@@ -90,6 +104,11 @@ class PipecatConsole(Console):
             error_message = str(error_code) if error_code else DEFAULT_ERROR_MESSAGE
             code = None
 
+        if code == "SPEND_LIMIT_REACHED":
+            # Safe to pass through: code is only set when error_code is a dict.
+            self._spend_limit_reached(error_code)  # type: ignore[arg-type]
+            return
+
         if not error_message:
             hide_subtitle = True
 
@@ -106,6 +125,48 @@ class PipecatConsole(Console):
             )
         )
 
+    def _spend_limit_reached(self, error: dict):
+        """Render the wrapped remediation message for HTTP 402 SPEND_LIMIT_REACHED.
+
+        Falls back gracefully if the error body omits the spend fields: in that
+        case we render the remediation message without the usage line.
+        """
+        from pipecatcloud.config import config as base_config
+
+        current = error.get("currentSpendCents")
+        limit = error.get("limitCents")
+
+        if current is not None and limit is not None:
+            usage_line = (
+                f"Your organization has reached its spend limit "
+                f"({format_cents(current)} of {format_cents(limit)} used in this billing period)."
+            )
+        else:
+            usage_line = (
+                "Your organization has reached its spend limit for the current billing period."
+            )
+
+        # Fall back to the documented default if the host is unset or empty,
+        # so the rendered link is never `[link=][/link]` or `[link=None]None[/link]`.
+        dashboard = base_config.get("dashboard_host") or "https://pipecat.daily.co"
+        body = (
+            f"{usage_line}\n"
+            "New sessions are being rejected. In-flight sessions continue to run.\n\n"
+            "To unblock new sessions:\n"
+            f"  [bold cyan]{PIPECAT_CLI_NAME} spend-limit set <new amount>[/bold cyan]\n"
+            f"  [bold cyan]{PIPECAT_CLI_NAME} spend-limit clear[/bold cyan]\n\n"
+            f"Or visit [link={dashboard}]{dashboard}[/link]"
+        )
+
+        self.print(
+            Panel(
+                body,
+                title=f"[bold red]{PANEL_TITLE_ERROR} - Spend limit reached (402)[/bold red]",
+                title_align="left",
+                border_style="red",
+            )
+        )
+
 
 console = PipecatConsole()
 

{pipecatcloud-0.7.1 → pipecatcloud-1.0.0}/src/pipecatcloud/_utils/deploy_utils.py

@@ -266,21 +266,8 @@ def interpret_deployment_status(
 class ScalingParams:
     min_agents: int | None = 0
     max_agents: int | None = None
-    # @deprecated
-    min_instances: int | None = field(default=None, metadata={"deprecated": True})
-    # @deprecated
-    max_instances: int | None = field(default=None, metadata={"deprecated": True})
 
     def __attrs_post_init__(self):
-        # Handle deprecated fields
-        if self.min_instances is not None:
-            logger.warning("min_instances is deprecated, use min_agents instead")
-            self.min_agents = self.min_instances
-
-        if self.max_instances is not None:
-            logger.warning("max_instances is deprecated, use max_agents instead")
-            self.max_agents = self.max_instances
-
         # Validation
         if self.min_agents is not None:
             if self.min_agents < 0:
@@ -339,7 +326,6 @@ class DeployConfigParams:
     secret_set: str | None = None
     region: str | None = None
     scaling: ScalingParams = ScalingParams()
-    enable_krisp: bool = False
     docker_config: dict = field(factory=dict)
     build_config: BuildConfig = field(factory=BuildConfig)  # Cloud build configuration
     agent_profile: str | None = None
@@ -366,7 +352,6 @@ class DeployConfigParams:
             "secret_set": self.secret_set,
             "region": self.region,
             "scaling": self.scaling.to_dict() if self.scaling else None,
-            "enable_krisp": self.enable_krisp,
             "docker_config": self.docker_config,
             "build_config": self.build_config.to_dict() if self.build_config else None,
             "agent_profile": self.agent_profile,
@@ -409,16 +394,8 @@ def load_deploy_config_file() -> DeployConfigParams | None:
             exclude_patterns=exclude_data.get("patterns", []),
         )
 
-        # Create DeployConfigParams with validated data
-        validated_config = DeployConfigParams(
-            **config_data,
-            scaling=scaling_params,
-            docker_config=docker_data,
-            build_config=build_config,
-            krisp_viva=krisp_viva_config,
-        )
-
-        # Check for unexpected keys
+        # Check for unexpected keys before constructing the config, so users get a clear
+        # message instead of a raw constructor TypeError.
         expected_keys = {
             "agent_name",
             "image",
@@ -427,7 +404,6 @@ def load_deploy_config_file() -> DeployConfigParams | None:
             "secret_set",
             "region",
             "scaling",
-            "enable_krisp",
             "docker",
             "build",
             "agent_profile",
@@ -435,10 +411,26 @@ def load_deploy_config_file() -> DeployConfigParams | None:
             "websocket_auth",
             "max_session_duration",
         }
+
+        # TODO: Remove this enable_krisp migration hint in the 2.0.0 release.
+        if "enable_krisp" in config_data:
+            raise ConfigFileError(
+                "'enable_krisp' is no longer supported. Krisp is now configured via the "
+                "[krisp_viva] section in pcc-deploy.toml. Remove 'enable_krisp' from your config."
+            )
         unexpected_keys = set(config_data.keys()) - expected_keys
         if unexpected_keys:
             raise ConfigFileError(f"Unexpected keys in config file: {unexpected_keys}")
 
+        # Create DeployConfigParams with validated data
+        validated_config = DeployConfigParams(
+            **config_data,
+            scaling=scaling_params,
+            docker_config=docker_data,
+            build_config=build_config,
+            krisp_viva=krisp_viva_config,
+        )
+
         return validated_config
 
     except Exception as e:

pipecatcloud-1.0.0/src/pipecatcloud/agent.py

@@ -0,0 +1,85 @@
+#
+# Copyright (c) 2025, Daily
+#
+# SPDX-License-Identifier: BSD 2-Clause License
+#
+
+"""Agent session argument types.
+
+These are the argument types passed to a bot's ``bot()`` entry point. Each is a
+thin subclass of the matching pipecat-ai runner argument type
+(``pipecat.runner.types.*RunnerArguments``), so they interoperate with pipecat's
+runner machinery (``create_transport``, ``isinstance`` checks) while giving
+Pipecat Cloud a stable, branded session-argument API.
+
+These types require **pipecat-ai** (>= 1.0.0). pipecat-ai is an optional
+dependency of pipecatcloud (the SDK and CLI do not need it), so a bot environment
+must provide it — install with ``pip install "pipecatcloud[pipecat]"`` or bring
+your own ``pipecat-ai``. Importing this module without pipecat-ai raises a clear
+``ImportError``.
+"""
+
+from dataclasses import dataclass
+
+try:
+    from pipecat.runner.types import (
+        DailyRunnerArguments,
+        RunnerArguments,
+        SmallWebRTCRunnerArguments,
+        WebSocketRunnerArguments,
+    )
+except ImportError as e:  # pragma: no cover - exercised only without pipecat-ai
+    raise ImportError(
+        "pipecatcloud's agent session-argument types require pipecat-ai>=1.0.0. "
+        'Install it with `pip install "pipecatcloud[pipecat]"`, or add pipecat-ai '
+        "to your environment."
+    ) from e
+
+
+@dataclass
+class SessionArguments:
+    """Base class / marker for Pipecat Cloud agent session arguments.
+
+    The arguments are received by the bot() entry point.
+
+    Parameters:
+        session_id (str | None): The unique identifier for the session, used to
+            track it across requests.
+    """
+
+    # ``session_id`` is intentionally declared here as a compatibility shim:
+    # pipecat-ai only added ``session_id`` to the base ``RunnerArguments`` in
+    # v1.2.0. For pipecat-ai in the [1.0.0, 1.2.0) range, this mixin supplies
+    # ``session_id``. When pipecat-ai *does* define it on the base, that field
+    # overrides this one because ``RunnerArguments`` appears later than
+    # ``SessionArguments`` in the MRO of the subclasses below. That is why every
+    # subclass must list the ``*RunnerArguments`` base FIRST — e.g.
+    # ``(DailyRunnerArguments, SessionArguments)``. Do not reorder the bases.
+    # (No default here on purpose: giving it one would order a defaulted field
+    # before ``room_url`` on older pipecat-ai and raise "non-default argument
+    # follows default argument".)
+    session_id: str | None
+
+
+@dataclass
+class PipecatSessionArguments(RunnerArguments, SessionArguments):
+    """Standard Pipecat Cloud agent session arguments (no specific transport).
+
+    Used for HTTP activations that did not request a Daily room — for example the
+    room-less SmallWebRTC flow, where the WebRTC connection arrives separately.
+    """
+
+
+@dataclass
+class DailySessionArguments(DailyRunnerArguments, SessionArguments):
+    """Daily-based agent session arguments."""
+
+
+@dataclass
+class WebSocketSessionArguments(WebSocketRunnerArguments, SessionArguments):
+    """WebSocket-based agent session arguments."""
+
+
+@dataclass
+class SmallWebRTCSessionArguments(SmallWebRTCRunnerArguments, SessionArguments):
+    """SmallWebRTCTransport-based agent session arguments."""