watchdog-agent-sdk 0.1.0__tar.gz

watchdog_agent_sdk-0.1.0/ADAPTER_VERIFICATION.md

@@ -0,0 +1,66 @@
+# OpenAI Agents adapter verification
+
+The adapter uses the lifecycle contract below. Signatures include `self` and a
+trailing `**kwargs` in the Watchdog implementation for forward-compatible keyword
+extensions. Inputs are accepted only to match the framework contract and are not
+serialized.
+
+```python
+async def on_agent_start(self, context, agent): ...
+async def on_agent_end(self, context, agent, output): ...
+async def on_handoff(self, context, from_agent, to_agent): ...
+async def on_llm_start(self, context, agent, system_prompt, input_items): ...
+async def on_llm_end(self, context, agent, response): ...
+async def on_tool_start(self, context, agent, tool): ...
+async def on_tool_end(self, context, agent, tool, result): ...
+```
+
+The adapter reads `response.usage.input_tokens` and
+`response.usage.output_tokens`. It does not read response output or cumulative
+run-context usage. For function calls it reads tool names, local argument
+fingerprints, and elapsed monotonic time. If exposed by the framework,
+`context.tool_call_id` is used only for local timing correlation and
+`context.tool_arguments` is HMACed locally.
+
+Sources inspected on September 5, 2026:
+
+- [Official Agents SDK overview](https://developers.openai.com/api/docs/guides/agents)
+- [Official running agents guide](https://developers.openai.com/api/docs/guides/agents/running-agents)
+- [Official integrations and observability guide](https://developers.openai.com/api/docs/guides/agents/integrations-observability)
+
+The official `openai-agents` 0.8.4 distribution was downloaded and its source
+inspected. Wheel SHA-256:
+`2383c6e8e59ed4146b89d1b6f53e34e55caf94bc14ae3fd704e7aad5021f4ff1`.
+
+The optional dependency pins `openai-agents==0.8.4` and `openai==2.19.0` as a
+compatible baseline. Resolving the upstream Agents dependency without this pin
+installed `openai==2.54.0`, whose required `cache_write_tokens` usage field breaks
+the Agents 0.8.4 default `Usage()` constructor before lifecycle hooks run. The
+adapter does not monkeypatch upstream models or hide this compatibility failure.
+
+Verified directly in the distribution:
+
+- `agents/lifecycle.py`: all seven signatures above match. `RunHooks` is an alias
+  for `RunHooksBase[TContext, Agent]`.
+- `agents/run_internal/tool_execution.py`: function-tool hooks receive the
+  `ToolContext`, including the call ID and arguments used by this adapter.
+- `agents/tool_context.py`: `tool_call_id` and `tool_arguments` are required
+  context fields. The adapter only hashes arguments locally.
+- `agents/run_internal/run_loop.py`: per-response usage is added to the cumulative
+  context before the end hook. Reading `response.usage` avoids double counting.
+- `agents/run_internal/tool_actions.py`: some local action tools receive a plain
+  run context, so per-call ID/argument fidelity is not universally available.
+
+Four tests in `tests/test_real_openai.py` passed against the actual installed
+Runner using a deterministic local Model. They verify exact installed signatures,
+parallel tool calls with distinct private fingerprints, correct per-response token
+counts, preserved Runner exceptions, and cooperative cancellation. The tested
+environment used Python 3.12, `openai-agents==0.8.4`, `openai==2.19.0`, and
+`pydantic==2.13.5`. No live model request was made.
+
+Run the complete SDK and control-adapter suite after installing the optional
+extra: `python -m unittest discover -s tests -v`. Without the optional dependency,
+the four real Runner tests are explicitly skipped. The rest of the suite covers
+fail-open delivery, privacy, idempotency, and signed control dispatch.
+
+Final integration validation: all 39 tests passed, including the real loopback signed HTTP server test and four real OpenAI Runner tests.

watchdog_agent_sdk-0.1.0/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

watchdog_agent_sdk-0.1.0/MANIFEST.in

@@ -0,0 +1,7 @@
+include README.md LICENSE ADAPTER_VERIFICATION.md
+recursive-include examples *.py *.md
+recursive-include tests *.py
+global-exclude *.py[cod]
+global-exclude .DS_Store
+prune .git
+prune .venv

watchdog_agent_sdk-0.1.0/PKG-INFO

@@ -0,0 +1,263 @@
+Metadata-Version: 2.4
+Name: watchdog-agent-sdk
+Version: 0.1.0
+Summary: Fail-open reliability monitoring for unattended agent jobs
+Author: Watchdog Limited
+License-Expression: Apache-2.0
+Project-URL: Homepage, https://withwatchdog.com
+Project-URL: Documentation, https://withwatchdog.com/docs/quickstart
+Project-URL: Repository, https://github.com/withwatchdog/watchdog-sdk
+Project-URL: Issues, https://github.com/withwatchdog/watchdog-sdk/issues
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3 :: Only
+Classifier: Operating System :: OS Independent
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Provides-Extra: openai
+Requires-Dist: openai-agents==0.8.4; extra == "openai"
+Requires-Dist: openai==2.19.0; extra == "openai"
+Dynamic: license-file
+
+# Watchdog Python SDK
+
+Track the completion, progress, cost, tool activity, and expected outcomes of an
+unattended job. The SDK sends metadata to the Watchdog API from a bounded background
+queue. Monitoring outages do not raise exceptions into application code.
+
+## Install and configure
+
+```bash
+python -m pip install watchdog-agent-sdk
+export WATCHDOG_URL="https://withwatchdog.com"
+export WATCHDOG_API_KEY="your-ingest-key"
+```
+
+The distribution is `watchdog-agent-sdk`; its import is `watchdog_agent`. This
+avoids colliding with the unrelated Python filesystem package named `watchdog`.
+The base SDK has no runtime dependencies and supports Python 3.10 or newer.
+
+For local development, clone this repository and run `python -m pip install .`
+from its root. Self-hosted installations can set `WATCHDOG_URL` to their API origin.
+
+Register an agent and a job in the dashboard, then use the job ID or slug:
+
+```python
+from watchdog_agent import Watchdog
+
+with Watchdog() as watchdog:
+    with watchdog.run("daily-report", cancellable=True) as run:
+        with run.tool_call("competitors.search", arguments={"sector": "software"}):
+            results = search_competitors()
+        run.progress("Research complete", completed=len(results))
+
+        report = create_report(results)
+        run.outcome("report_created", metadata={"record_id": report.id})
+
+        run.check_cancelled()
+        post_report(report)
+        run.outcome("report_posted")
+```
+
+`run.started` is emitted on entry. Normal exit emits `run.completed`; an exception
+emits `run.failed` and preserves the original exception. Cancellation emits
+`run.cancelled`. Exceptions' type names are collected; their messages, stack
+traces, and local variables are not collected. Completion means the agent exited;
+the server evaluates whether the required business outcomes were satisfied.
+
+Only explicit `run.progress()` calls indicate meaningful progress. Tool calls,
+model calls, handoffs, and repeated activity do not reset the progress timer.
+
+## Usage, costs, and outcomes
+
+```python
+run.usage(
+    model="your-model-name",
+    input_tokens=2100,
+    output_tokens=300,
+    cost_usd=0.017,
+)
+run.tool("crm.update", duration_ms=180, status="success", arguments={"id": record_id})
+run.outcome("crm_updated", success=True, metadata={"record_id": record_id})
+```
+
+Each usage event is a **delta for one model request**, not the cumulative run
+usage. Omit `cost_usd` when it is unknown. The SDK does not embed a stale model
+price table. This version only sums explicitly reported costs; token counts alone do not calculate spending.
+Report an outcome only after the corresponding application operation succeeds.
+An emitted outcome is an application attestation, not independent verification.
+
+Tool fingerprints use a per-run random HMAC key over canonical tool name,
+arguments, and status. Raw arguments stay in the customer process. Reordered
+JSON keys and insignificant JSON whitespace produce the same fingerprint;
+different arguments normally produce different fingerprints. Without arguments,
+only tool names/status distinguish calls. Emit explicit progress within legitimate
+bulk-processing loops to avoid treating repeated work as a lack of progress.
+
+## Async jobs and cancellation
+
+```python
+async with Watchdog() as watchdog:
+    async with watchdog.run("daily-report", cancellable=True) as run:
+        await execute_agent()
+        run.outcome("report_created")
+```
+
+For a cancellable async context, an authenticated cancel command schedules
+`Task.cancel()` on the task owning that context. It takes effect at an await
+boundary. Application code must allow `asyncio.CancelledError` to propagate.
+For synchronous code, call `run.check_cancelled()` between work units.
+`run.tool_call()` checks automatically before entering a tool. Blocking external
+operations cannot be forcefully stopped by this SDK.
+
+The SDK acknowledges a cancel action only after the run exits cancelled. A
+received command is not proof that execution has stopped. If the application
+completes without observing cancellation, the action is acknowledged as failed.
+Retry commands require a customer runtime webhook/controller; this client does
+not retain business input or execute customer code again.
+
+The included [signed control adapter](https://github.com/withwatchdog/watchdog-sdk/blob/main/examples/CONTROL_ADAPTER.md) implements a
+customer-owned callback endpoint with cancellation, retry, fallback allowlisting,
+missed-slot correlation, HMAC verification, and a durable action ledger. Its local
+demo executes a supplied application function and writes report files.
+
+Cancellation is out of band. Polling, network latency, in-flight tool requests,
+and model requests can cause delay or budget overshoot. This is not a hard
+real-time spend ceiling.
+
+## OpenAI Agents adapter
+
+```bash
+python -m pip install 'watchdog-agent-sdk[openai]'
+```
+
+The optional extra pins the verified combination `openai-agents==0.8.4` and
+`openai==2.19.0`. Run the integration suite when upgrading either dependency;
+the upstream Agents version's broad dependency range also permits a newer,
+incompatible usage schema. Details are in
+[ADAPTER_VERIFICATION.md](https://github.com/withwatchdog/watchdog-sdk/blob/main/ADAPTER_VERIFICATION.md).
+
+```python
+from agents import Runner, RunConfig
+from watchdog_agent.openai_agents import WatchdogHooks
+
+async with watchdog.run("daily-report", cancellable=True) as run:
+    result = await Runner.run(
+        agent,
+        business_input,
+        hooks=WatchdogHooks(run),
+        run_config=RunConfig(trace_include_sensitive_data=False),
+    )
+    # Save the result in your application before recording the outcome.
+    saved = await save_report(result.final_output)
+    run.outcome("report_created", metadata={"record_id": saved.id})
+```
+
+Use one hook instance per Watchdog run. The outer context owns job completion,
+so handoffs and nested-agent completion cannot finish it prematurely. Per-response
+token usage is used; cumulative `context.usage` would double-count earlier calls.
+OpenAI's own tracing is separate from Watchdog telemetry: disabling sensitive
+data there does not change application-provided Watchdog messages or metadata.
+
+Adapter coverage and limitations:
+
+- Lifecycle hooks capture function-tool completions and per-model response usage.
+- Hosted provider tools may not pass through function-tool hooks; supply explicit
+  instrumentation when that activity needs to count toward a tool-call policy.
+- Tool exceptions converted by a framework into result strings cannot be
+  classified safely without examining sensitive output. Use `run.tool_call()`
+  inside a custom tool, or emit explicit error status for accurate error storms.
+  Avoid also counting the same completed tool through the adapter.
+- Call IDs distinguish concurrent tool calls where the framework exposes them.
+  Older contexts without call IDs use a FIFO fallback; durations may be
+  approximate for parallel calls of the same tool.
+- Hook-generated events do not imply business outcomes or semantic progress.
+
+The official [Agents SDK guide](https://developers.openai.com/api/docs/guides/agents)
+and [running agents guide](https://developers.openai.com/api/docs/guides/agents/running-agents)
+describe the SDK execution model. See `ADAPTER_VERIFICATION.md` for the exact
+compatibility evidence and remaining limitations.
+
+## Delivery and privacy behavior
+
+- The default queue holds 1,024 requests; enqueue never waits for network I/O.
+  Full queues drop new telemetry and increment `watchdog.stats["dropped"]`.
+- Events have unique IDs and per-run monotonic sequences. Retries preserve the
+  original serialized event, timestamp, sequence, and ID for server deduplication.
+- Transient failures receive two retries by default. HTTP 4xx other than 408/429
+  are not retried. No prompts, outputs, payloads, or bearer keys are logged.
+- Use the client as a context manager or call `watchdog.close(timeout=2)` before
+  a short-lived process exits. `flush()` and `close()` return `False` if their
+  bounded wait expires. Daemon threads cannot guarantee delivery after a crash
+  or process kill. There is no durable disk spool in this version.
+- Missing `WATCHDOG_API_KEY` disables delivery. Inspect `.enabled` and `.stats`
+  during installation checks. Configuration errors, such as insecure remote URLs,
+  raise immediately; network failures do not interrupt an otherwise valid job.
+- Metadata accepts bounded JSON values and removes common secret-bearing keys.
+  Application-provided messages, names, and metadata values are intentionally
+  transmitted: do not place secrets in them. Secret-key filtering is defense in
+  depth, not a content classifier.
+- HTTPS is required except for loopback development. Redirects are rejected so
+  bearer credentials are not forwarded to another host.
+- Customer-supplied `headers={...}` can support additional deployment access
+  layers. Authentication and request-framing headers cannot be overridden.
+
+Create the client **after forking** a worker process. A client owns live threads
+and is not process-safe. Reuse one client across jobs within each process.
+
+## Wire protocol
+
+`POST /api/v1/events` accepts a single JSON event with bearer authentication:
+
+```json
+{
+  "event_id": "evt_a_unique_id",
+  "run_id": "run_a_unique_id",
+  "job_id": "daily-report",
+  "type": "tool.completed",
+  "sequence": 3,
+  "timestamp": "2026-09-05T12:00:00.000Z",
+  "data": {
+    "name": "crm.update",
+    "fingerprint": "a-per-run-hmac",
+    "duration_ms": 180,
+    "status": "success",
+    "metadata": {}
+  }
+}
+```
+
+Types: `run.started`, `progress`, `tool.completed`, `llm.completed`, `outcome`,
+`run.completed`, `run.failed`, `run.cancelled`.
+
+`GET /api/v1/runs/{run_id}/commands` returns
+`{"commands":[{"id":"action-id","type":"cancel"}]}`.
+The SDK sends `POST /api/v1/actions/{action_id}/ack` with
+`{"status":"acknowledged","message":"Runtime stopped cooperatively"}`
+after cancellation takes effect, or `status: "failed"` when it cannot be applied.
+
+## Tests
+
+```bash
+python -m pip install '.[openai]'
+python -m unittest discover -s tests -v
+```
+
+Run these commands from the cloned repository root. Tests cover outages,
+queue saturation, bounded shutdown, retry idempotency,
+privacy, concurrent event sequences, sync/async cancellation acknowledgments,
+tool failures, outcomes, and hook mapping without requiring a model API key.
+
+## Start with lifecycle-only monitoring
+
+New Watchdog jobs leave progress monitoring disabled (`progress_timeout: 0`) and have no expected schedule unless you add one. Set a realistic maximum runtime, for example 1,200 seconds for a legitimate 15-minute job. The run context reports start, completion and failure; it cannot report a process kill. A missing completion is detected when the runtime deadline expires.
+
+Add `run.progress()` after meaningful completed work, then explicitly enable a milestone timeout in the job's Additional checks. The timer starts at run start. Tool calls do not reset it, and emitting progress does not turn the timeout on. Progress can still reset the tool-loop window while milestone timeout monitoring is off. Existing jobs retain their saved policies; edits apply to future runs.
+
+Install without repository access:
+
+```sh
+python -m pip install watchdog-agent-sdk==0.1.0
+```
+
+Use `watchdog-agent-sdk`, not the unrelated `watchdog` filesystem package.