@rawwee/interactive-mcp 1.1.0 → 1.2.0

package/README.md

@@ -131,11 +131,10 @@ This section is primarily for developers looking to modify or contribute to the
 bun run start
 ```
 
-### Terminal UI backend status
+### UI backend status
 
-`interactive-mcp` now uses OpenTUI (`@opentui/core`, `@opentui/react`) for terminal UI rendering.
-
-OpenTUI is the terminal UI renderer backend.
+`interactive-mcp` currently runs with the OpenTUI terminal backend (`@opentui/core`, `@opentui/react`).
+The VS Code extension and bridge runtime have been removed from the active feature set for now, and may be reconsidered in a future iteration.
 
 #### Command-Line Options
 
@@ -143,7 +142,7 @@ The `interactive-mcp` server accepts the following command-line options. These s
 
 | Option            | Alias | Description                                                                                                                                                                                           |
 | ----------------- | ----- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `--timeout`       | `-t`  | Sets the default timeout (in seconds) for user input prompts. Defaults to 30 seconds.                                                                                                                 |
+| `--timeout`       | `-t`  | Sets the default timeout (in seconds) for user input prompts.                                                                                                                                         |
 | `--disable-tools` | `-d`  | Disables specific tools or groups (comma-separated list). Prevents the server from advertising or registering them. Options: `request_user_input`, `message_complete_notification`, `intensive_chat`. |
 
 **Example:** Setting multiple options in the client config `args` array:

package/dist/index.js

@@ -4,8 +4,8 @@ import { StdioServerTransport } from '@modelcontextprotocol/sdk/server/stdio.js'
 import notifier from 'node-notifier';
 import yargs from 'yargs';
 import { hideBin } from 'yargs/helpers';
+import { askQuestionInSession, startIntensiveChatSession, stopIntensiveChatSession, } from './commands/intensive-chat/index.js';
 import { getCmdWindowInput } from './commands/input/index.js';
-import { startIntensiveChatSession, askQuestionInSession, stopIntensiveChatSession, } from './commands/intensive-chat/index.js';
 import { USER_INPUT_TIMEOUT_SECONDS, USER_INPUT_TIMEOUT_SENTINEL, } from './constants.js';
 import logger from './utils/logger.js';
 import { validateRepositoryBaseDirectory } from './utils/base-directory.js';
@@ -158,10 +158,11 @@ if (isToolEnabled('start_intensive_chat')) {
         const { sessionTitle, baseDirectory } = args;
         try {
             const validatedBaseDirectory = await validateRepositoryBaseDirectory(baseDirectory);
-            // Start a new intensive chat session, passing global timeout
             const sessionId = await startIntensiveChatSession(sessionTitle, validatedBaseDirectory, globalTimeoutSeconds);
             // Track this session for the client
-            activeChatSessions.set(sessionId, sessionTitle);
+            activeChatSessions.set(sessionId, {
+                title: sessionTitle,
+            });
             return {
                 content: [
                     {
@@ -200,8 +201,8 @@ if (isToolEnabled('ask_intensive_chat')) {
     async (args) => {
         // Use inferred args type
         const { sessionId, question, predefinedOptions, baseDirectory } = args;
-        // Check if session exists
-        if (!activeChatSessions.has(sessionId)) {
+        const activeSession = activeChatSessions.get(sessionId);
+        if (!activeSession) {
             return {
                 content: [
                     { type: 'text', text: 'Error: Invalid or expired session ID.' },
@@ -210,7 +211,6 @@ if (isToolEnabled('ask_intensive_chat')) {
         }
         try {
             const validatedBaseDirectory = await validateRepositoryBaseDirectory(baseDirectory);
-            // Ask the question in the session
             const answer = await askQuestionInSession(sessionId, question, validatedBaseDirectory, predefinedOptions);
             // Check for the specific timeout indicator
             if (answer === USER_INPUT_TIMEOUT_SENTINEL) {
@@ -279,8 +279,8 @@ if (isToolEnabled('stop_intensive_chat')) {
     async (args) => {
         // Use inferred args type
         const { sessionId } = args;
-        // Check if session exists
-        if (!activeChatSessions.has(sessionId)) {
+        const activeSession = activeChatSessions.get(sessionId);
+        if (!activeSession) {
             return {
                 content: [
                     { type: 'text', text: 'Error: Invalid or expired session ID.' },
@@ -288,7 +288,6 @@ if (isToolEnabled('stop_intensive_chat')) {
             };
         }
         try {
-            // Stop the session
             const success = await stopIntensiveChatSession(sessionId);
             // Remove session from map if successful
             if (success) {

package/dist/tool-definitions/intensive-chat.js

@@ -1,7 +1,7 @@
 import { z } from 'zod';
 // === Start Intensive Chat Definition ===
 const startCapability = {
-    description: 'Start a persistent OpenTUI intensive chat session for gathering multiple answers quickly with markdown-friendly prompts.',
+    description: 'Start a persistent intensive chat session for gathering multiple answers quickly with markdown-friendly prompts.',
     parameters: {
         type: 'object',
         properties: {
@@ -18,17 +18,18 @@ const startCapability = {
     },
 };
 const startDescription = (globalTimeoutSeconds) => `<description>
