Tilde

🏠 tilde

Your AI agents' home directory

tilde is a privacy-first Model Context Protocol (MCP) server that acts as the universal memory and profile layer for AI Agents.

Configure once. Use everywhere. Your data, your control.

Supports profile management, skills, resume import, and team sync.

The Problem

Every time you switch AI tools, you face the same issues:

• 🔄 Repetition: "I'm a Senior SWE", "I prefer Python", "Don't use ORMs"
• 🧩 Fragmentation: Preferences learned in Cursor aren't available in Claude
• 🔒 Privacy Concerns: Unsure who has access to your personal context

The Solution

tilde acts as a "digital passport" that your AI agents can read:

┌────────────────────────────────────────────────────────────┐│  Claude Desktop  │   Cursor   │  Windsurf  │  Your Agent   │└────────┬─────────┴─────┬──────┴─────┬──────┴───────┬───────┘         │               │            │              │         └───────────────┴─────┬──────┴──────────────┘                               │                    ┌──────────▼──────────┐                    │   tilde MCP Server  │                    │   (runs locally)    │                    └──────────┬──────────┘                               │                    ┌──────────▼──────────┐                    │   ~/.tilde/profile  │                    │   (your data)       │                    └─────────────────────┘

Features

• 🏠 Local-First: Your data stays on your machine by default
• 📋 Structured Profiles: Identity, tech stack, knowledge, skills
• 🔌 MCP Standard: Works with any MCP-compliant agent
• ✏️ Human-in-the-Loop: Agents can propose updates, you approve them
• 🔧 Extensible Schema: Add custom fields without modifying code
• 🔒 Skills Privacy: Control which skills are visible to agents (public/private/team)
• 🤖 Agent-Callable Skills: Define skills that AI agents can invoke on your behalf
• 📄 Resume Import: Bootstrap your profile from existing resume/CV
• 📚 Knowledge Sources: Books, docs, courses, articles - unified learning model
• 👥 Team Sync: Share coding standards across your team

Quick Start

Installation

# Install from PyPIpip install tilde-ai
# Initialize your profiletilde init

# Clone the repositorygit clone https://github.com/topskychen/tilde.gitcd tilde
# Install with uvuv sync
# Run locallyuv run tilde init

Configure Cursor

Add to .cursor/mcp.json in your project (or ~/.cursor/mcp.json for global access):

{  "mcpServers": {    "tilde": {      "command": "npx",      "args": ["-y", "tilde-ai"]    }  }}

Once configured, you'll see tilde in your MCP servers with all available tools and resources:

[Cursor MCP Settings]

Configure Antigravity

Add to .gemini/antigravity/settings.json in your project:

{  "mcpServers": {    "tilde": {      "command": "npx",      "args": ["-y", "tilde-ai"]    }  }}

Configure Claude Desktop

Add to ~/Library/Application Support/Claude/claude_desktop_config.json:

{  "mcpServers": {    "tilde": {      "command": "npx",      "args": ["-y", "tilde-ai"]    }  }}

Example Usage

Once configured, your AI agent can access your profile. Try asking:

"What is my name?"

The agent will use the get_profile tool to fetch your identity and respond with your name and role:

[Cursor Demo]

Create Your Profile

Edit ~/.tilde/profile.yaml:

schema_version: "1.0.0"
user_profile:  identity:    name: "John Doe"    role: "Full Stack Developer"    years_experience: 10    # Add any custom fields you need:    timezone: "America/Los_Angeles"    pronouns: "they/them"
  tech_stack:    languages:      - TypeScript      - Python      - Go    frameworks:      - React      - FastAPI      - Next.js    preferences:      - "Prefer composition over inheritance"      - "Write tests before implementation (TDD)"      - "Use descriptive variable names over comments"    environment: "VS Code, Docker, Linux/MacOS"
  # Knowledge sources: books, docs, courses, articles, etc.  knowledge:    domains:      web_development: "Focus on performance and accessibility"      ml_ops: "Experience deploying ML models to production"        sources:      - title: "Clean Code"        source_type: "book"        insights:          - "Functions should do one thing"          - "Prefer meaningful names over documentation"      - title: "React Documentation"        source_type: "document"        url: "https://react.dev"        insights:          - "Prefer Server Components for data fetching"
  # Agent-callable skills (Anthropic SKILL.md format)  skills:    - name: "code-formatter"      description: "Format code using project conventions"      visibility: "public"      tags: ["automation", "code-quality"]    - name: "deploy-staging"      description: "Deploy current branch to staging environment"      visibility: "team"    - name: "expense-reporter"      description: "Generate expense reports from receipts"      visibility: "private"
team_context:  organization: "Acme Corp"  coding_standards: "ESLint + Prettier, PR reviews required"  architecture_patterns: "Monorepo with shared packages"  do_not_use:    - "jQuery"    - "Class components in React"

MCP Resources

tilde exposes these resources to agents:

MCP Tools

CLI Commands

tilde init                    # Create default profiletilde show                    # Display current profiletilde show skills             # Show skills section onlytilde show --full             # Show full content without truncationtilde edit                    # Open profile in $EDITORtilde config                  # Show current configurationtilde pending                 # List pending agent updatestilde approve <id> [id2...]   # Approve one or more updatestilde reject <id> [id2...]    # Reject one or more updatestilde approve --all           # Approve all pending updatestilde reject --all            # Reject all pending updatestilde approve --all -e <id>   # Approve all except onetilde log                     # View update historytilde ingest <file>           # Extract insights from a documenttilde export --format json    # Export profile

