Quickstart

In 5 minutes, create an account, sync your sessions with our CLI, and start building your knowledge graph.

Step 1: Create an Account

1. Go to app.dexicon.ai
2. Sign up for an account and provision an API key

Step 2: Install Dexicon CLI

Install the Dexicon CLI to automatically sync your AI coding sessions from Claude Code, Cursor, Codex, VS Code, and GitHub Copilot.

Using curl (macOS/Linux):

curl -sSL https://raw.githubusercontent.com/Dexicon-AI/get-dexicon-cli/main/install.sh | sh

Using Homebrew (macOS/Linux):

brew install Dexicon-AI/tap/dexicon

Using PowerShell (Windows):

irm https://raw.githubusercontent.com/Dexicon-AI/get-dexicon-cli/main/install.ps1 | iex

Step 3: Sync Your AI Coding Sessions

1. Discover agent session logs and login:

dexicon init
dexicon login

2. Sync your past 30 days of agent sessions in that folder:

cd ~/git-repo-to-sync
dexicon sync

Our CLI tracks what sessions are uploaded so it will automatically skip uploaded sessions on subsequent dexicon sync.

Step 4: Connect Dexicon MCP to Your Coding Agent

Connect Dexicon's MCP server to give your AI coding agent access to your knowledge base.

We support any MCP-compatible IDE or CLI including Cursor, Claude Code, VS Code, GitHub Copilot, Codex, Windsurf, Gemini CLI.

See the MCP Server documentation for setup instructions for your specific agent.

Step 5: Explore Your Knowledge

Once your sessions are synced, you can immediately start interacting with your knowledge graph via the web app or through your AI coding agent.

Via the Dexicon Web App

• Chat - Ask questions about your codebase and past work
• Search - Find sessions by natural language query
• Knowledge Base - Browse your distilled knowledge graph
• Sessions - View all synced coding sessions

Via Your Coding Agent (MCP)

Once you've connected the Dexicon MCP (Step 4), your AI assistant can search your knowledge directly:

• "Search Dexicon for how I handled API rate limiting"
• "What did I do last week?"
• "Find my previous sessions about database schema design"

Step 6: Configure Your Agent (Recommended)

AI agents won't search Dexicon unless prompted. Add the following rules to your agent's configuration file (.cursorrules, CLAUDE.md, .github/copilot-instructions.md, etc.) to teach them when to proactively check your engineering context.

## Dexicon Context Search

**Search proactively, not reactively.** Check Dexicon before implementing—prior context prevents duplicate work.

### When to Search

- Before implementing features or fixes
- When debugging errors (especially API/integration failures)
- For "why did we...?" or "how should we...?" questions
- When uncertain about team patterns or conventions
- When investigating build/test failures

### Choose Your Approach

| Situation | Tool | Example |
|-----------|------|---------|
| Fuzzy/conceptual query | `search` | "redis caching bug", "auth flow" |
| Know the topic/category | `list_work_topics` → `get_work_by_topic` | "show me debugging sessions" |
| Recent work / "what was I doing?" | `get_recent_work` | chronological browsing |
| Scope to a codebase | `list_projects` → `search` with `project_id` | filter to specific repo |

### Common Queries

| User asks... | Approach |
|--------------|----------|
| "What did I do last week/recently?" | `get_recent_work(scope="me", lookback_days=7)` |
| "What has the team done with Stripe?" | `search("Stripe")` or `list_work_topics()` → `get_work_by_topic("stripe")` |
| "What have I worked on with Supabase?" | `search("Supabase", scope="me")` or `get_work_by_topic("supabase", scope="me")` |
| "Show me recent API work" | `list_work_topics()` → `get_work_by_topic("api")` |
| "What was I doing on project X?" | `list_projects()` → `get_recent_work(project_id=...)` |

### Workflows

**Search → Deep Dive:**

    search("query") → get_document(document_id)  # for uploaded docs
    search("query") → get_session(session_id)    # for conversations

**Browse by Topic:**

    list_work_topics() → get_work_by_topic(tag) → get_session(session_id)

### Filtering Options

- `scope="me"` - Only your sessions
- `scope="team"` - Everyone in the org (default)
- `lookback_days` - How far back to look (1-90 days, default 30)
- `project_id` - Scope to a specific codebase

### Query Tips

- Be specific: "PostgreSQL connection pooling" not "database stuff"
- Include error messages: "ECONNREFUSED 5432"
- Reference paths: "auth/oauth_handler.py retry logic"
- Multi-hop when needed: search the "what", then the "why"

### Don't Search For

- Basic language syntax or standard library usage
- General programming concepts (unless asking about *our* approach)
- Brand new features with no prior history

### When Searches Fail

- Broaden terms first, then narrow
- Try related components or similar patterns
- If a summary is incomplete, use `get_document` or `get_session` for full content
- Ask user if this is genuinely new territory

CLI Tips

At the end of each working day, run from each folder you worked in:

dexicon sync

Autosync (Beta): The Dexicon CLI has a beta feature for automatic syncing that can be enabled via dexicon schedule enable. See the CLI Reference for more details.

When CLI updates are needed:

brew upgrade dexicon