# Claude Code

Add the authenticated Fabric code graph and governed Fractal memory to [Claude Code](https://claude.com/claude-code).

## Prerequisites

Node.js 20.18.1+, a Cognisos account, Claude Code 2.x, and a marked project you want indexed.

## Install

```bash
cd /path/to/your/project
npx -y @cognisos/fabric-mcp@beta setup
```

Setup signs you in through Cognisos, stores the credential in the OS keychain,
verifies both local engines, and atomically registers one private exact wrapper.
`setup --local` is not a public beta path.

## Verify

Restart Claude Code, then run `/mcp`. You should see one `fabric` connector as
**connected**, with both `fabric_*` and `fractal_*` tools.

The required Fabric Code Indexer daemon should be ready. The separate Fractal
background capture daemon is optional and off by default; `not_running` there
does not mean the connector failed.

## Add the Fabric Agent plugin (optional)

Fabric Agent adds governed-work classification, evidence-status language, and
continuity guidance directly to Claude Code, plus `/fabric-status`,
`/fabric-continuity`, and `/fabric-govern` commands.

```bash
claude plugin marketplace add cognisos-ai/5thDev
claude plugin install fabric-agent@5thdev
```

Restart Claude Code afterward. The plugin uses your already-installed Fabric
MCP connector, it doesn't install a second MCP server. Lifecycle observation
is off by default; see the
[plugin repo](https://github.com/cognisos-ai/5thDev) for exactly what it does
and doesn't capture.

## Try it

```text
> Use fabric_explain to explain `parseDoc`, use fabric_impact to show what it can affect, then recall the governed decision that explains why it exists.
```

Claude combines the local graph with governed cross-session memory. Project
source is not uploaded by the local engines.

## See also

* [Cursor](/integrations/cursor) — same Fabric, different host