sync

[solution]

Flushes pending watcher changes into the index now; full: true forces a complete re-scan. Rarely needed because every query self-flushes via the freshness gate.

Why this tool exists

Queries self-flush pending changes, so sync exists for bulk filesystem changes the watcher has not delivered yet.

How it helps the agent

The model can request an explicit index refresh after generated-code changes or branch switches.

Parameters

Name	Type	Required	Description
full	boolean	No	false: flush pending changes; true: full re-scan and rebuild.

Examples

Flush pending changes

Request 
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "sync",
    "arguments": {}
  }
}

Force a full re-scan

Request 
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "sync",
    "arguments": {
      "full": true
    }
  }
}

Response Notes

Returns flushed, rescanned, and the resulting index revision.