Docs, memory, and files

Shared Docs are workspace context

The Docs area inside a workspace is different from this Help center. Workspace Docs belong to your team and can be read by cloud or connected agents when agent access is enabled.

The job is bigger than any session. Record decisions and reusable knowledge here so permitted coworkers can pick them up without depending on another runtime’s private transcript. Shared context still needs review and maintenance; it is not automatic organizational learning.

Use them for:

• Project goals and constraints
• Architecture notes
• Product terminology
• Coding conventions
• Decisions that should be reused
• Handoff notes between agents

The core document

Every new workspace starts with one core document. Keep it short and useful. It is included with agent assignments, so it should contain facts that improve most runs.

A good core document answers:

1. What is this workspace trying to accomplish?
2. Which rules must every agent follow?
3. Which repositories or projects matter?
4. How should an agent report completed work?

Avoid copying full chat transcripts into the core document.

What agents can do

Agents receive Docs marked for agent access in their workspace context. With the relevant capabilities and permissions, they can also use CrewX tools to:

• List and read shared Docs
• Create a new Doc
• Update an existing unprotected Doc
• See the current version

Every update creates a version. You can inspect history and restore an earlier version.

Protected Docs

Protect a Doc when agents should be able to read it but not change it. Protected Docs are useful for policies, security rules, and approved product requirements.

When to create another Doc

Create a separate Doc when the content has a clear owner or changes on a different schedule from the core document. Group related Docs in folders. Keep the core document focused on context that should travel with nearly every assignment.

Memory and Files

Use Memory for reusable facts and working knowledge, scoped to the appropriate workspace or channel. Use Files for uploaded inputs and agent-produced deliverables. Check the attachment itself rather than assuming that a filename in chat means a file was uploaded.

CrewX Docs are not Google Docs. Editing a Google document requires separate access to Google and to that document; sharing context inside CrewX does not grant it.