@triedotdev/mcp 1.0.39 → 1.0.41

package/README.md

@@ -1,8 +1,8 @@
 # Trie
 
-**Customizable Parallel Agents for AI Code Review**
+**A central registry for agents that follow you from Cursor to CI/CD and everything in between.**
 
-Specialized agents scan your code for security, privacy, compliance, and bugs—all running in parallel with intelligent caching and real-time streaming.
+Download the Trie workspace: https://www.trie.dev
 
 ## Why Trie
 
@@ -12,6 +12,8 @@ The last mile of shipping is where things break—not because your code doesn't
 
 ## What's New (latest updates)
 
+- **Project Info Registry**: Store important project context in `.trie/PROJECT.md` that travels with you across Claude Code, Cursor, GitHub Actions, and CLI. Define your project description, tech stack, conventions, architecture, and custom AI instructions—all in one place.
+
 - **Accessibility Agent (v2.0)**: Comprehensive WCAG 2.1 AA compliance. Detects icon-only buttons, touch targets, skipped headings, positive tabIndex, ARIA validation, color-only indicators, and 20+ more checks with WCAG criterion references.
 
 - **Health Score Triaging**: Your health score (0-100) now actively controls what agents run. Below 50%? All agents run automatically. Agents that found issues before get boosted priority in future scans.
