Drive context
Keep instructions, design guidance, source files, and Agent outputs together in a private Workspace with owner-reviewed revisions.
AGENT CONTEXT
Give every Agent the same brief
Keep your instructions, design guidance, and source files together. The Agents you connect can start from the same reviewed brief, wherever you work.
Owner reviewed
Make the first five minutes feel simple.
- Instructions
- Write for someone setting up their first workspace. Explain one action at a time.
- Design
- Use clear labels, level graphics, and a readable layout on every screen.
- Sources
- Approved product notes and the current project files.
Publishing context
Carry the approved brief into Pages so an Agent can create the right output while visibility and sharing remain explicit owner decisions.
Email context
Release approved email as passive text for your Agent. Attachments are listed as metadata; attachment conversion is not enabled yet.
HOW IT FITS TOGETHER
Context that follows the work
Keep the brief beside the work and share it with only the Agents that need it.
01
Instructions · AGENTS.md
Hosted Agents can receive the current Agent Guide as a managed block. External Agents read the same owner-approved operating contract over MCP.
02
Design · DESIGN.md
Store the project’s visual and interaction rules beside its working files, with immutable revisions and visible Agent proposals.
03
Approved product context
Use the same reviewed brief across Drive, Pages, Wiki, and released email without giving every Agent access to every surface.
THE RULES
Clear boundaries at the address
Claw Me keeps context portable and reviewed while preserving the permissions and safety boundaries of each product surface.
Identity stays separate
Agent Context does not rewrite SOUL.md or IDENTITY.md outside a hosted runtime. Personality and visible identity remain owner-controlled.
Access follows the surface
Drive, Pages, Wiki, and Email keep separate permissions. Sharing context with an Agent does not silently grant publishing or delivery authority.
Email stays untrusted
An approved sender or released message can provide context, but it cannot approve a purchase, publish a Page, or expand the Agent’s permissions.
Review before replacement
Agents propose brief and file changes in an isolated Workspace revision. The approved context does not change until the owner accepts the proposal.
GOOD TO KNOW
Before you use it
What becomes Agent Context?+
The owner chooses the approved instructions, design guidance, Wiki knowledge, Drive files, Page rules, and released email that are relevant to the work. An Agent receives only the parts allowed by its scopes.
Which Agents can use the context?+
Managed OpenClaw is the first hosted runtime. Other owner-authorized clients can read the Agent Guide and work with permitted Drive, Pages, Wiki, and Email context through Claw Me’s provider-neutral MCP tools.
Does Claw Me edit SOUL.md or IDENTITY.md?+
Not as part of Agent Context. Instructions and project design belong in AGENTS.md and DESIGN.md. Personality and visible identity remain separate.
Does context grant permission to publish or send?+
No. Context helps an Agent understand the work. Publishing a Page, releasing email, and delivering output still follow their own owner-controlled permissions and approval rules.
Give every Agent the same brief
Keep your instructions, design guidance, and source files together. The Agents you connect can start from the same reviewed brief, wherever you work.