-Start an intensive chat session (OpenTUI terminal UI) for gathering multiple answers quickly from the user.
+Start an intensive chat session for gathering multiple answers quickly from the user.
 **Highly recommended** for scenarios requiring a sequence of related inputs or confirmations.
 Very useful for gathering multiple answers from the user in a short period of time.
 Especially useful for brainstorming ideas or discussing complex topics with the user.
 </description>
 
 <importantNotes>
-- (!important!) Opens a persistent console window that stays open for multiple questions.
+- (!important!) Opens a persistent interaction session that stays active for multiple questions.
 - (!important!) Returns a session ID that **must** be used for subsequent questions via 'ask_intensive_chat'.
 - (!important!) **Must** be closed with 'stop_intensive_chat' when finished gathering all inputs.
 - (!important!) After starting a session, **immediately** continue asking all necessary questions using 'ask_intensive_chat' within the **same response message**. Do not end the response until the chat is closed with 'stop_intensive_chat'. This creates a seamless conversational flow for the user.
+- (!important!) Continue the prompt loop until the user explicitly says one of: "Stop prompting", "End session", or "Don't ask anymore".
 </importantNotes>
 
 <whenToUseThisTool>
@@ -41,7 +42,7 @@ Especially useful for brainstorming ideas or discussing complex topics with the
 </whenToUseThisTool>
 
 <features>
-- Opens a persistent OpenTUI window for continuous interaction
+- Opens a persistent interactive prompt surface for continuous interaction
 - Renders markdown prompts, including code/diff snippets, for richer question context
 - Preserves markdown links, including VS Code file links (for example: "vscode://file/<abs-path>:<line>:<column>") in prompt content
 - Supports option mode + free-text mode while asking follow-up questions
@@ -49,6 +50,7 @@ Especially useful for brainstorming ideas or discussing complex topics with the
 - Returns a session ID for subsequent interactions
 - Keeps full chat history visible to the user
 - Maintains state between questions
+- Backend-agnostic contract: start/ask/stop behavior is consistent across available UI backends
 - Requires baseDirectory and pins autocomplete/search scope to the repository root
 </features>
 