@@ -36,6 +38,7 @@ The last mile of shipping is where things break—not because your code doesn't
 - [Design Engineer (v2.0)](#design-engineer-v20)
 - [Special Agents](#special-agents)
 - [Custom Agents](#custom-agents)
+- [Project Info Registry](#project-info-registry)
 - [AI-Enhanced Mode](#ai-enhanced-mode)
 - [CI/CD Integration](#cicd-integration)
 - [VS Code Extension](#vs-code-extension)
@@ -386,6 +389,7 @@ These tools are available when using Trie via MCP (Cursor, Claude Code, etc.).
 | `trie_watch` | Watch mode—automatically scan files as you code |
 | `trie_fix` | Generate fix recommendations for detected issues |
 | `trie_explain` | Explain code, issues, or changes in plain language |
+| `trie_project` | View and manage project info (.trie/PROJECT.md) |
 
 ### Custom Agent Tools
 
@@ -943,6 +947,141 @@ Custom agents are stored in `.trie/agents/` in your project directory.
 
 ---
 
+## Project Info Registry
+
+Store important project-specific information in `.trie/PROJECT.md` that's automatically available to all AI tools.
+
+### Why Project Info?
+
+When you work across multiple tools (Cursor, Claude Code, GitHub Actions, CLI), context gets lost. The Project Info Registry solves this by providing a single source of truth for:
+
+- Project description and purpose
+- Technology stack and frameworks
+- Architecture decisions and patterns
+- Coding conventions and style guidelines
+- Environment info (URLs, API endpoints)
+- Team ownership and contacts
+- Compliance requirements
+- Custom instructions for AI assistants
+
+### Create PROJECT.md
+
+**Using CLI:**
+```bash
+trie-agent project init
+```
+
+**Using MCP (Cursor/Claude Code):**
+```
+trie_project action="init"
+```
+
+This creates a template at `.trie/PROJECT.md` with sections ready to fill in.
+
+### View Project Info
+
+**CLI:**
+```bash
+trie-agent project
+```
+
+**MCP:**
+```
+trie_project action="view"
+```
+
+**MCP Resource:**
+```
+Read trie://project
+```
+
+### Update Sections
+
+**MCP:**
+```
+trie_project action="update" section="Technology Stack" content="- **Language:** TypeScript\n- **Framework:** Next.js 14\n- **Database:** PostgreSQL"
+```
+
+### How It Works
+
+```
+your-project/
+├── .trie/
+│   └── PROJECT.md    ← Your project context
+├── src/
+└── package.json
+```
+
+The PROJECT.md file is:
+- **Committed to git** — context travels with your code
+- **Available via `trie://project`** — AI tools can read it directly
+- **Integrated into `trie://context`** — included in overall project context
+- **Per-project** — each project has its own file
+
+### Template Sections
+
+| Section | What to Include |
+|---------|-----------------|
+| **Project Overview** | What does this project do? Who is it for? |
+| **Technology Stack** | Languages, frameworks, databases, cloud services |
+| **Architecture** | Key patterns, system design, important decisions |
+| **Coding Conventions** | Style rules, naming conventions, patterns to follow |
+| **Environment** | Dev/staging/prod URLs, API endpoints |
+| **Team** | Who owns what, contact info |
+| **Compliance** | GDPR, SOC2, HIPAA requirements |
+| **AI Instructions** | Special instructions for AI assistants |
+
+### Example PROJECT.md
+
+```markdown
+## Project Overview
+
+E-commerce platform for sustainable products. 
+Focus on fast checkout and mobile-first UX.
+
+## Technology Stack
+
+- **Language:** TypeScript
+- **Framework:** Next.js 14 (App Router)
+- **Database:** PostgreSQL with Prisma ORM
+- **Hosting:** Vercel + Supabase
+
+## Architecture
+
+- Server Components by default, Client Components only when needed
+- tRPC for type-safe API calls
+- Zustand for client state
+
+## Coding Conventions
+
+- Use `pnpm` for package management
+- Prefer named exports over default exports
+- Use Tailwind CSS, no inline styles
+- Tests required for payment-related code
+
+## AI Instructions
+
+When working on this project:
+1. Always use Server Components unless client interactivity is needed
+2. Check for accessibility issues (we target WCAG AA)
+3. Payment code must be reviewed by security agent before commit
+```
+
+### Multi-Project Support
+
+Each project has its own `.trie/PROJECT.md`:
+
+```
+~/projects/
+├── project-a/.trie/PROJECT.md  ← Project A's context
+├── project-b/.trie/PROJECT.md  ← Project B's context  
+└── project-c/.trie/PROJECT.md  ← Project C's context
+```
+
+When you open Project A in Cursor, it reads Project A's context. Switch to Project B, and it reads Project B's context. No configuration needed.
+
+---
+
 ## AI-Enhanced Mode
 
 Trie works in two modes:
@@ -1091,14 +1230,16 @@ Trie auto-detects your project root by looking for `package.json`, `.git`, `Carg
 <summary>MCP Resources (click to expand)</summary>
 
 ```
-trie://context        # AGENTS.md content (read this first)
+trie://context        # Combined context (PROJECT.md + scan results)
+trie://project        # User-defined project info (PROJECT.md)
 trie://context/state  # Detailed JSON state
 trie://agents         # Available agents
 trie://config         # Current configuration
 ```
 
 Files stored:
-- `.trie/AGENTS.md` - Human-readable context
+- `.trie/PROJECT.md` - User-defined project context (description, stack, conventions, AI instructions)
+- `.trie/AGENTS.md` - Auto-generated scan context
 - `.trie/state.json` - Machine-readable state for programmatic access
 
 </details>

package/dist/{chunk-HG5AWUH7.js → chunk-G2GNVUMP.js}

@@ -1,3 +1,7 @@
+import {
+  loadProjectInfo,
+  projectInfoExists
+} from "./chunk-Q4RVENDE.js";
 import {
   CustomAgent,
   getAgentRegistry
@@ -974,8 +978,19 @@ _Run a scan to identify hot files._
 }
 async function getContextForAI() {
   const state = await loadContextState();
-  const lines = [
-    "## Trie Context Summary",
+  const workDir = getWorkingDirectory(void 0, true);
+  const lines = [];
+  if (projectInfoExists(workDir)) {
+    const projectInfo = await loadProjectInfo(workDir);
+    if (projectInfo) {
+      lines.push(projectInfo);
+      lines.push("");
+      lines.push("---");
+      lines.push("");
+    }
+  }
+  lines.push(
+    "## Trie Scan Context",
     "",
     `**Health Score:** ${state.healthScore}%`,
     `**Last Scan:** ${state.lastScan ? new Date(state.lastScan.timestamp).toLocaleString() : "Never"}`,
@@ -983,7 +998,7 @@ async function getContextForAI() {
     "**Active Priorities:**",
     ...state.activePriorities.map((p) => `- ${p}`),
     ""
-  ];
+  );
   if (state.lastScan) {
     lines.push(
       "**Recent Issues:**",
@@ -6912,4 +6927,4 @@ export {
   getContextForAI,
   TrieScanTool
 };
-//# sourceMappingURL=chunk-HG5AWUH7.js.map
+//# sourceMappingURL=chunk-G2GNVUMP.js.map