Keep unfinished work here, with enough context to find the owning code and decide what to do next. Check the source and tests before starting an item, add an issue link when work is selected, and delete the entry when it is resolved. The IDs are stable references, not priorities or release commitments. Recurring release checks belong in Release .
Runtime and resource limits
RT-1 — Resolve or bound process-environment changes during late R startup. R can initialize after Python and its native services are running. R integration still sets library environment variables before initialization, and R’s bootstrap can change the process environment. Establish which changes can race with native readers and choose a safe embedding interface or an explicit restriction. Verify startup-package behavior, existing Python objects and SQL connections, and reentrant callbacks. Separate runtime threads would not remove this process-wide risk.
RT-2 — Decide limits for internal frames and queued stdin. The worker transport has no general frame-size or stdin-queue cap. Public output budgets do not bound these allocations. Define rejection, streaming or backpressure, and cancellation behavior before adding limits.
RT-3 — Define recording retention and retrieval policy. Recordings have per-output limits but no aggregate disk quota, automatic cleanup, built-in read tool, or redaction. Select the required retention and retrieval behavior; protect active sessions and user-managed files.
RT-4 — Replace the R DuckDB Arrow adapter when incremental data-frame fetching is supported. The temporary adapter lives in the SQL bridge . Check supported DuckDB R versions for upstream streaming support , then use ordinary DBI retrieval and remove Arrow-specific retained-result handling. Preserve data-frame results, row limits, previews, and cleanup; the scratch catalog also serves exact preview formatting.
RT-5 — Reproduce and fix interrupt completion during R DuckDB 2.0 Arrow fetching. A query can remain active after an interrupt while its Arrow result is fetched. Exercise this through Console’s SQL API and verify interruption and retained connection state before advancing the DuckDB fixture pin in shared R support . Those tests pin DuckDB 1.5.6; production package selection is independent of that fixture.
RT-6 — Bound the remaining waits on the recording writer. Shutdown finalization and the integrator’s recording request wait for the recording writer without a limit, so a filesystem call that never returns keeps the process alive after MCP input closes. Before adding a deadline, decide what abandoned finalization leaves behind (writable files, no recording_ended event, incomplete projections) and how Console reports it.
Documentation and agent usability