Marketingclaw Debugging

MarketingClaw Debugging

Use this skill when MarketingClaw behavior differs between local tests, live models, providers, code mode, Tool Search, Crabbox, or CI, and the next move should be a debug signal rather than a guess.

Read First

• docs/logging.md for log files, marketingclaw logs, and targeted debug flags.
• docs/reference/test.md for local test commands.
• docs/reference/code-mode.md for code-mode exec/wait and tool catalog rules.
• Use $marketingclaw-testing for choosing test lanes.
• Use $crabbox for broad, Docker, package, Linux, live-key, or CI-parity proof.

Default Loop

1. State the suspected boundary: config, tool construction, provider payload, fetch, stream/SSE, transcript replay, worker/runtime, package/dist, or CI.
2. Add or enable the narrowest signal that proves that boundary.
3. Reproduce with the same provider/model/config. Do not randomly switch models unless the model itself is the variable being tested.
4. Compare configured state with actual run activation.
5. Patch the root cause.
6. Rerun the exact failing probe, then broaden only if the contract requires it.

Model Transport Logs

Use targeted env flags instead of global debug when the model request shape or stream timing matters:

MARKETINGCLAW_DEBUG_MODEL_TRANSPORT=1 marketingclaw gateway
MARKETINGCLAW_DEBUG_MODEL_PAYLOAD=tools MARKETINGCLAW_DEBUG_SSE=events marketingclaw gateway
MARKETINGCLAW_DEBUG_MODEL_PAYLOAD=full-redacted MARKETINGCLAW_DEBUG_SSE=peek marketingclaw gateway

Useful flags:

• MARKETINGCLAW_DEBUG_MODEL_TRANSPORT=1: request start, fetch response, SDK headers, first SSE event, stream done, and transport errors at info.
• MARKETINGCLAW_DEBUG_MODEL_PAYLOAD=summary: bounded payload summary.
• MARKETINGCLAW_DEBUG_MODEL_PAYLOAD=tools: all model-facing tool names.
• MARKETINGCLAW_DEBUG_MODEL_PAYLOAD=full-redacted: capped, redacted JSON payload. Use only while debugging; prompts/message text may still appear.
• MARKETINGCLAW_DEBUG_SSE=events: first-event and stream-completion timing.
• MARKETINGCLAW_DEBUG_SSE=peek: first five redacted SSE events.
• MARKETINGCLAW_DEBUG_CODE_MODE=1: code-mode tool-surface diagnostics.

Watch logs with:

marketingclaw logs --follow

Common Boundaries

• Config vs activation: config can be enabled while the run disables tools, is raw, has an empty allowlist, or lacks model tool support. Check the actual visible tools before enforcing provider payload invariants.
• Tool surface: inspect final model-visible tool names, not only the tool registry or config. Code mode means exactly exec and wait only after it actually activates.
• Provider payload: log fields, model id, service tier, reasoning, input size, metadata keys, prompt-cache key presence, and tool names before SDK call.
• Fetch vs SSE: fetch response proves HTTP headers arrived; first SSE event proves provider body progress. A gap here is a stream/body/provider issue, not tool execution.
• Worker/dist: run pnpm build when touching workers, dynamic imports, package exports, lazy runtime boundaries, or published paths.
• Live keys: use the configured secret workflow for missing provider keys before saying live proof is blocked. Env checks are presence-only; never print secrets.

Code Pointers

• Model payload + Responses stream: src/agents/openai-transport-stream.ts
• Guarded fetch/timing: src/agents/provider-transport-fetch.ts
• OpenAI/Codex provider wrappers: src/agents/pi-embedded-runner/openai-stream-wrappers.ts
• Tool construction, Tool Search, code-mode activation: src/agents/pi-embedded-runner/run/attempt.ts
• Code-mode runtime and worker: src/agents/code-mode.ts src/agents/code-mode.worker.ts
• Tool Search catalog: src/agents/tool-search.ts

Proof Choice

• Single helper/payload bug: local targeted Vitest.
• Docs/logging-only: pnpm check:docs and git diff --check.
• Worker/dist/lazy import/package surface: targeted tests plus pnpm build.
• Live provider/model behavior: same provider/model with debug flags and a real key if available.
• Docker/package/Linux/CI-parity: $crabbox.
• CI failure: exact SHA, relevant job only, logs only after failure/completion.

Output Habit

Report:

• boundary tested
• exact command/env shape, redacted
• observed signal, such as tool names or first SSE event timing
• fix location
• narrow proof and any remaining risk