@@ -85,7 +87,7 @@ const startToolDefinition = {
 };
 // === Ask Intensive Chat Definition ===
 const askCapability = {
-    description: 'Ask a markdown-friendly question in an active OpenTUI intensive chat session.',
+    description: 'Ask a markdown-friendly question in an active intensive chat session.',
     parameters: {
         type: 'object',
         properties: {
@@ -120,6 +122,8 @@ Ask a new question in an active intensive chat session previously started with '
 - (!important!) Supports predefined options for quick selection.
 - (!important!) Returns the user's answer or indicates if they didn't respond.
 - (!important!) **Use this repeatedly within the same response message** after 'start_intensive_chat' until all questions are asked.
+- (!important!) If response is empty or times out for required input, re-prompt and do not proceed with assumptions.
+- (!important!) Keep the loop active until the user explicitly says one of: "Stop prompting", "End session", or "Don't ask anymore".
 </importantNotes>
 
 <whenToUseThisTool>
@@ -193,9 +197,10 @@ const stopDescription = `<description>
 </description>
 
 <importantNotes>
-- (!important!) Closes the console window for the intensive chat.
+- (!important!) Closes the active intensive chat session.
 - (!important!) Frees up system resources.
 - (!important!) **Should always be called** as the final step when finished with an intensive chat session, typically at the end of the response message where 'start_intensive_chat' was called.
+- (!important!) Only stop the session when the user explicitly wants to end prompting, such as with "Stop prompting", "End session", or "Don't ask anymore".
 </importantNotes>
 
 <whenToUseThisTool>
@@ -207,7 +212,7 @@ const stopDescription = `<description>
 </whenToUseThisTool>
 
 <features>
-- Gracefully closes the console window
+- Gracefully closes the active session in the current backend
 - Cleans up system resources
 - Marks the session as complete
 </features>

package/dist/tool-definitions/request-user-input.js

@@ -1,7 +1,7 @@
 import { z } from 'zod';
 // Define capability conforming to ToolCapabilityInfo
 const capabilityInfo = {
-    description: 'Ask the user a question in an OpenTUI terminal prompt with markdown-friendly rendering and await their reply.',
+    description: 'Ask the user a question in an interactive prompt surface and await their reply.',
     parameters: {
         type: 'object',
         properties: {
@@ -29,7 +29,7 @@ const capabilityInfo = {
 };
 // Define description conforming to ToolRegistrationDescription
 const registrationDescription = (globalTimeoutSeconds) => `<description>
-Send a question to the user via the OpenTUI terminal prompt. **Crucial for clarifying requirements, confirming plans, or resolving ambiguity.**
+Send a question to the user via an interactive prompt surface. **Crucial for clarifying requirements, confirming plans, or resolving ambiguity.**
 You should call this tool whenever it has **any** uncertainty or needs clarification or confirmation, even for trivial or silly questions.
 Feel free to ask anything! **Proactive questioning is preferred over making assumptions.**
 </description>
@@ -39,9 +39,15 @@ Feel free to ask anything! **Proactive questioning is preferred over making assu
 - (!important!) Continue to generate existing messages after user answers.
 - (!important!) Provide predefined options for quick selection if applicable.
 - (!important!) **Essential for validating assumptions before proceeding with significant actions (e.g., code edits, running commands).**
+- (!important!) **Do not exit the prompt loop** until the user explicitly says one of: "Stop prompting", "End session", or "Don't ask anymore".
+- (!important!) Immediately before final/closing handoff, ask exactly: "Are you satisfied with this result, or would you like any changes?"
+- (!important!) If a required prompt times out or response is empty, re-prompt indefinitely and do not proceed with assumptions.
+- (!important!) If the user skips a requested command/script, ask why it was skipped and whether to continue with alternatives or stop.
 </importantNotes>
 
 <whenToUseThisTool>
+- Before starting any task, even if requirements appear clear
+- After completing any task, to run the mandatory satisfaction check
 - When you need clarification on user requirements or preferences
 - When multiple implementation approaches are possible and user input is needed
 - **Before making potentially impactful changes (code edits, file operations, complex commands)**
@@ -51,14 +57,19 @@ Feel free to ask anything! **Proactive questioning is preferred over making assu
 - When facing ambiguous instructions that require clarification
 - When seeking feedback on generated code or solutions
 - When needing permission to modify critical files or functionality
+- When user instructions are conflicting or unclear
+- When the user asks to be prompted, asks a direct question, or asks a reply question
+- When the user skips a command you requested
+- Immediately before any final/closing handoff
 - **Whenever you feel even slightly unsure about the user's intent or the correct next step.**
 </whenToUseThisTool>
 
 <features>
-- OpenTUI prompt with markdown rendering (including code/diff blocks)
+- Interactive prompt UI with markdown rendering (including code/diff blocks)
 - Preserves markdown links, including VS Code file links (for example: "vscode://file/<abs-path>:<line>:<column>") when provided in the prompt text
 - Supports option mode + free-text input mode when predefinedOptions are provided
 - Returns user response or timeout notification (timeout defaults to ${globalTimeoutSeconds} seconds)
+- Backend-agnostic contract: same request/response behavior regardless of the active UI backend
 - Maintains context across user interactions
 - Handles empty responses gracefully
 - Shows project context in the prompt header/title

package/package.json

@@ -1,13 +1,19 @@
 {
   "name": "@rawwee/interactive-mcp",
-  "version": "1.1.0",
+  "version": "1.2.0",
   "main": "dist/index.js",
   "type": "module",
   "bin": {
     "interactive-mcp": "dist/index.js"
   },
   "files": [
-    "dist",
+    "dist/constants.js",
+    "dist/index.js",
+    "dist/commands/input",
+    "dist/commands/intensive-chat",
+    "dist/components",
+    "dist/tool-definitions",
+    "dist/utils",
     "README.md",
     "LICENSE",
     "package.json"