# Cognisos Fabric Beta Quickstart The beta is one authenticated connector: the local Indexer plus governed Fractal memory, combined. Sign in with a Cognisos account and you're running in about five minutes. ## Prerequisites * Node.js 20.18.1 or newer * macOS or Linux * A Cognisos account (create one during sign-in) * Claude Code, Claude Desktop, Cursor, or Codex * A project directory with a recognized marker (`.git`, `package.json`, `Cargo.toml`, `pyproject.toml`, `go.mod`, Maven, or Gradle) * A repository under 1.5 GB ## Install and sign in From inside the project you want Fabric to understand: ```bash cd /path/to/your/project npx -y @cognisos/fabric-mcp@beta setup ``` Setup opens Cognisos sign-in in your browser, indexes your project, and registers one `fabric` connector in every client it detects, all in one atomic step. Setting up from a different directory? Pass `--project /path/to/your/project`. Restart Claude Code, Claude Desktop, or Cursor afterward. A new Codex session picks up the connector automatically. ## Verify both engines Ask your client to run: ```text fabric_status fractal_status ``` `fabric_status` confirms the index is built and current. `fractal_status` confirms the memory engine is live. The Fractal background *capture* daemon is a separate, optional feature that's off by default, so seeing `not_running` there is expected, not a failure. ## 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. That's the core loop: current code structure plus governed cross-session memory, in one place. ## Sharing Where enabled for your beta account, share Fabric state with teammates via the pinned Liminal commands: `liminal fabric list`, `liminal fabric share`, and `liminal fabric accept`. ## Sign out ```bash npx -y @cognisos/fabric-mcp@beta logout ``` This revokes your device key, unregisters the connector, and removes local Fabric data. Add `--all-devices` to revoke every device on the account instead of just this one. ## Troubleshooting **WSL2** is best-effort, not a release-qualified target. A Windows-host browser may be unable to reach the Linux guest's OAuth callback, so a browser authorization screen alone doesn't mean setup finished. Wait for the WSL terminal to report success, then confirm with `doctor`. If the terminal hangs, use native Linux or an isolated Linux VM instead. **One release line per OS user.** This beta supports multiple projects, but only one Fabric release line per user account on a machine, so don't install stable and beta into the same profile. Setup fails closed if it detects incompatible project or runtime ownership; use a separate OS user, VM, or container to compare versions safely. **Repeated Keychain prompts on macOS.** Setup and your AI client run as separate processes, so macOS may ask for Keychain access at both points, which is expected, not a bug. Never paste your credential into a prompt or config file. If prompts continue past your first successful client launch, run `npx -y @cognisos/fabric-mcp@beta doctor` and check its output (it prints your project path, verified IDs, and version identity). **`setup --local` is disabled.** Public beta access is account-gated, so this flag is intentionally rejected.