Documentation Index
Fetch the complete documentation index at: https://docs.enagrams.com/llms.txt
Use this file to discover all available pages before exploring further.
Overview
sync is the primary context-loading tool. It reports what the agent is currently working on and returns the full workspace state in a single call — agents, decisions, conflicts, file reservations, work packages, and branch directives.
Agents typically call sync at the start of a task and when they need a context refresh mid-session. Session management (creation, heartbeat, termination) is handled automatically by IDE hooks — sync is for explicit context requests.
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
task | string | Yes | Brief description of the current task |
session_id | string | No | Session ID from a previous sync response — enables per-tab session tracking |
files | string | No | Comma-separated file paths the agent currently plans to work on |
branch | string | No | Current git branch |
agent_type | string | No | One of cursor, claude_code, windsurf, copilot, custom |
plan | string | No | JSON string: { goal, approach, patterns_needed, files_planned, dependencies } |
Response
Response Fields
| Field | Description |
|---|---|
session_id | Pass back on the next sync call to maintain session continuity |
agents | Other active agents in the workspace |
decisions | Recent architectural decisions |
conflicts | File overlaps and proximity warnings |
reserved_files | Files locked by other agents |
your_work | Work packages claimed by this user |
branch_directive | Current team branch and whether a pull is needed |
meeting_context | Summary from the most recent meeting |
learnings | Team learnings surfaced since your last sync |
contracts | Shared interface contracts other agents have published |
stale_decisions | Decisions whose linked symbols have drifted |
conventions | Active conventions that may gate your edits (see convention_list) |
Example
When to Call sync
- Start of a task — get current team context before writing any code
- Before touching a new area — check for conflicts and existing decisions
- After a long pause — refresh context if the session has been idle
- When the agent mentions uncertainty — “I’m not sure how the team handles auth” → call
sync