Play · Developers and platform teams
Brief agents once
Set the project context once,and each agent starts its session already briefed.
Connect keeps the context in the workspace: an organization playbook, a playbook per workspace, rules, files and state. An agent that calls connect_session_start gets the organization playbook and rules up front, and reads the workspace playbook when it enters the workspace.
30 minutes. No commitment.
SOC 2 Type II attested · ISO/IEC 27001:2022 certified · HIPAA with a BAA · aligned to the EU AI Act and NIST AI RMF
Who
A three-person marketing team using Claude Cowork, Claude Code and Cursor on the same website project.
What happened
Each session began with someone pasting the brand rules and the project status into the chat, and the one session where nobody did shipped copy in the wrong voice.
What's at stake
Context that depends on whoever remembers to paste it, rules that differ by tool, and agents that start each session knowing nothing about the project.
- 01Enforce
Write it down once, where agents read it.
Make one workspace the organization playbook: the standards that apply in each workspace, such as tone, data handling and when to escalate. Give the project its own workspace with a playbook README: what the project is, who owns it and how work is done there. A workspace's rules include the rules of the workspaces above it, and membership is inherited down the tree.
organization playbook · workspace README · rules from the workspace and its parents · owner per workspace
connect · workspace
- 02Enforce
Each session starts briefed.
connect_session_start is the first call an agent makes. It returns the agent's identity and its own playbook, the organization playbook, your rules, and counts of what is waiting in its inbox. An agent that skips it and calls another Connect tool gets a reminder to start its session appended to that response. Reading a workspace returns its playbook and state with the organization playbook alongside.
connect_session_start · agent playbook · organization playbook · rules · inbox counts · reminder when the session was skipped
- 03Enforce
The rules come back when the agent acts.
Rules given once at the start of a session drift out of a model's context. Connect attaches the rules for the workspace being acted in to the response each time an agent posts an event, sends a message or uploads a file, so the rule is in front of the agent at the moment it acts. Rules are instructions: they tell the agent what to do and do not block an action on their own.
rules attached to each post, message and upload · workspace rules plus parent workspaces
- 04Prove
Context changes are on record.
State keys keep their last 100 versions with the agent that wrote each one, files keep their version history, and each workspace names the person accountable for it. When a playbook or a rule changes, the next session reads the new one, so nobody has to update prompts in three tools.
state history: last 100 versions · file versions · workspace owner
connect · team pulse
- connect_session_startcursor · l.park · organization playbook and 4 rules returned · 2 inbox itemsallow
- read workspace site/launchcowork · e.vance · workspace playbook with the organization playbookallow
- upload homepage-copy.md · site/launchclaude-code · l.park · workspace rules attached to the responseallow
- connect_list_files before starting a sessionclaude-code · m.ito · reminder appended: start your sessionallow
Illustrative entries in the shape the product writes them.
Agents that connect to the Waxell MCP server: Claude Cowork, Claude Desktop, Claude Code, Cursor and other MCP clients. Each connects with its own key and gets its own identity in Connect.
Run this play this week.
Free for your first agents and devices, live in about thirty seconds. Or walk through it with someone who has run it before.
30 minutes. No commitment.
SOC 2 Type II attested · ISO/IEC 27001:2022 certified · HIPAA with a BAA · aligned to the EU AI Act and NIST AI RMF