Document Ingestion

# Ingest a book and extract insightstilde ingest "~/Books/DDIA.pdf" --topic data_systems
# Dry run to preview what would be extractedtilde ingest notes.md --dry-run
# Auto-approve high-confidence updatestilde ingest paper.pdf --auto-approve 0.8

Resume Import

Bootstrap your profile from an existing resume:

# Import resume (PDF, DOCX, or text)tilde ingest ~/Documents/resume.pdf --type resume
# Preview what would be extractedtilde ingest resume.pdf --type resume --dry-run
# Auto-approve high-confidence itemstilde ingest resume.pdf --type resume --auto-approve 0.8

The resume importer extracts:

• Identity: Name, role, years of experience
• Experience: Work history with companies, roles, dates
• Education: Degrees, institutions, graduation years
• Tech Stack: Programming languages, frameworks, tools
• Projects: Personal and open-source projects
• Publications: Papers, patents, articles

Skills Management

Manage Anthropic-format skills with full bundling support:

# Import skills from Anthropic skills directorytilde skills import /path/to/skills
# Import specific skills by nametilde skills import /path/to/skills -n mcp-builder -n pdf
# Dry run to preview importtilde skills import ./skills --dry-run
# Import as private skillstilde skills import ./skills --visibility private
# List all imported skillstilde skills list
# Export skills to Anthropic formattilde skills export ./my-skills
# Export specific skilltilde skills export ./output -n mcp-builder
# Delete skillstilde skills delete skill-nametilde skills delete --all --force

The skill importer bundles:

• SKILL.md: Skill content with YAML frontmatter
• scripts/: Python scripts and utilities
• references/: Documentation files
• templates/: Template files
• assets/: Static assets
• Root files: LICENSE.txt, etc.

All bundled resources are preserved through import → persist → export.

Team Management

# Create a teamtilde team create myteam --name "My Startup" --org "ACME Corp"
# Activate team context (applies to all profile queries)tilde team activate myteam
# Sync team config from URL or git repotilde team sync https://example.com/team.json --activatetilde team sync [email protected]:myorg/team-config.git --activate
# List and manage teamstilde team listtilde team showtilde team edittilde team deactivate

Storage Backends

tilde supports multiple storage backends:

# Use SQLite backendexport TILDE_STORAGE=sqlitetilde init
# Query profile fields (SQLite only)uv run python -c "from tilde.storage import get_storagestorage = get_storage(backend='sqlite')print(storage.query('%languages%'))"

Configuration

tilde uses a centralized configuration for LLM and embedding settings. Configuration is stored in ~/.tilde/config.yaml and can be synced across devices.

Configuration Priority

1. Environment variables (highest priority)
2. Config file (~/.tilde/config.yaml)
3. Built-in defaults (lowest priority)

Environment Variables

Managing Configuration

# View current configurationtilde config
# Save settings to config file (for syncing across devices)tilde config --save
# Modify a setting and savetilde config --set llm_model=gemini-1.5-pro
# Show config file pathtilde config --path

Note: API keys are NEVER saved to the config file for security. Always set them via environment variables.

Quick Setup

# Minimal setup (just one API key!)export GOOGLE_API_KEY="your-google-api-key"
# Save your settings for this devicetilde config --save
# Now you can use all featurestilde ingest paper.pdf

Syncing Across Devices

The config file at ~/.tilde/config.yaml is designed to be synced:

1. Via dotfiles repo: Add ~/.tilde/ to your dotfiles
2. Via cloud sync: Dropbox, iCloud, or similar
3. Manually: Copy the file to new devices

Example config file:

llm_model: gemini-3-flash-previewllm_temperature: 0.7embedding_model: gemini-embedding-001embedding_dimensions: 768storage_backend: yaml

Programmatic Configuration

from tilde.config import get_config, call_llm, get_embedding, save_config
# Check current configconfig = get_config()print(f"Provider: {config.provider}")print(f"LLM Model: {config.llm_model}")
# Use directlyresponse = call_llm("Summarize this document...")embedding = get_embedding("Some text to embed")

Roadmap

• Phase 1: MVP with profile reading
• Phase 2: Agent-proposed updates with approval flow
• Phase 3: Document ingestion (books, PDFs)
• Phase 4: Team sync for B2B use cases
• Phase 5: SQLite and Mem0 storage backends
• Phase 6: Skill Management (Anthropic SKILL.md format)
  • Batch import from directory with tilde skills import
  • Export to directory with tilde skills export
  • Full bundling of scripts, references, templates, assets
  • Deduplication by skill name

Why "tilde"?

In Unix, ~ (tilde) represents your home directory — the place where your personal configuration lives. tilde is the home for your AI identity.

Philosophy

1. Your Data, Your Control: Local by default, sync only if you choose
2. Human-in-the-Loop: Agents propose, humans decide
3. Portable & Open: Export anytime, no lock-in, works with any MCP tool
4. Progressive Disclosure: Start simple, add complexity as needed

License

MIT

Configure once. Use everywhere. Your data, your control.