# Cognisos Fabric Beta Quickstart The beta is one authenticated connector backed by the local Indexer and governed Fractal memory. The Indexer is a subsystem, not the complete beta. ## Prerequisites * Node.js 20.18.1 or newer. * macOS or Linux. * A Cognisos account. You can create one during browser sign-in. * Claude Code, Claude Desktop, Cursor, or Codex. * A marked project directory (`.git`, `package.json`, `Cargo.toml`, `pyproject.toml`, `go.mod`, Maven, or Gradle). WSL2 is best-effort and is not a release-qualified target for this candidate. A Windows-host browser may be unable to reach the Linux guest's `127.0.0.1` OAuth callback. A browser authorization page alone is not proof that setup completed: wait for setup to report success in the WSL terminal, then require `doctor` to pass. If the terminal keeps waiting or times out, the credential exchange did not complete; use native Linux or an isolated Linux VM for a qualified beta run. ## Install and sign in In a terminal, enter the project you want Fabric to understand, then run setup: ```bash cd /path/to/your/project npx -y @cognisos/fabric-mcp@beta-candidate setup ``` Setup uses the exact directory you are in; you do not need to copy its full path. For automation or setup from another directory, use `setup --project /path/to/your/project`. Multiple projects are supported, but this beta supports only one Fabric release line per OS user. To compare stable and beta safely, use a separate OS user, VM, or container; do not install both into the same user profile. Setup fails closed when verified project/runtime ownership is incompatible. The browser opens Cognisos sign-in. After authorization, setup verifies the OS keychain, the immutable Fractal distribution pin, the platform Indexer helper, the initial project graph, watcher freshness, and one combined connector. It then registers that connector atomically in the supported clients it detects. On macOS, setup and the AI client's first connector launch are separate Node processes, so Keychain may ask for access at both boundaries. Never paste the credential into a prompt or config. If prompts continue after the first successful client launch, run `npx -y @cognisos/fabric-mcp@beta-candidate doctor` and report the output. Doctor prints the canonical project path, verified project/store IDs, running version identity, and the supported one-release-line-per-user profile. Do not use `setup --local`. Public beta access is account-gated and that accountless path is disabled. Restart Claude Code, Claude Desktop, or Cursor after setup. A new Codex session picks up the connector automatically. ## Verify both engines Open the client's tool list and confirm one `fabric` connector contains both `fabric_*` and `fractal_*` names. Then ask the assistant to call: ```text fabric_status fractal_status ``` `fabric_status` should report the exact helper identity, completed initial index, active watcher, and fresh project graph. `fractal_status` should report the pinned local runtime and governed store status. Do not confuse the two daemon states: * The **Fabric Code Indexer daemon** is required and should be ready. * The **Fractal background capture daemon** is optional and off by default. The Fractal memory engine is still required and usable through the connector. Seeing `not_running` for its optional background capture daemon is expected and does not by itself indicate a failed setup. ## Prove value Try a combined workflow: > Use `fabric_explain` to explain the main entry point and `fabric_impact` to > identify a risky dependency. Then use Fractal recall to recover the relevant > prior decision, including its provenance and whether any later correction > demoted it. This demonstrates the intended product: current code structure plus governed cross-session cognition in one agent-visible surface. ## Sharing The existing Shared Fabric transport is preserved. Where enabled for your beta account, use the pinned Liminal commands `liminal fabric list`, `liminal fabric share`, and `liminal fabric accept`. The unified installer does not create a parallel sync protocol. ## Sign out ```bash npx -y @cognisos/fabric-mcp@beta-candidate logout ``` Logout revokes the device key, unregisters the connector, clears the OS keychain entry, and removes local Fabric data. Add `--all-devices` only when you want every device key revoked.