Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
| 1 | --- |
| 2 | type: "reference" |
| 3 | title: "Tool Router Workbench Retention" |
| 4 | description: "Public support knowledge for Tool Router Workbench Retention." |
| 5 | category: "sessions-and-execution" |
| 6 | visibility: "public" |
| 7 | timestamp: "2026-07-16T00:00:00Z" |
| 8 | tags: |
| 9 | - "tool-router-workbench" |
| 10 | --- |
| 11 | # Tool Router Workbench Retention |
| 12 | |
| 13 | Use this when customers ask whether Tool Router workbench state persists forever, or whether personal data used in the remote workbench is retained indefinitely. |
| 14 | |
| 15 | ## A “fresh” client label can still reuse the same sandbox |
| 16 | |
| 17 | Workbench and sandbox reuse follows the actual Tool Router session, not an arbitrary client-side session label. Reusing the same `trs_*` session or MCP URL can reuse the same cached workbench and sandbox. |
| 18 | |
| 19 | Create a new Tool Router session and use its newly returned MCP URL when a |
| 20 | workflow requires an independent sandbox rather than reused session state. |