Release v1.6.0 · karashiiro/my-cool-proxy

Major Changes

Large tool results are now automatically offloaded to the database with schema summaries. When an execute script produces a result larger than the configurable resultSizeThreshold (default 50KB), the gateway replaces it with a compact, type-specific summary (item structure for arrays, key listing for objects) and an execution ID. Agents retrieve and filter the full data in a follow-up script via _gateway.get_result(). This prevents massive tool results from blowing out the context window.
Upstream stdio servers now inherit the client's working directory. In HTTP mode, the gateway resolves the connected client's roots before spawning upstream stdio processes, so servers like Playwright operate in the client's project directory instead of the gateway's.

All unbounded async operations now have timeouts. Session restoration (30s), HTTP client connect (30s), pagination page fetches (10s), and notification re-list handlers (15s) will fail with a TimeoutError instead of hanging indefinitely when an upstream server becomes unresponsive.
Session data and tool inspection states now survive gateway restarts. Previously, session capabilities were deleted on disconnect, which broke session restoration and caused a cascade-deletion of event history. tool-details is now backed by the database instead of an in-memory map, so agents don't need to re-inspect tools after a gateway restart.
Added --paths CLI flag to print platform-specific config, data, and log directory paths.
Skill resources now include MCP annotations (audience, priority, lastModified) and a size field in their metadata.
New sessions are now blocked during HTTP shutdown to prevent race conditions.
Database schema now uses PRAGMA user_version for versioning with automatic migration (v0 -> v1). Cascading deletions are now correctly handled with a foreign key constraint.
Updated documentation.

Full Changelog: v1.5.4...v1.6.0