Skip to main content

flightdeck-sensor

In-process agent observability sensor for Flightdeck.

Local development venv

Flightdeck pins Python 3.12 for local development. The sensor supports 3.11 ≤ x < 3.15 (pyproject requires-python); sensor/.venv is the canonical interpreter for every Make target that runs Python.

Recreate from a fresh clone or after a rm -rf sensor/.venv:

python3.12 -m venv sensor/.venv
./sensor/.venv/bin/python -m pip install -e ".[dev,anthropic,openai]"

make -C sensor install does the same once the venv exists. To get the exact versions CI tests with, install from the lockfile instead:

cd sensor && uv sync --locked --python 3.12 --extra dev --extra anthropic --extra openai

CI installs from sensor/uv.lock into the actions/setup-python interpreter and overrides via env (PYTHON=python make -C sensor test). The lock covers Python 3.11 to 3.14 and both CI lanes: the framework lane (dev extra) and the newest-SDK lane (sdk-majors dependency group). uv lock resolves only releases at least 14 days old, anthropic a day old ([tool.uv] in pyproject.toml).

Optional session_id hint

By default init() auto-generates a fresh UUID every time the process starts. Orchestrators that re-run the same logical workflow (Temporal, Airflow, cron) can instead pass a stable identifier; if the backend already has a row for that session, the new execution is attached to it and appears as a continuation of the prior run in the fleet view.

Supply the hint via either the session_id= kwarg or the FLIGHTDECK_SESSION_ID environment variable. The env var takes precedence.

The value MUST parse as a canonical UUID (any version) -- the sessions table column is UUID-typed. If you pass a non-UUID the sensor logs a warning and falls back to auto-generating one. Orchestrators that use string identifiers (Temporal workflow_id, Airflow dag_run_id) should hash the identifier into a deterministic UUID with uuid.uuid5.

Temporal workflow example

import uuid
import flightdeck_sensor as fd
from temporalio import workflow

# Pick any fixed namespace UUID for your deployment. The same
# workflow_id + namespace always produces the same session UUID,
# so re-runs of the same workflow all map to the same sessions row.
FLIGHTDECK_NS = uuid.UUID("00000000-0000-0000-0000-000000000001")


@workflow.defn
class MyWorkflow:
    @workflow.run
    async def run(self, input):
        ctx = workflow.info()
        fd.init(
            server="http://flightdeck.internal/ingest",
            token="ftd_...",
            session_id=str(uuid.uuid5(FLIGHTDECK_NS, ctx.workflow_id)),
        )
        # If this workflow_id has run before, the backend attaches
        # this execution to the existing session automatically; the
        # sensor logs INFO on the first response that confirms it.
        ...

The sensor logs a single WARNING at init() time whenever a custom session_id is in play so the behaviour is visible in operational logs, and an INFO line on the first response where the backend confirms attachment. See ARCHITECTURE.md ("Session attachment flow") for the full protocol.

Framework support

flightdeck_sensor.patch() installs six interceptors process-wide: three LLM-call interceptors (class-level or module-level), one MCP interceptor, and two sub-agent interceptors. Every LLM call that flows through a patched entry point emits a pre_call / post_call event pair without any framework-specific wiring; the MCP and sub-agent interceptors emit their own event types, described in the table.

