Introduction

Semantica is observability and control for AI-assisted development. It tracks what AI coding agents do in your repositories and ties that activity to your Git commits, giving you a clear, auditable record of who or what wrote your code and how.

Git tells you what changed. Semantica tells you how it happened.

What Semantica does

When you run semantica enable in a repository, Semantica installs lightweight Git hooks that fire automatically on every commit. From that point on, each commit:

  • Creates a checkpoint: a full file manifest snapshot of the repository at that moment
  • Ingests agent session data from detected AI providers (Claude Code, Cursor, Kiro IDE, Kiro CLI, Gemini CLI, GitHub Copilot)
  • Computes AI attribution: what percentage of changed lines match AI-generated output, broken down by file
  • Appends a Semantica-Checkpoint trailer to the commit message linking the commit to its checkpoint

All of this happens in a background worker, fully detached from your terminal. Commits are never slowed down.

Why it matters

As AI coding agents become standard tools, the question "what percentage of this PR was AI-generated?" becomes important for code review, compliance, and team visibility. Semantica answers it automatically, without requiring developers to change how they work.

For teams using multiple agents, Semantica normalizes attribution data from all six supported providers into one consistent format. Whether your team uses Claude Code, Cursor, or Kiro IDE, you get the same structured output.

For organizations that need enforcement, Semantica can post attribution results as GitHub check runs, enabling branch protection rules that gate merges on AI attribution thresholds.

Where data lives

By default, all Semantica data is stored locally in a .semantica/ directory inside your repository, alongside .git/. This directory is automatically added to .gitignore. Nothing is sent anywhere unless you explicitly authenticate with semantica auth login and connect the repo with semantica connect.

.semantica/
  settings.json     # Configuration
  lineage.db        # SQLite database (checkpoints, sessions, attribution, playbooks)
  objects/          # Content-addressed blob store (SHA-256, zstd compressed)
  worker.log        # Background worker logs

Semantica never writes to Git history, never creates side branches, and never modifies agent session logs.

Supported platforms

  • macOS and Linux (x86_64 and arm64)
  • Git is required. Semantica hooks into the commit lifecycle
  • At least one supported AI provider for capture (see Integrations)

Next steps

  • Quickstart: install and enable in under two minutes
  • Core concepts: understand checkpoints, sessions, and attribution
  • Installation: all install methods including Homebrew and shell script