Let agents reason about the code being changed

What it changes

• Expose changed symbols, signatures and documentation
• Keep bodies private from the working-tree stream
• Make uncommitted limitations explicit when the companion is absent
• Combine local change context with organization-wide committed relationships

A practical example

A developer renames an interface and changes its signature before committing. The working-tree companion publishes that structural diff, so the agent can combine the active shape with committed downstream relationships instead of describing the old interface as current.

Built for trustworthy answers

Every answer carries its own boundaries: what was searched, which revision was used, what was omitted and whether a limit degraded the result. That context is part of the product, because confident ambiguity is worse than an honest next action.

Use it across the organization

SynapCTX exposes this capability over MCP so compatible coding agents can use the same organizational context without separate retrieval stacks or copied instruction files.