Summary

When asking an agent to inspect the codebase with codedb, bundled codedb_outline calls sometimes return repeated missing path argument errors even though the agent intended to request outlines for specific files.

This looks like a reliability issue in the bundled-tool path rather than a normal user-facing validation error.

Observed behavior

A codebase exploration flow used a bundled request for multiple codedb_outline operations. The response contained repeated errors like:

--- [0] codedb_outline ---
error: missing path argument
--- [1] codedb_outline ---
error: missing path argument
--- [2] codedb_outline ---
error: missing path argument

The same pattern appeared more than once during the session.

Why this matters

This may explain some of the aggregate outline/query reliability signal. Agents commonly batch outlines after reading a tree, so if nested arguments are dropped or malformed in the bundle path, the agent sees a high-noise failure and has to retry with individual calls.

That hurts the planned Agent Context Planner direction because it depends on composing search, outline, read, symbol, and dependency steps reliably.

Expected behavior

One of these should happen:

• bundled codedb_outline calls preserve and receive their nested path argument correctly, or
• if a bundled operation is malformed, the error identifies the failing bundle item and includes machine-readable diagnostics showing the received argument object, with sensitive values redacted if needed.

Things to check

• Argument parsing for codedb_bundle operations.
• Whether the MCP schema names for nested calls match the handler expectation.
• Whether path is being dropped when an operation is marshalled through the bundle wrapper.
• Whether missing required arguments inside a bundle should return partial results for the rest of the bundle instead of repeated opaque errors.
• Tests for a bundle containing multiple valid codedb_outline calls.
• Tests for a mixed valid/invalid bundle, ensuring valid operations still run and invalid operations get actionable errors.

Privacy note

This issue intentionally avoids raw project paths, raw request payloads, user identifiers, credentials, and exact telemetry counts.