workspace

To read and write session files across multiple agents, use a unified workspace that provides logical path namespaces. This allows agents to find files created by other skills and immediately access shared artifacts like code outputs and documents.

Cross-skill file sharing for binary images and documents works through encoding-aware transfers. The workspace automatically returns text for plain files and base64 for binary files, and accepts base64 encoding when writing binaries to ensure data integrity.

Yes, you can use logical path namespaces to exchange interpreter results between tools. This unified read and write access centralizes artifact sharing, allowing a code agent to save a report and an analysis agent to read it immediately.

The best way to isolate session file access is to use a workspace that provides automatic userId and sessionId injection. This mechanism ensures isolated session access, preventing cross-contamination of artifacts between different users and sessions.

You need a unified file workspace for multi-agent workflows to eliminate ad hoc file passing and reduce friction. It centralizes access to artifacts like code agent outputs and office documents while handling text and base64 encoding automatically.