Skip to main content

Configuration

AGIT works out of the box with sensible defaults, but you can customize its behavior.

Generated Files

When you run agit init, these files are created:

.agit/ Directory

The neural graph storage, similar to .git/:

.agit/
├── objects/ # Content-addressable object store
├── refs/ # Branch references
│ └── heads/ # Branch head pointers
├── HEAD # Current branch pointer
└── index # Staging area (JSONL format)

Editor Configuration Files

AGIT generates configuration files for AI editors:

FileEditorPurpose
CLAUDE.mdClaude CodeInstructions for Claude to log thoughts
.cursorrulesCursorInstructions for Cursor AI
.windsurfrulesWindsurfInstructions for Windsurf AI

These files tell your AI assistant to:

  1. Call agit_log_step when planning
  2. Record user intents and AI reasoning
  3. Help create meaningful commit summaries

Git Integration

AGIT works alongside Git, not replacing it:

  1. Parallel Storage: .agit/ lives alongside .git/
  2. Linked Commits: Neural commits reference git commits
  3. Branch Tracking: AGIT follows your git branches
# 1. Work on your feature with AI assistance
# (AI automatically logs thoughts)

# 2. Stage changes
git add .

# 3. Commit with AGIT (creates git + neural commit)
agit commit -m "Add feature X"

MCP Server Configuration

The AGIT MCP server starts automatically when needed. For manual configuration:

# Start server manually
agit server

# With custom port (if needed)
agit server --port 8080

Ignoring AGIT Files

Add to your .gitignore if you don't want to share neural commits:

# Ignore AGIT data (optional)
.agit/

However, we recommend committing the editor config files so your team shares the same AI instructions:

# Don't ignore these
# CLAUDE.md
# .cursorrules
# .windsurfrules

Next Steps