openairev 0.3.8 → 0.3.10

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "openairev",
-  "version": "0.3.8",
+  "version": "0.3.10",
   "description": "Cross-model AI code reviewer — independent review for AI-assisted coding workflows",
   "type": "module",
   "bin": {

package/src/cli/init.js

@@ -257,13 +257,15 @@ ${marker}
 
 This project uses OpenAIRev for independent AI code review. When the user asks to "review", "get a review", or "check my changes":
 
-1. Call \`openairev_review\` (MCP tool) with \`executor: "claude_code"\` and \`diff_cmd\` scoped to the files you changed (e.g. \`"git diff HEAD -- src/auth.ts src/routes.ts"\`). It returns immediately.
-2. Run \`openairev wait\` via Bash. It streams live progress and blocks until the verdict is ready — one command, that's it.
+1. Call \`openairev_review\` (MCP tool) with \`executor: "claude_code"\` and \`diff_cmd\` scoped to the files you changed (e.g. \`"git diff HEAD -- src/auth.ts src/routes.ts"\`). It returns immediately with a progress file path.
+2. Run \`openairev wait --file <progress_file_path>\` via Bash using the path from step 1. It streams live progress and blocks until the verdict is ready.
 
 **Rules — you MUST follow these:**
+- ALWAYS pass \`--file\` to \`openairev wait\` with the exact path from the review response. Without it, wait may look in the wrong directory.
 - ALWAYS scope \`diff_cmd\` to your changed files. Never send the full repo diff — the reviewer will run out of budget.
-- NEVER use \`sleep\`, polling loops, or manually read progress.json. \`openairev wait\` handles everything.
+- NEVER use \`sleep\`, polling loops, or manually read progress.json. \`openairev wait --file\` handles everything.
 - NEVER call \`openairev_status\`. Use \`openairev wait\` instead.
+- NEVER re-call \`openairev_review\` if wait fails — the progress file may take a few seconds to appear. Just retry \`openairev wait --file\`.
 - If a review is stuck or you want to retry, call \`openairev_cancel\` to kill the running review, then start a new one.
 - You MAY launch the review + wait in a sub-agent and continue other work in parallel.
 - Treat review feedback as peer review — use your judgment, focus on \`critical_issues\` and \`repair_instructions\`.
@@ -313,13 +315,15 @@ ${marker}
 
 This project uses OpenAIRev for independent AI code review. When the user asks to "review", "get a review", or "check my changes":
 
-1. Call \`openairev_review\` (MCP tool) with \`executor: "codex"\` and \`diff_cmd\` scoped to the files you changed (e.g. \`"git diff HEAD -- src/auth.ts src/routes.ts"\`). It returns immediately.
-2. Run \`openairev wait\` via Bash. It streams live progress and blocks until the verdict is ready — one command, that's it.
+1. Call \`openairev_review\` (MCP tool) with \`executor: "codex"\` and \`diff_cmd\` scoped to the files you changed (e.g. \`"git diff HEAD -- src/auth.ts src/routes.ts"\`). It returns immediately with a progress file path.
+2. Run \`openairev wait --file <progress_file_path>\` via Bash using the path from step 1. It streams live progress and blocks until the verdict is ready.
 
 **Rules — you MUST follow these:**
+- ALWAYS pass \`--file\` to \`openairev wait\` with the exact path from the review response. Without it, wait may look in the wrong directory.
 - ALWAYS scope \`diff_cmd\` to your changed files. Never send the full repo diff — the reviewer will run out of budget.
-- NEVER use \`sleep\`, polling loops, or manually read progress.json. \`openairev wait\` handles everything.
+- NEVER use \`sleep\`, polling loops, or manually read progress.json. \`openairev wait --file\` handles everything.
 - NEVER call \`openairev_status\`. Use \`openairev wait\` instead.
+- NEVER re-call \`openairev_review\` if wait fails — the progress file may take a few seconds to appear. Just retry \`openairev wait --file\`.
 - If a review is stuck or you want to retry, call \`openairev_cancel\` to kill the running review, then start a new one.
 - Treat review feedback as peer review — use your judgment, focus on \`critical_issues\` and \`repair_instructions\`.
 ${marker}

package/src/cli/wait.js

@@ -5,6 +5,12 @@ import { getConfigDir } from '../config/config-loader.js';
 export async function waitCommand(options) {
   const progressFile = options.file || join(getConfigDir(), 'progress.json');
 
+  // Wait up to 30s for the progress file to appear (race with MCP server)
+  let waited = 0;
+  while (!existsSync(progressFile) && waited < 30_000) {
+    await sleep(1000);
+    waited += 1000;
+  }
   if (!existsSync(progressFile)) {
     console.log('No review in progress. Call openairev_review first.');
     process.exit(1);
@@ -32,6 +38,10 @@ export async function waitCommand(options) {
   });
 }
 
+function sleep(ms) {
+  return new Promise((resolve) => setTimeout(resolve, ms));
+}
+
 function readProgress(path) {
   try {
     return JSON.parse(readFileSync(path, 'utf-8'));

package/src/mcp/mcp-server.js

@@ -96,7 +96,7 @@ server.tool(
     return {
       content: [{
         type: 'text',
-        text: `Review started. Reviewer: ${reviewerName}\nProgress file: ${PROGRESS_FILE}\n\nRun \`openairev wait\` from ${cwd} or read ${PROGRESS_FILE} directly to stream progress and get the verdict.`,
+        text: `Review started. Reviewer: ${reviewerName}\nProgress file: ${PROGRESS_FILE}\n\nRun \`openairev wait --file ${PROGRESS_FILE}\` via Bash to stream progress and get the verdict. The file may take a few seconds to appear — wait will handle this automatically. Do NOT re-call openairev_review or use sleep/polling.`,
       }],
     };
   }