@triedotdev/mcp 1.0.3 → 1.0.4

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -116,8 +116,61 @@ Use trie_scan to analyze the current file
116
116
  - **`trie_fix`** - Apply high-confidence fixes automatically
117
117
  - **`trie_explain`** - Get plain-language explanations of code/issues
118
118
  - **`trie_test`** - Generate tests or check coverage
119
- - **`trie_commit`** - Create smart commit messages
120
- - **`trie_register_agent`** - Add custom agents
119
+ - **`trie_watch`** - Watch mode for continuous scanning
120
+ - **`trie_security`**, **`trie_privacy`**, **`trie_bugs`**, etc. - Run specific agents
121
+
122
+ ### Custom Agent Tools
123
+
124
+ - **`trie_create_agent`** - Create a custom agent from a document (PDF, TXT, MD)
125
+ - **`trie_save_agent`** - Save agent config after extraction
126
+ - **`trie_list_agents`** - List all registered agents (built-in and custom)
127
+
128
+ ## Custom Agents
129
+
130
+ Create specialized code review agents from any document—style guides, compliance docs, framework best practices, etc.
131
+
132
+ ### Creating a Custom Agent
133
+
134
+ ```
135
+ Use trie_create_agent with filePath:"./react-handbook.pdf" agentName:"react-handbook"
136
+ ```
137
+
138
+ Or paste content directly:
139
+ ```
140
+ Use trie_create_agent with agentName:"my-style-guide" documentContent:"[paste your style guide here]"
141
+ ```
142
+
143
+ The tool will parse the document and prompt you to extract knowledge. Then use `trie_save_agent` to save it.
144
+
145
+ ### Listing Custom Agents
146
+
147
+ ```
148
+ Use trie_list_agents
149
+ ```
150
+
151
+ This shows all built-in and custom agents with their pattern counts and categories.
152
+
153
+ ### Using a Custom Agent
154
+
155
+ Custom agents automatically activate during `trie_scan` based on their activation rules. To force a specific custom agent:
156
+
157
+ ```
158
+ Use trie_scan with forceAgents:["react-handbook"]
159
+ ```
160
+
161
+ ### Removing a Custom Agent
162
+
163
+ Custom agents are stored as JSON files in your project's `.trie/agents/` directory. To remove one:
164
+
165
+ ```bash
166
+ # List custom agents
167
+ ls .trie/agents/
168
+
169
+ # Remove a specific agent
170
+ rm .trie/agents/react-handbook.json
171
+ ```
172
+
173
+ The agent will no longer be loaded on subsequent scans.
121
174
 
122
175
  ## MCP Resources
123
176
 
@@ -6270,6 +6270,16 @@ var TrieScanTool = class {
6270
6270
  agentRegistry = new AgentRegistry();
6271
6271
  incrementalScanner = null;
6272
6272
  progress = new ProgressReporter();
6273
+ customAgentsLoaded = false;
6274
+ /**
6275
+ * Ensure custom agents are loaded before using the registry
6276
+ */
6277
+ async ensureCustomAgentsLoaded() {
6278
+ if (!this.customAgentsLoaded) {
6279
+ await this.agentRegistry.loadCustomAgents();
6280
+ this.customAgentsLoaded = true;
6281
+ }
6282
+ }
6273
6283
  async execute(args) {
6274
6284
  const startTime = Date.now();
6275
6285
  try {
@@ -6328,6 +6338,7 @@ var TrieScanTool = class {
6328
6338
  const riskLevel = this.riskAssessor.assessRisk(context);
6329
6339
  this.logRiskAssessment(context, riskLevel);
6330
6340
  this.progress.startPhase("ai-review", "Selecting AI agents...");
6341
+ await this.ensureCustomAgentsLoaded();
6331
6342
  const selectedAgents = forceAgents ? this.agentRegistry.getAgentsByNames(forceAgents) : await this.triager.selectAgents(context, riskLevel);
6332
6343
  const allAgentNames = this.agentRegistry.getAgentNames();
6333
6344
  this.logTriaging(selectedAgents.map((a) => a.name), allAgentNames, context, riskLevel);
@@ -7612,4 +7623,4 @@ export {
7612
7623
  getSystemPrompt,
7613
7624
  TrieFixTool
7614
7625
  };
7615
- //# sourceMappingURL=chunk-E7CKHS3R.js.map
7626
+ //# sourceMappingURL=chunk-6INDJQPJ.js.map