memorix 0.9.28 → 0.9.29

package/dist/cli/index.js

@@ -40651,7 +40651,9 @@ function generateGeminiConfig() {
     };
   }
   return {
+    tools: { enableHooks: true },
     hooks: {
+      enabled: true,
       SessionStart: [entry("memorix-session-start", "Load memorix context at session start")],
       AfterTool: [entry("memorix-after-tool", "Record tool usage in memorix")],
       AfterAgent: [entry("memorix-after-agent", "Record agent response in memorix")],
@@ -40878,6 +40880,10 @@ async function installHooks(agent, projectRoot, global = false) {
       const existingHooks = existing.hooks && typeof existing.hooks === "object" ? existing.hooks : {};
       merged.hooks = { ...existingHooks, ...gen.hooks };
     }
+    if (gen.tools && typeof gen.tools === "object") {
+      const existingTools = existing.tools && typeof existing.tools === "object" ? existing.tools : {};
+      merged.tools = { ...existingTools, ...gen.tools };
+    }
     await fs5.writeFile(configPath, JSON.stringify(merged, null, 2), "utf-8");
   }
   const events = [];
@@ -40930,7 +40936,7 @@ async function installAgentRules(agent, projectRoot) {
       rulesPath = path7.join(projectRoot, ".kiro", "steering", "memorix.md");
       break;
     case "antigravity":
-      rulesPath = path7.join(projectRoot, ".gemini", "rules", "memorix.md");
+      rulesPath = path7.join(projectRoot, "GEMINI.md");
       break;
     default:
       rulesPath = path7.join(projectRoot, ".agent", "rules", "memorix.md");
@@ -40938,7 +40944,7 @@ async function installAgentRules(agent, projectRoot) {
   }
   try {
     await fs5.mkdir(path7.dirname(rulesPath), { recursive: true });
-    if (agent === "codex") {
+    if (agent === "codex" || agent === "antigravity") {
       try {
         const existing = await fs5.readFile(rulesPath, "utf-8");
         if (existing.includes("Memorix")) {
@@ -40976,58 +40982,42 @@ alwaysApply: true
   }
   return `${frontmatter}# Memorix \u2014 Automatic Memory Rules
 
-You have access to Memorix memory tools. Follow these rules to maintain persistent context across sessions.
+You have access to Memorix memory tools. You MUST follow these rules to maintain persistent context across sessions.
+These rules are NOT optional \u2014 they are critical for cross-session memory continuity.
 
-## Session Start \u2014 Load Context
+## RULE 1: Session Start \u2014 Load Context (MUST)
 
-At the **beginning of every conversation**, before responding to the user:
+At the **beginning of every conversation**, BEFORE responding to the user:
 
 1. Call \`memorix_search\` with a query related to the user's first message or the current project
 2. If results are found, use \`memorix_detail\` to fetch the most relevant ones
-3. Reference relevant memories naturally in your response \u2014 the user should feel you "remember" them
-
-This ensures you already know the project context without the user re-explaining.
-
-## During Session \u2014 Capture Important Context
+3. Reference relevant memories naturally in your response
 
-**Proactively** call \`memorix_store\` whenever any of the following happen:
+> **CRITICAL**: Do NOT skip this step. The user expects you to "remember" previous sessions.
 
-### Architecture & Decisions
-- Technology choice, framework selection, or design pattern adopted
-- Trade-off discussion with a clear conclusion
-- API design, database schema, or project structure decisions
+## RULE 2: After Every Action \u2014 Check & Record (MUST)
 
-### Bug Fixes & Problem Solving
-- A bug is identified and resolved \u2014 store root cause + fix
-- Workaround applied for a known issue
-- Performance issue diagnosed and optimized
+After EVERY tool call that modifies state (file create/edit, shell command, config change), run this checklist:
 
-### Gotchas & Pitfalls
-- Something unexpected or tricky is discovered
-- A common mistake is identified and corrected
-- Platform-specific behavior that caused issues
+**Ask yourself: "Would a different AI agent need to know about this?"**
+- If YES \u2192 call \`memorix_store\` IMMEDIATELY, BEFORE replying to the user
+- If NO \u2192 skip (e.g., simple file reads, ls/dir, greetings)
 
-### Configuration & Environment
-- Environment variables, port numbers, paths changed
-- Docker, nginx, Caddy, or reverse proxy config modified
-- Package dependencies added, removed, or version-pinned
+### What MUST be recorded:
+- \u2705 File created or significantly modified \u2192 type: \`what-changed\`
+- \u2705 Bug identified and fixed \u2192 type: \`problem-solution\`
+- \u2705 Architecture or design decision made \u2192 type: \`decision\`
+- \u2705 Unexpected behavior or gotcha discovered \u2192 type: \`gotcha\`
+- \u2705 Configuration changed (env vars, ports, deps) \u2192 type: \`what-changed\`
+- \u2705 Feature completed or milestone reached \u2192 type: \`what-changed\`
+- \u2705 Trade-off discussed with conclusion \u2192 type: \`trade-off\`
 
-### Deployment & Operations
-- Server deployment steps (Docker, VPS, cloud)
-- DNS, SSL/TLS certificate, domain configuration
-- CI/CD pipeline setup or changes
-- Database migration or data transfer procedures
-- Server topology (ports, services, reverse proxy chain)
-- SSH keys, access credentials setup (store pattern, NOT secrets)
+### What should NOT be recorded:
+- \u274C Simple file reads without findings
+- \u274C Greetings, acknowledgments
+- \u274C Trivial commands (ls, pwd, git status with no issues)
 
-### Project Milestones
-- Feature completed or shipped
-- Version released or published to npm/PyPI/etc.
-- Repository made public, README updated, PR submitted
-
-Use appropriate types: \`decision\`, \`problem-solution\`, \`gotcha\`, \`what-changed\`, \`discovery\`, \`how-it-works\`.
-
-## Session End \u2014 Store Summary
+## RULE 3: Session End \u2014 Store Summary (MUST)
 
 When the conversation is ending or the user says goodbye:
 
@@ -41041,13 +41031,12 @@ This creates a "handoff note" for the next session (or for another AI agent).
 
 ## Guidelines
 
-- **Don't store trivial information** (greetings, acknowledgments, simple file reads, ls/dir output)
-- **Do store anything you'd want to know if you lost all context**
-- **Do store anything a different AI agent would need to continue this work**
 - **Use concise titles** (~5-10 words) and structured facts
 - **Include file paths** in filesModified when relevant
 - **Include related concepts** for better searchability
 - **Prefer storing too much over too little** \u2014 the retention system will auto-decay stale memories
+
+Use types: \`decision\`, \`problem-solution\`, \`gotcha\`, \`what-changed\`, \`discovery\`, \`how-it-works\`, \`trade-off\`.
 `;
 }
 async function uninstallHooks(agent, projectRoot, global = false) {