Framework Interceptor Entry points
Anthropic SDK — every client class (Anthropic, AnthropicBedrock, AnthropicVertex, AnthropicFoundry, AnthropicAWS, AnthropicBedrockMantle, AnthropicGoogleCloud and their async forms), direct or via a framework that constructs one internally (LangChain, LlamaIndex, CrewAI native) patch_anthropic_classes messages.create (including stream=True), .stream, .parse, async + sync, beta resources, the raw view (with_raw_response) and the streaming view (with_streaming_response, metered at parse()); streamed calls are metered from the in-stream usage events; every post_call carries provider_metadata.platform (anthropic, bedrock, bedrock-mantle, aws, vertex, google-cloud, foundry, or a gateway's host)
OpenAI SDK (direct or via a framework that constructs OpenAI() internally — LangChain, LlamaIndex, CrewAI native) patch_openai_classes OpenAI.chat.completions.create / .parse, .responses.create / .parse, and their with_raw_response counterparts (create / parse), .embeddings.create, async + sync; create(stream=True) on chat and Responses is metered from the chat usage chunk and response.completed; the .stream() helpers and with_streaming_response are not intercepted
litellm (router that aggregates many providers behind one function surface) patch_litellm_functions litellm.completion, litellm.acompletion, litellm.embedding, litellm.aembedding
MCP (official Python mcp SDK, reached transitively by langchain-mcp-adapters, llama-index-tools-mcp and mcpadapt) patch_mcp_classes mcp.client.session.ClientSession.initialize on mcp 1.x / .adopt on mcp 2.x (server fingerprint capture, every 2.x handshake path), .list_tools, .call_tool, .list_resources, .read_resource, .list_prompts, .get_prompt (one mcp_* event type each), plus the stdio / SSE / streamable-HTTP / websocket transport client factories and mcp 2.x's Client._build_session for transport attribution. call_tool also enforces the MCP Protection Policy. Supported SDK range: mcp>=1.20,<3.
CrewAI (sub-agent sessions) patch_crewai_classes crewai.Agent.execute_task / .aexecute_task — each Crew member's turn lands as a child session (session_start / session_end) with parent_session_id, agent_role taken from Agent.role, and incoming / outgoing message capture gated on capture_prompts
LangGraph (sub-agent sessions) patch_langgraph_classes langgraph.graph.StateGraph.add_node — the registered node callable is wrapped so each node run lands as a child session with agent_role taken from the node name; every node is treated as agent-bearing unless narrowed with init(langgraph_agent_node_pattern=...)

litellm example

litellm's Anthropic route uses raw httpx instead of the Anthropic SDK, so it bypasses the SDK-class patches. The litellm interceptor patches litellm.completion / litellm.acompletion directly to close this gap. An Anthropic model string via litellm exercises the bypass case:

import flightdeck_sensor
import litellm

flightdeck_sensor.init(
    server="http://flightdeck.internal/ingest",
    token="ftd_...",
)
flightdeck_sensor.patch()

# After patch(), this call routes through the sensor's pre/post-call
# plumbing regardless of which underlying provider litellm picks for
# the model string.
response = litellm.completion(
    model="claude-haiku-4-5-20251001",
    messages=[{"role": "user", "content": "hi"}],
    max_tokens=5,
)

Install the optional dependency: pip install flightdeck-sensor[litellm] (the extra requires litellm>=1.83.0; 1.82.7 and 1.82.8 were compromised builds).

What the litellm interceptor catches, and what it doesn't

Catches. Direct callers of litellm.completion(**kwargs) and litellm.acompletion(**kwargs) — the vast majority of litellm integrations, including the default chat-completion surface exposed by user code, Router, and frameworks that route through the public API (CrewAI non-native flavors, langchain-community's litellm adapter, etc.) — streaming included: stream=True on either returns the sensor's stream guard around litellm's CustomStreamWrapper, iterated the same way (for / async for), metered from the token counts litellm reports in its trailing usage chunk; that chunk is kept from a caller who did not ask for stream_options.include_usage. A call litellm serves through the OpenAI SDK (which the sensor also patches) is counted once, by the litellm wrapper. Embedding calls through litellm.embedding(**kwargs) and litellm.aembedding(**kwargs) are wrapped the same way, so embedding-model token usage lands too (12_litellm.py in the playground exercises sync and async streaming, the single-count assertion and the capture round-trip).

Does NOT catch.

  • Lower-level litellm entry points. Some integrations reach past completion into litellm.llms.custom_httpx.http_handler or other internal helpers directly. Those calls bypass the module-level wrapper. A broader httpx-level interceptor was considered when the litellm interceptor was scoped and deferred — if framework reports surface calls that slip past the current coverage, file a new issue.
  • litellm.text_completion / atext_completion and litellm.responses / aresponses. Neither is wrapped (root README.md Roadmap), but some routes are still reported. The legacy completion API calls completion through the name bound in litellm.main, which the module-attribute swap does not reach; on an OpenAI chat model the OpenAI interceptor reports the SDK call it makes, and litellm's own httpx routes are unobserved. The Responses API on a provider without a native Responses API (for example Anthropic) is bridged through the patched litellm.completion and reported once as a chat call; native routes (OpenAI) go through litellm's own httpx handler and are unobserved.
  • SDK calls made from inside a litellm call. The litellm wrapper marks the call it serves so the SDK interceptors pass it through; the mark covers the whole call, so an SDK call made while it is in flight by a litellm callback, guardrail or custom provider, or by a task created inside the call, is neither policed nor metered.

Metadata

Release files for flightdeck-sensor 0.7.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for flightdeck-sensor 0.7.0
File Size Uploaded Provenance Actions
flightdeck_sensor-0.7.0.tar.gz 698.4 kB With provenance Details for flightdeck_sensor-0.7.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for flightdeck-sensor 0.7.0
File Interpreter ABI Platform Actions
flightdeck_sensor-0.7.0-py3-none-any.whl Python 3 none any Details for flightdeck_sensor-0.7.0-py3-none-any.whl

Total release size: 895.1 kB

Release files / flightdeck_sensor-0.7.0.tar.gz

Download URL flightdeck_sensor-0.7.0.tar.gz
Size 698.4 kB
Tags Source
SHA-256 checksum
How to use checksums
7e750b8699a71f412ea9c5628d3d8314c8046bbe1d9acaae4a9d2ae3a58ca4bd
BLAKE2b-256 checksum
How to use checksums
5a4e6e5186381e08f4a0485bf1730f7456c0fca9795d2f2455f80fa9cab65700
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 26, 2026.

Transparency log

Release files / flightdeck_sensor-0.7.0-py3-none-any.whl

Download URL flightdeck_sensor-0.7.0-py3-none-any.whl
Size 196.7 kB
Tags Python 3
SHA-256 checksum
How to use checksums
110c1364073831b08d87045f3154133dd1b85306a8fc812b7b62c04c0190c615
BLAKE2b-256 checksum
How to use checksums
d8b75b9e47155b62c0fd678fbde4077c382450614e75d1890e09861309b7fd96
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 26, 2026.

Transparency log

Security for flightdeck-sensor 0.7.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

Both files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for flightdeck_sensor-0.7.0.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 26, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page