Codegraph - powered by Wexa (VS Code / Cursor / Windsurf)

Keeps the Wexa Fabric context graph (CognoDB) in lockstep with your local git working tree via the local fabric-sync daemon.

Connect this repo to Fabric

Open your repo folder, then either:

• Click the notification "Sign In & Set Up" that appears when the repo isn't connected yet, or
• Click 🔌 Codegraph: set up in the bottom-left status bar, or
• Cmd+Shift+P → Codegraph: Sign In & Set Up This Repo

The flow: email + password (Fabric identity) → pick a project (your token only sees projects your role — user / org admin / super admin — can access) → pick or auto-create the codebase connector → optional department id. Your organization comes from the sign-in token, never typed. It then registers the repo (.fabric/sync.json, auto-gitignored), installs git hooks, and starts the initial ingest. Every push authenticates as you; the harness rejects tokens from other orgs.

After connecting

Open the Codegraph activity-bar panel for:

• Live sync status per repo (branch, elements, errors)
• One shared Connection card (org / department / project / connector) with Change buttons — the machine has a single Fabric identity, so it is shown once, not per repo
• Sync Now / Retry / Sign In (auth still opens the Fabric app in the browser)

Status bar still shows synced / syncing / daemon-down / error.

Requirements

The fabric-sync binary must be installed and resolvable (PATH, or the fabricSync.binaryPath setting) — build it with cargo build --release in codegraph/. The extension itself starts and supervises the daemon automatically: on sign-in, on every VS Code restart, and whenever the daemon is found unreachable (crash, machine reboot). You never need to run fabric-sync daemon or ./fabric.sh start by hand.

The backend services (identity, data-service, harness, api-gateway) are pre-configured to reach the hosted Fabric deployment out of the box.

Claude Code / Codex / CLI agents

MCP or SDK alone does not enable sync. Sync follows the local filesystem.

Recommended (auto-connect): use the Fabric Connect launcher as the MCP command so connecting an agent also starts sync:

cd tools/fabric-connect && npm install && npm link
# MCP config command: fabric-connect

See docs/fabric/mcp-connection-guide.md (Automatic Fabric Sync section) and tools/fabric-connect/README.md.

After this repo is registered (Sign In above), you can also bootstrap hooks only:

./tools/fabric-sync-connect.sh
# or:
fabric-sync supervise --repo . --json --install-agents
fabric-sync connect --repo .

That installs:

• ~/.local/bin/fabric-sync PATH shim
• git hooks (post-commit / checkout / merge / rewrite)
• Claude Code hooks (.claude/settings.json + ~/.claude/settings.json)
• Codex hooks (.codex/hooks.json + ~/.codex/hooks.json)

Any local agent that writes files then wakes the same daemon. Cloud/remote agents editing a different machine still need fabric-sync / fabric-connect running there (use POST /v1/codesync/bootstrap for short-lived tokens).