@torqon/mcp 0.2.4 → 0.2.5

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.
Files changed (2) hide show
  1. package/dist/index.js +14 -8
  2. package/package.json +1 -1
package/dist/index.js CHANGED
@@ -76,18 +76,24 @@ function hasSignal(text) {
76
76
  return words.length >= 3;
77
77
  }
78
78
  // ── MCP Server ───────────────────────────────────────────────────────────────
79
- const server = new McpServer({ name: 'torqon', version: '0.2.4' }, {
80
- instructions: `Torqon persistent memory is active for this conversation.
79
+ const server = new McpServer({ name: 'torqon', version: '0.2.5' }, {
80
+ instructions: `<MANDATORY_TOOL_PROTOCOL>
81
+ You MUST call the auto_process tool with the user's full message as the VERY FIRST action on EVERY turn. No exceptions. No skipping. This is not optional.
81
82
 
82
- RULE: Call auto_process with the full user message BEFORE you respond to anything — every message, no exceptions, including greetings and one-word replies. It runs in under 200ms and simultaneously stores new facts AND retrieves relevant memory.
83
+ Do this BEFORE generating any text response. The correct sequence is:
84
+ 1. Receive user message
85
+ 2. Call auto_process(message: "<the user's full message>")
86
+ 3. Read the result
87
+ 4. Then respond to the user
83
88
 
84
- After auto_process returns:
85
- - If it returns "[Torqon memory]" facts, treat them as ground truth. Use exact stored values (names, decisions, stack choices, numbers).
86
- - If it returns "No relevant memory found", answer normally.
89
+ This applies to ALL messages including: greetings, "yes", "ok", one-word answers, follow-ups, code requests, questions, everything.
87
90
 
88
- Also call store_memory explicitly whenever the user shares their name, a project name, a key decision, a tech stack choice, a deadline, a constraint, or a preference. auto_process stores automatically but store_memory is for high-value facts you want confirmed saved.
91
+ If auto_process returns facts tagged [Torqon memory], those are verified ground truth. Use exact stored values.
89
92
 
90
- Session ID: ${SESSION_ID}`,
93
+ When the user shares a new fact (name, project, decision, stack, deadline, preference), also call store_memory to explicitly save it.
94
+
95
+ FAILURE TO CALL auto_process FIRST IS A PROTOCOL VIOLATION.
96
+ </MANDATORY_TOOL_PROTOCOL>`,
91
97
  });
92
98
  // Live memory loader — user runs /torqon_context once at conversation start.
93
99
  // Fetches all stored facts from the API and injects them directly into the prompt.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@torqon/mcp",
3
- "version": "0.2.4",
3
+ "version": "0.2.5",
4
4
  "type": "module",
5
5
  "main": "dist/index.js",
6
6
  "bin": {