AI tool integration

Wire SEIF into Claude, Cursor, Copilot, Gemini, Antigravity, and Codex via standard configuration files.

SEIF integrates with AI tools through the configuration files they already read. Place the relevant file at your project root and the tool loads SEIF context and provenance hooks automatically.

Claude / Claude Code

Reads CLAUDE.md. SEIF hooks into pre/post tool-use events for automatic signing and quality measurement.

Cursor

Reads .cursor/rules/*.mdc and an MCP server entry. Run seif setup cursor to generate both.

GitHub Copilot

Reads .github/copilot-instructions.md. SEIF modules are injected via instruction prepend.

Gemini CLI

Reads GEMINI.md at the project root for context and signing hooks.

Antigravity CLI (agy)

Launched via seif start --client antigravity. SEIF wires the agy hooks in ~/.gemini/antigravity-cli/hooks.json — PreInvocation injects the grounding kernel, PreToolUse/PostToolUse run the gate, and Stop runs session closure.

OpenAI Codex

Reads AGENTS.md for agent directives, including SEIF protocol instructions.

Launching a grounded session

seif start bootstraps the workspace and launches your configured AI client, grounding it from the first message. Which client launches comes from a per-host registry, not a hardcoded default:

seif start                            # the registry default (claude-code out of the box)
seif start --client antigravity       # launch the Antigravity CLI (agy)
seif start --client gemini            # launch the Gemini CLI

seif admin client list                # registered clients + which is default
seif admin client set-default gemini  # change the default seif start launches

A client must be registered before seif start --client <name> can launch it. The built-in adapters are claude-code, gemini, and antigravity; register a missing built-in with, e.g.:

seif admin client add --name antigravity --bin agy --adapter antigravity

Model Context Protocol (MCP)

The CLI ships an MCP server so any MCP-capable client can call SEIF governance tools directly.

seif mcp serve

For Cursor specifically:

seif setup cursor
# writes .cursor/mcp.json and .cursor/rules/*.mdc

After setup, restart your client and enable the SEIF server. The first tool each session is session_orient, which returns the grounding kernel and a snapshot of your workspace memory.

What gets loaded

On session start, a SEIF-aware tool loads:

the conduct constitution (operating maxims, with their control-theory origin model),
your memory modules (decisions, conventions, observations),
open governance cycles and high-priority pending items.

This is how a fresh session on any machine starts already knowing your project.