Gap
docs/api-reference/configuration.mdx documents PMXT_LOG_LEVEL as controlling "Log verbosity for SDK + local server: debug, info, warn, error." It's implemented in core's local-server logger and in the TypeScript SDK's own logger, but the Python SDK has no logger module and never reads this variable at all.
Core
core/src/utils/logger.ts:21 — let currentLevel: LogLevel = (process.env.PMXT_LOG_LEVEL as LogLevel) || 'info'; (honored by the self-hosted local server).
TypeScript SDK
Implemented — sdks/typescript/pmxt/logger.ts:22-25 reads process.env.PMXT_LOG_LEVEL and gates console.debug/info/warn/error calls by threshold; also read directly in sdks/typescript/pmxt/server-manager.ts:211.
Python SDK
Missing — grep -rn "PMXT_LOG_LEVEL\|LOG_LEVEL" sdks/python/pmxt/*.py returns zero matches. There is no logger module, no level-threshold concept, and no read of PMXT_LOG_LEVEL anywhere in the Python SDK.
Evidence
Confirmed via direct grep: sdks/typescript/pmxt/logger.ts:7,22-23 and core/src/utils/logger.ts:21 both reference PMXT_LOG_LEVEL; docs/api-reference/configuration.mdx:97 documents it as applying to "SDK + local server" (not TypeScript-SDK-specific); no match anywhere in sdks/python/pmxt/.
Impact
Python users who follow the documented configuration table and set PMXT_LOG_LEVEL to control SDK verbosity get no effect whatsoever — a silent no-op that's asymmetric with the TypeScript SDK's actual behavior and contradicts the doc's "SDK + local server" framing.
Found by automated Core-to-SDK surface coverage audit
Gap
docs/api-reference/configuration.mdxdocumentsPMXT_LOG_LEVELas controlling "Log verbosity for SDK + local server: debug, info, warn, error." It's implemented in core's local-server logger and in the TypeScript SDK's own logger, but the Python SDK has no logger module and never reads this variable at all.Core
core/src/utils/logger.ts:21—let currentLevel: LogLevel = (process.env.PMXT_LOG_LEVEL as LogLevel) || 'info';(honored by the self-hosted local server).TypeScript SDK
Implemented —
sdks/typescript/pmxt/logger.ts:22-25readsprocess.env.PMXT_LOG_LEVELand gatesconsole.debug/info/warn/errorcalls by threshold; also read directly insdks/typescript/pmxt/server-manager.ts:211.Python SDK
Missing —
grep -rn "PMXT_LOG_LEVEL\|LOG_LEVEL" sdks/python/pmxt/*.pyreturns zero matches. There is no logger module, no level-threshold concept, and no read ofPMXT_LOG_LEVELanywhere in the Python SDK.Evidence
Confirmed via direct grep:
sdks/typescript/pmxt/logger.ts:7,22-23andcore/src/utils/logger.ts:21both referencePMXT_LOG_LEVEL;docs/api-reference/configuration.mdx:97documents it as applying to "SDK + local server" (not TypeScript-SDK-specific); no match anywhere insdks/python/pmxt/.Impact
Python users who follow the documented configuration table and set
PMXT_LOG_LEVELto control SDK verbosity get no effect whatsoever — a silent no-op that's asymmetric with the TypeScript SDK's actual behavior and contradicts the doc's "SDK + local server" framing.Found by automated Core-to-SDK surface coverage audit