@hailer/mcp 1.3.23 → 1.3.32

package/dist/public-chat/index.js

@@ -14,6 +14,7 @@ exports.PUBLIC_CHAT_AUTHORIZE_ROUTE = exports.PUBLIC_CHAT_HISTORY_ROUTE = export
 exports.registerPublicChatRoutes = registerPublicChatRoutes;
 const express_1 = __importDefault(require("express"));
 const logger_1 = require("../lib/logger");
+const config_1 = require("../config");
 const handler_1 = require("./handler");
 const system_prompt_1 = require("./system-prompt");
 const session_store_1 = require("./session-store");
@@ -27,7 +28,17 @@ exports.PUBLIC_CHAT_HISTORY_ROUTE = '/api/public-chat/history';
 const UUID_REGEX = /^[0-9a-f]{8}-[0-9a-f]{4}-[1-5][0-9a-f]{3}-[89ab][0-9a-f]{3}-[0-9a-f]{12}$/i;
 function registerPublicChatRoutes(app, opts) {
     if (!opts.anthropicApiKey) {
-        logger.warn(`${exports.PUBLIC_CHAT_ROUTE} disabled — ANTHROPIC_API_KEY not set in environment`);
+        // A hosted deployment missing the key is a config problem worth a
+        // warning; on CLI-run servers (npm run mcp-start) public chat is not
+        // a supported feature and the missing key is the norm — keep it out
+        // of local dev logs.
+        const message = `${exports.PUBLIC_CHAT_ROUTE} disabled — ANTHROPIC_API_KEY not set in environment`;
+        if (config_1.environment.HAILER_MCP_CLI) {
+            logger.debug(message);
+        }
+        else {
+            logger.warn(message);
+        }
         return false;
     }
     app.post(exports.PUBLIC_CHAT_ROUTE, (0, handler_1.createPublicChatHandler)(opts.anthropicApiKey));

package/dist/public-chat/index.js.map

@@ -1 +1 @@
-{"version":3,"file":"index.js","sourceRoot":"","sources":["../../src/public-chat/index.ts"],"names":[],"mappings":";AAAA;;;;;;GAMG;;;;;;AAmBH,4DA0DC;AA3ED,sDAA8B;AAC9B,0CAA6C;AAC7C,uCAAoD;AACpD,mDAAkD;AAClD,mDAAyD;AACzD,6CAAyC;AACzC,yCAA2F;AAMlF,4GANkC,sCAA2B,OAMlC;AAJpC,MAAM,MAAM,GAAG,IAAA,qBAAY,EAAC,EAAE,SAAS,EAAE,aAAa,EAAE,CAAC,CAAC;AAE7C,QAAA,iBAAiB,GAAG,kBAAkB,CAAC;AACvC,QAAA,yBAAyB,GAAG,0BAA0B,CAAC;AAGpE,qEAAqE;AACrE,MAAM,UAAU,GAAG,4EAA4E,CAAC;AAEhG,SAAgB,wBAAwB,CACpC,GAAoB,EACpB,IAA6C;IAE7C,IAAI,CAAC,IAAI,CAAC,eAAe,EAAE,CAAC;QACxB,MAAM,CAAC,IAAI,CACP,GAAG,yBAAiB,sDAAsD,CAC7E,CAAC;QACF,OAAO,KAAK,CAAC;IACjB,CAAC;IAED,GAAG,CAAC,IAAI,CAAC,yBAAiB,EAAE,IAAA,iCAAuB,EAAC,IAAI,CAAC,eAAe,CAAC,CAAC,CAAC;IAE3E,0EAA0E;IAC1E,wEAAwE;IACxE,8DAA8D;IAC9D,EAAE;IACF,0EAA0E;IAC1E,0EAA0E;IAC1E,oEAAoE;IACpE,0EAA0E;IAC1E,GAAG,CAAC,GAAG,CAAC,iCAAyB,EAAE,CAAC,GAAG,EAAE,GAAG,EAAE,EAAE;QAC5C,sEAAsE;QACtE,MAAM,IAAI,GAAG,IAAA,sBAAS,EAAC,GAAG,CAAC,EAAE,IAAI,SAAS,CAAC,CAAC;QAC5C,IAAI,CAAC,IAAI,CAAC,EAAE,EAAE,CAAC;YACX,GAAG,CAAC,SAAS,CAAC,aAAa,EAAE,MAAM,CAAC,IAAI,CAAC,aAAa,IAAI,EAAE,CAAC,CAAC,CAAC;YAC/D,GAAG,CAAC,MAAM,CAAC,GAAG,CAAC,CAAC,IAAI,CAAC,EAAE,KAAK,EAAE,cAAc,EAAE,CAAC,CAAC;YAChD,OAAO;QACX,CAAC;QACD,MAAM,SAAS,GAAG,OAAO,GAAG,CAAC,KAAK,CAAC,SAAS,KAAK,QAAQ,CAAC,CAAC,CAAC,GAAG,CAAC,KAAK,CAAC,SAAS,CAAC,CAAC,CAAC,EAAE,CAAC;QACrF,IAAI,CAAC,UAAU,CAAC,IAAI,CAAC,SAAS,CAAC,EAAE,CAAC;YAC9B,GAAG,CAAC,MAAM,CAAC,GAAG,CAAC,CAAC,IAAI,CAAC,EAAE,KAAK,EAAE,oBAAoB,EAAE,CAAC,CAAC;YACtD,OAAO;QACX,CAAC;QACD,MAAM,KAAK,GAAG,sCAAsB,CAAC,GAAG,CAAC,SAAS,CAAC,CAAC;QACpD,IAAI,CAAC,KAAK,EAAE,CAAC;YACT,GAAG,CAAC,MAAM,CAAC,GAAG,CAAC,CAAC,IAAI,CAAC,EAAE,KAAK,EAAE,mBAAmB,EAAE,CAAC,CAAC;YACrD,OAAO;QACX,CAAC;QACD,GAAG,CAAC,IAAI,CAAC,EAAE,SAAS,EAAE,QAAQ,EAAE,KAAK,EAAE,CAAC,CAAC;IAC7C,CAAC,CAAC,CAAC;IAEH,qEAAqE;IACrE,uEAAuE;IACvE,uEAAuE;IACvE,GAAG,CAAC,IAAI,CACJ,sCAA2B,EAC3B,iBAAO,CAAC,UAAU,CAAC,EAAE,QAAQ,EAAE,IAAI,EAAE,CAAC,EACtC,IAAA,2CAAgC,GAAE,CACrC,CAAC;IAEF,MAAM,CAAC,IAAI,CAAC,+BAA+B,EAAE;QACzC,IAAI,EAAE,yBAAiB;QACvB,OAAO,EAAE,iCAAyB;QAClC,SAAS,EAAE,sCAA2B;QACtC,cAAc,EAAE,+BAAe;KAClC,CAAC,CAAC;IACH,OAAO,IAAI,CAAC;AAChB,CAAC"}
+{"version":3,"file":"index.js","sourceRoot":"","sources":["../../src/public-chat/index.ts"],"names":[],"mappings":";AAAA;;;;;;GAMG;;;;;;AAoBH,4DAiEC;AAnFD,sDAA8B;AAC9B,0CAA6C;AAC7C,sCAAwC;AACxC,uCAAoD;AACpD,mDAAkD;AAClD,mDAAyD;AACzD,6CAAyC;AACzC,yCAA2F;AAMlF,4GANkC,sCAA2B,OAMlC;AAJpC,MAAM,MAAM,GAAG,IAAA,qBAAY,EAAC,EAAE,SAAS,EAAE,aAAa,EAAE,CAAC,CAAC;AAE7C,QAAA,iBAAiB,GAAG,kBAAkB,CAAC;AACvC,QAAA,yBAAyB,GAAG,0BAA0B,CAAC;AAGpE,qEAAqE;AACrE,MAAM,UAAU,GAAG,4EAA4E,CAAC;AAEhG,SAAgB,wBAAwB,CACpC,GAAoB,EACpB,IAA6C;IAE7C,IAAI,CAAC,IAAI,CAAC,eAAe,EAAE,CAAC;QACxB,kEAAkE;QAClE,qEAAqE;QACrE,oEAAoE;QACpE,qBAAqB;QACrB,MAAM,OAAO,GAAG,GAAG,yBAAiB,sDAAsD,CAAC;QAC3F,IAAI,oBAAW,CAAC,cAAc,EAAE,CAAC;YAC7B,MAAM,CAAC,KAAK,CAAC,OAAO,CAAC,CAAC;QAC1B,CAAC;aAAM,CAAC;YACJ,MAAM,CAAC,IAAI,CAAC,OAAO,CAAC,CAAC;QACzB,CAAC;QACD,OAAO,KAAK,CAAC;IACjB,CAAC;IAED,GAAG,CAAC,IAAI,CAAC,yBAAiB,EAAE,IAAA,iCAAuB,EAAC,IAAI,CAAC,eAAe,CAAC,CAAC,CAAC;IAE3E,0EAA0E;IAC1E,wEAAwE;IACxE,8DAA8D;IAC9D,EAAE;IACF,0EAA0E;IAC1E,0EAA0E;IAC1E,oEAAoE;IACpE,0EAA0E;IAC1E,GAAG,CAAC,GAAG,CAAC,iCAAyB,EAAE,CAAC,GAAG,EAAE,GAAG,EAAE,EAAE;QAC5C,sEAAsE;QACtE,MAAM,IAAI,GAAG,IAAA,sBAAS,EAAC,GAAG,CAAC,EAAE,IAAI,SAAS,CAAC,CAAC;QAC5C,IAAI,CAAC,IAAI,CAAC,EAAE,EAAE,CAAC;YACX,GAAG,CAAC,SAAS,CAAC,aAAa,EAAE,MAAM,CAAC,IAAI,CAAC,aAAa,IAAI,EAAE,CAAC,CAAC,CAAC;YAC/D,GAAG,CAAC,MAAM,CAAC,GAAG,CAAC,CAAC,IAAI,CAAC,EAAE,KAAK,EAAE,cAAc,EAAE,CAAC,CAAC;YAChD,OAAO;QACX,CAAC;QACD,MAAM,SAAS,GAAG,OAAO,GAAG,CAAC,KAAK,CAAC,SAAS,KAAK,QAAQ,CAAC,CAAC,CAAC,GAAG,CAAC,KAAK,CAAC,SAAS,CAAC,CAAC,CAAC,EAAE,CAAC;QACrF,IAAI,CAAC,UAAU,CAAC,IAAI,CAAC,SAAS,CAAC,EAAE,CAAC;YAC9B,GAAG,CAAC,MAAM,CAAC,GAAG,CAAC,CAAC,IAAI,CAAC,EAAE,KAAK,EAAE,oBAAoB,EAAE,CAAC,CAAC;YACtD,OAAO;QACX,CAAC;QACD,MAAM,KAAK,GAAG,sCAAsB,CAAC,GAAG,CAAC,SAAS,CAAC,CAAC;QACpD,IAAI,CAAC,KAAK,EAAE,CAAC;YACT,GAAG,CAAC,MAAM,CAAC,GAAG,CAAC,CAAC,IAAI,CAAC,EAAE,KAAK,EAAE,mBAAmB,EAAE,CAAC,CAAC;YACrD,OAAO;QACX,CAAC;QACD,GAAG,CAAC,IAAI,CAAC,EAAE,SAAS,EAAE,QAAQ,EAAE,KAAK,EAAE,CAAC,CAAC;IAC7C,CAAC,CAAC,CAAC;IAEH,qEAAqE;IACrE,uEAAuE;IACvE,uEAAuE;IACvE,GAAG,CAAC,IAAI,CACJ,sCAA2B,EAC3B,iBAAO,CAAC,UAAU,CAAC,EAAE,QAAQ,EAAE,IAAI,EAAE,CAAC,EACtC,IAAA,2CAAgC,GAAE,CACrC,CAAC;IAEF,MAAM,CAAC,IAAI,CAAC,+BAA+B,EAAE;QACzC,IAAI,EAAE,yBAAiB;QACvB,OAAO,EAAE,iCAAyB;QAClC,SAAS,EAAE,sCAA2B;QACtC,cAAc,EAAE,+BAAe;KAClC,CAAC,CAAC;IACH,OAAO,IAAI,CAAC;AAChB,CAAC"}

package/dist/public-chat/session-store.d.ts

@@ -23,12 +23,33 @@ export interface StoredTurn {
     content: string;
     at: number;
 }
+export interface DiscoveryBrief {
+    industry?: string;
+    job?: string;
+    today?: string;
+    door?: 'never_built' | 'tried_building' | 'wont_build';
+    must_haves?: string;
+}
 export declare class PublicChatSessionStore {
     private sessions;
     /** Append a user/assistant exchange to the session. Creates the session if needed. */
     append(sessionId: string, userText: string, assistantText: string): void;
-    /** Returns stored turns for a session, or null if unknown / expired. */
+    /**
+     * Returns a snapshot of the stored turns for a session, or null if
+     * unknown / expired. A copy, not the live array — callers hold the result
+     * across async gaps (e.g. the graduation flow), and a concurrent append()
+     * must not mutate their view (nor can the >cap reslice in append() leave
+     * them pointing at a detached array).
+     */
     get(sessionId: string): StoredTurn[] | null;
+    /** Set guide mode for a session. */
+    setGuideMode(sessionId: string, guideMode: boolean): void;
+    /** Check if a session is in guide mode. */
+    isGuideMode(sessionId: string): boolean;
+    /** Get the discovery brief for a session. */
+    getDiscoveryBrief(sessionId: string): DiscoveryBrief | null;
+    /** Parse [brief:field=value] tags from assistant text. */
+    private parseBriefTags;
     /** Removes a session entirely (e.g., visitor clicked Reset). */
     clear(sessionId: string): void;
     /** Test/debug helper. */

package/dist/public-chat/session-store.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"session-store.d.ts","sourceRoot":"","sources":["../../src/public-chat/session-store.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;GAmBG;AAEH,MAAM,WAAW,UAAU;IACzB,IAAI,EAAE,MAAM,GAAG,WAAW,CAAC;IAC3B,OAAO,EAAE,MAAM,CAAC;IAChB,EAAE,EAAE,MAAM,CAAC;CACZ;AAaD,qBAAa,sBAAsB;IACjC,OAAO,CAAC,QAAQ,CAAoC;IAEpD,sFAAsF;IACtF,MAAM,CAAC,SAAS,EAAE,MAAM,EAAE,QAAQ,EAAE,MAAM,EAAE,aAAa,EAAE,MAAM,GAAG,IAAI;IAyBxE,wEAAwE;IACxE,GAAG,CAAC,SAAS,EAAE,MAAM,GAAG,UAAU,EAAE,GAAG,IAAI;IAO3C,gEAAgE;IAChE,KAAK,CAAC,SAAS,EAAE,MAAM,GAAG,IAAI;IAI9B,yBAAyB;IACzB,IAAI,IAAI,MAAM;IAId,OAAO,CAAC,YAAY;IASpB,OAAO,CAAC,WAAW;CAapB;AAED,+CAA+C;AAC/C,eAAO,MAAM,sBAAsB,wBAA+B,CAAC"}
+{"version":3,"file":"session-store.d.ts","sourceRoot":"","sources":["../../src/public-chat/session-store.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;GAmBG;AAEH,MAAM,WAAW,UAAU;IACzB,IAAI,EAAE,MAAM,GAAG,WAAW,CAAC;IAC3B,OAAO,EAAE,MAAM,CAAC;IAChB,EAAE,EAAE,MAAM,CAAC;CACZ;AAED,MAAM,WAAW,cAAc;IAC7B,QAAQ,CAAC,EAAE,MAAM,CAAC;IAClB,GAAG,CAAC,EAAE,MAAM,CAAC;IACb,KAAK,CAAC,EAAE,MAAM,CAAC;IACf,IAAI,CAAC,EAAE,aAAa,GAAG,gBAAgB,GAAG,YAAY,CAAC;IACvD,UAAU,CAAC,EAAE,MAAM,CAAC;CACrB;AAeD,qBAAa,sBAAsB;IACjC,OAAO,CAAC,QAAQ,CAAoC;IAEpD,sFAAsF;IACtF,MAAM,CAAC,SAAS,EAAE,MAAM,EAAE,QAAQ,EAAE,MAAM,EAAE,aAAa,EAAE,MAAM,GAAG,IAAI;IA8BxE;;;;;;OAMG;IACH,GAAG,CAAC,SAAS,EAAE,MAAM,GAAG,UAAU,EAAE,GAAG,IAAI;IAO3C,oCAAoC;IACpC,YAAY,CAAC,SAAS,EAAE,MAAM,EAAE,SAAS,EAAE,OAAO,GAAG,IAAI;IAOzD,2CAA2C;IAC3C,WAAW,CAAC,SAAS,EAAE,MAAM,GAAG,OAAO;IAIvC,6CAA6C;IAC7C,iBAAiB,CAAC,SAAS,EAAE,MAAM,GAAG,cAAc,GAAG,IAAI;IAM3D,0DAA0D;IAC1D,OAAO,CAAC,cAAc;IAgBtB,gEAAgE;IAChE,KAAK,CAAC,SAAS,EAAE,MAAM,GAAG,IAAI;IAI9B,yBAAyB;IACzB,IAAI,IAAI,MAAM;IAId,OAAO,CAAC,YAAY;IASpB,OAAO,CAAC,WAAW;CAapB;AAED,+CAA+C;AAC/C,eAAO,MAAM,sBAAsB,wBAA+B,CAAC"}

package/dist/public-chat/session-store.js

@@ -38,6 +38,8 @@ class PublicChatSessionStore {
             session = {
                 sessionId,
                 turns: [],
+                guideMode: false,
+                discoveryBrief: {},
                 createdAt: now,
                 updatedAt: now,
             };
@@ -46,18 +48,70 @@ class PublicChatSessionStore {
         const now = Date.now();
         session.turns.push({ role: 'user', content: userText, at: now });
         session.turns.push({ role: 'assistant', content: assistantText, at: now });
+        // Parse <brief> tags from assistant message and update discovery brief
+        this.parseBriefTags(session, assistantText);
         if (session.turns.length > PUBLIC_CHAT_SESSION_MAX_TURNS) {
             session.turns = session.turns.slice(-PUBLIC_CHAT_SESSION_MAX_TURNS);
         }
         session.updatedAt = now;
     }
-    /** Returns stored turns for a session, or null if unknown / expired. */
+    /**
+     * Returns a snapshot of the stored turns for a session, or null if
+     * unknown / expired. A copy, not the live array — callers hold the result
+     * across async gaps (e.g. the graduation flow), and a concurrent append()
+     * must not mutate their view (nor can the >cap reslice in append() leave
+     * them pointing at a detached array).
+     */
     get(sessionId) {
         this.evictExpired();
         const session = this.sessions.get(sessionId);
         if (!session)
             return null;
-        return session.turns;
+        return session.turns.slice();
+    }
+    /** Set guide mode for a session. */
+    setGuideMode(sessionId, guideMode) {
+        const session = this.sessions.get(sessionId);
+        if (session) {
+            session.guideMode = guideMode;
+        }
+    }
+    /** Check if a session is in guide mode. */
+    isGuideMode(sessionId) {
+        return this.sessions.get(sessionId)?.guideMode ?? false;
+    }
+    /** Get the discovery brief for a session. */
+    getDiscoveryBrief(sessionId) {
+        const session = this.sessions.get(sessionId);
+        if (!session || Object.keys(session.discoveryBrief).length === 0)
+            return null;
+        return { ...session.discoveryBrief };
+    }
+    /** Parse [brief:field=value] tags from assistant text. */
+    parseBriefTags(session, text) {
+        const regex = /\[brief:(\w+)=([^\]]+)\]/gi;
+        let match;
+        while ((match = regex.exec(text)) !== null) {
+            const field = match[1];
+            const value = match[2].trim();
+            switch (field) {
+                case 'industry':
+                    session.discoveryBrief.industry = value;
+                    break;
+                case 'job':
+                    session.discoveryBrief.job = value;
+                    break;
+                case 'today':
+                    session.discoveryBrief.today = value;
+                    break;
+                case 'door':
+                    session.discoveryBrief.door = value;
+                    break;
+                case 'must_haves':
+                    session.discoveryBrief.must_haves = value;
+                    break;
+            }
+        }
     }
     /** Removes a session entirely (e.g., visitor clicked Reset). */
     clear(sessionId) {

package/dist/public-chat/session-store.js.map

@@ -1 +1 @@
-{"version":3,"file":"session-store.js","sourceRoot":"","sources":["../../src/public-chat/session-store.ts"],"names":[],"mappings":";AAAA;;;;;;;;;;;;;;;;;;;GAmBG;;;AAeH,MAAM,0BAA0B,GAAG,EAAE,GAAG,EAAE,GAAG,EAAE,GAAG,IAAI,CAAC,CAAC,WAAW;AACnE,MAAM,gCAAgC,GAAG,IAAI,CAAC;AAC9C,MAAM,6BAA6B,GAAG,EAAE,CAAC;AAEzC,MAAa,sBAAsB;IACzB,QAAQ,GAAG,IAAI,GAAG,EAAyB,CAAC;IAEpD,sFAAsF;IACtF,MAAM,CAAC,SAAiB,EAAE,QAAgB,EAAE,aAAqB;QAC/D,IAAI,CAAC,YAAY,EAAE,CAAC;QACpB,IAAI,OAAO,GAAG,IAAI,CAAC,QAAQ,CAAC,GAAG,CAAC,SAAS,CAAC,CAAC;QAC3C,IAAI,CAAC,OAAO,EAAE,CAAC;YACb,IAAI,IAAI,CAAC,QAAQ,CAAC,IAAI,IAAI,gCAAgC,EAAE,CAAC;gBAC3D,IAAI,CAAC,WAAW,EAAE,CAAC;YACrB,CAAC;YACD,MAAM,GAAG,GAAG,IAAI,CAAC,GAAG,EAAE,CAAC;YACvB,OAAO,GAAG;gBACR,SAAS;gBACT,KAAK,EAAE,EAAE;gBACT,SAAS,EAAE,GAAG;gBACd,SAAS,EAAE,GAAG;aACf,CAAC;YACF,IAAI,CAAC,QAAQ,CAAC,GAAG,CAAC,SAAS,EAAE,OAAO,CAAC,CAAC;QACxC,CAAC;QACD,MAAM,GAAG,GAAG,IAAI,CAAC,GAAG,EAAE,CAAC;QACvB,OAAO,CAAC,KAAK,CAAC,IAAI,CAAC,EAAE,IAAI,EAAE,MAAM,EAAE,OAAO,EAAE,QAAQ,EAAE,EAAE,EAAE,GAAG,EAAE,CAAC,CAAC;QACjE,OAAO,CAAC,KAAK,CAAC,IAAI,CAAC,EAAE,IAAI,EAAE,WAAW,EAAE,OAAO,EAAE,aAAa,EAAE,EAAE,EAAE,GAAG,EAAE,CAAC,CAAC;QAC3E,IAAI,OAAO,CAAC,KAAK,CAAC,MAAM,GAAG,6BAA6B,EAAE,CAAC;YACzD,OAAO,CAAC,KAAK,GAAG,OAAO,CAAC,KAAK,CAAC,KAAK,CAAC,CAAC,6BAA6B,CAAC,CAAC;QACtE,CAAC;QACD,OAAO,CAAC,SAAS,GAAG,GAAG,CAAC;IAC1B,CAAC;IAED,wEAAwE;IACxE,GAAG,CAAC,SAAiB;QACnB,IAAI,CAAC,YAAY,EAAE,CAAC;QACpB,MAAM,OAAO,GAAG,IAAI,CAAC,QAAQ,CAAC,GAAG,CAAC,SAAS,CAAC,CAAC;QAC7C,IAAI,CAAC,OAAO;YAAE,OAAO,IAAI,CAAC;QAC1B,OAAO,OAAO,CAAC,KAAK,CAAC;IACvB,CAAC;IAED,gEAAgE;IAChE,KAAK,CAAC,SAAiB;QACrB,IAAI,CAAC,QAAQ,CAAC,MAAM,CAAC,SAAS,CAAC,CAAC;IAClC,CAAC;IAED,yBAAyB;IACzB,IAAI;QACF,OAAO,IAAI,CAAC,QAAQ,CAAC,IAAI,CAAC;IAC5B,CAAC;IAEO,YAAY;QAClB,MAAM,GAAG,GAAG,IAAI,CAAC,GAAG,EAAE,CAAC;QACvB,KAAK,MAAM,CAAC,EAAE,EAAE,CAAC,CAAC,IAAI,IAAI,CAAC,QAAQ,EAAE,CAAC;YACpC,IAAI,GAAG,GAAG,CAAC,CAAC,SAAS,GAAG,0BAA0B,EAAE,CAAC;gBACnD,IAAI,CAAC,QAAQ,CAAC,MAAM,CAAC,EAAE,CAAC,CAAC;YAC3B,CAAC;QACH,CAAC;IACH,CAAC;IAEO,WAAW;QACjB,IAAI,QAAQ,GAAkB,IAAI,CAAC;QACnC,IAAI,eAAe,GAAG,QAAQ,CAAC;QAC/B,KAAK,MAAM,CAAC,EAAE,EAAE,CAAC,CAAC,IAAI,IAAI,CAAC,QAAQ,EAAE,CAAC;YACpC,IAAI,CAAC,CAAC,SAAS,GAAG,eAAe,EAAE,CAAC;gBAClC,eAAe,GAAG,CAAC,CAAC,SAAS,CAAC;gBAC9B,QAAQ,GAAG,EAAE,CAAC;YAChB,CAAC;QACH,CAAC;QACD,IAAI,QAAQ,KAAK,IAAI,EAAE,CAAC;YACtB,IAAI,CAAC,QAAQ,CAAC,MAAM,CAAC,QAAQ,CAAC,CAAC;QACjC,CAAC;IACH,CAAC;CACF;AArED,wDAqEC;AAED,+CAA+C;AAClC,QAAA,sBAAsB,GAAG,IAAI,sBAAsB,EAAE,CAAC"}
+{"version":3,"file":"session-store.js","sourceRoot":"","sources":["../../src/public-chat/session-store.ts"],"names":[],"mappings":";AAAA;;;;;;;;;;;;;;;;;;;GAmBG;;;AAyBH,MAAM,0BAA0B,GAAG,EAAE,GAAG,EAAE,GAAG,EAAE,GAAG,IAAI,CAAC,CAAC,WAAW;AACnE,MAAM,gCAAgC,GAAG,IAAI,CAAC;AAC9C,MAAM,6BAA6B,GAAG,EAAE,CAAC;AAEzC,MAAa,sBAAsB;IACzB,QAAQ,GAAG,IAAI,GAAG,EAAyB,CAAC;IAEpD,sFAAsF;IACtF,MAAM,CAAC,SAAiB,EAAE,QAAgB,EAAE,aAAqB;QAC/D,IAAI,CAAC,YAAY,EAAE,CAAC;QACpB,IAAI,OAAO,GAAG,IAAI,CAAC,QAAQ,CAAC,GAAG,CAAC,SAAS,CAAC,CAAC;QAC3C,IAAI,CAAC,OAAO,EAAE,CAAC;YACb,IAAI,IAAI,CAAC,QAAQ,CAAC,IAAI,IAAI,gCAAgC,EAAE,CAAC;gBAC3D,IAAI,CAAC,WAAW,EAAE,CAAC;YACrB,CAAC;YACD,MAAM,GAAG,GAAG,IAAI,CAAC,GAAG,EAAE,CAAC;YACvB,OAAO,GAAG;gBACR,SAAS;gBACT,KAAK,EAAE,EAAE;gBACT,SAAS,EAAE,KAAK;gBAChB,cAAc,EAAE,EAAE;gBAClB,SAAS,EAAE,GAAG;gBACd,SAAS,EAAE,GAAG;aACf,CAAC;YACF,IAAI,CAAC,QAAQ,CAAC,GAAG,CAAC,SAAS,EAAE,OAAO,CAAC,CAAC;QACxC,CAAC;QACD,MAAM,GAAG,GAAG,IAAI,CAAC,GAAG,EAAE,CAAC;QACvB,OAAO,CAAC,KAAK,CAAC,IAAI,CAAC,EAAE,IAAI,EAAE,MAAM,EAAE,OAAO,EAAE,QAAQ,EAAE,EAAE,EAAE,GAAG,EAAE,CAAC,CAAC;QACjE,OAAO,CAAC,KAAK,CAAC,IAAI,CAAC,EAAE,IAAI,EAAE,WAAW,EAAE,OAAO,EAAE,aAAa,EAAE,EAAE,EAAE,GAAG,EAAE,CAAC,CAAC;QAE3E,uEAAuE;QACvE,IAAI,CAAC,cAAc,CAAC,OAAO,EAAE,aAAa,CAAC,CAAC;QAC5C,IAAI,OAAO,CAAC,KAAK,CAAC,MAAM,GAAG,6BAA6B,EAAE,CAAC;YACzD,OAAO,CAAC,KAAK,GAAG,OAAO,CAAC,KAAK,CAAC,KAAK,CAAC,CAAC,6BAA6B,CAAC,CAAC;QACtE,CAAC;QACD,OAAO,CAAC,SAAS,GAAG,GAAG,CAAC;IAC1B,CAAC;IAED;;;;;;OAMG;IACH,GAAG,CAAC,SAAiB;QACnB,IAAI,CAAC,YAAY,EAAE,CAAC;QACpB,MAAM,OAAO,GAAG,IAAI,CAAC,QAAQ,CAAC,GAAG,CAAC,SAAS,CAAC,CAAC;QAC7C,IAAI,CAAC,OAAO;YAAE,OAAO,IAAI,CAAC;QAC1B,OAAO,OAAO,CAAC,KAAK,CAAC,KAAK,EAAE,CAAC;IAC/B,CAAC;IAED,oCAAoC;IACpC,YAAY,CAAC,SAAiB,EAAE,SAAkB;QAChD,MAAM,OAAO,GAAG,IAAI,CAAC,QAAQ,CAAC,GAAG,CAAC,SAAS,CAAC,CAAC;QAC7C,IAAI,OAAO,EAAE,CAAC;YACZ,OAAO,CAAC,SAAS,GAAG,SAAS,CAAC;QAChC,CAAC;IACH,CAAC;IAED,2CAA2C;IAC3C,WAAW,CAAC,SAAiB;QAC3B,OAAO,IAAI,CAAC,QAAQ,CAAC,GAAG,CAAC,SAAS,CAAC,EAAE,SAAS,IAAI,KAAK,CAAC;IAC1D,CAAC;IAED,6CAA6C;IAC7C,iBAAiB,CAAC,SAAiB;QACjC,MAAM,OAAO,GAAG,IAAI,CAAC,QAAQ,CAAC,GAAG,CAAC,SAAS,CAAC,CAAC;QAC7C,IAAI,CAAC,OAAO,IAAI,MAAM,CAAC,IAAI,CAAC,OAAO,CAAC,cAAc,CAAC,CAAC,MAAM,KAAK,CAAC;YAAE,OAAO,IAAI,CAAC;QAC9E,OAAO,EAAE,GAAG,OAAO,CAAC,cAAc,EAAE,CAAC;IACvC,CAAC;IAED,0DAA0D;IAClD,cAAc,CAAC,OAAsB,EAAE,IAAY;QACzD,MAAM,KAAK,GAAG,4BAA4B,CAAC;QAC3C,IAAI,KAA6B,CAAC;QAClC,OAAO,CAAC,KAAK,GAAG,KAAK,CAAC,IAAI,CAAC,IAAI,CAAC,CAAC,KAAK,IAAI,EAAE,CAAC;YAC3C,MAAM,KAAK,GAAG,KAAK,CAAC,CAAC,CAAC,CAAC;YACvB,MAAM,KAAK,GAAG,KAAK,CAAC,CAAC,CAAC,CAAC,IAAI,EAAE,CAAC;YAC9B,QAAQ,KAAK,EAAE,CAAC;gBACd,KAAK,UAAU;oBAAE,OAAO,CAAC,cAAc,CAAC,QAAQ,GAAG,KAAK,CAAC;oBAAC,MAAM;gBAChE,KAAK,KAAK;oBAAE,OAAO,CAAC,cAAc,CAAC,GAAG,GAAG,KAAK,CAAC;oBAAC,MAAM;gBACtD,KAAK,OAAO;oBAAE,OAAO,CAAC,cAAc,CAAC,KAAK,GAAG,KAAK,CAAC;oBAAC,MAAM;gBAC1D,KAAK,MAAM;oBAAE,OAAO,CAAC,cAAc,CAAC,IAAI,GAAG,KAA+B,CAAC;oBAAC,MAAM;gBAClF,KAAK,YAAY;oBAAE,OAAO,CAAC,cAAc,CAAC,UAAU,GAAG,KAAK,CAAC;oBAAC,MAAM;YACtE,CAAC;QACH,CAAC;IACH,CAAC;IAED,gEAAgE;IAChE,KAAK,CAAC,SAAiB;QACrB,IAAI,CAAC,QAAQ,CAAC,MAAM,CAAC,SAAS,CAAC,CAAC;IAClC,CAAC;IAED,yBAAyB;IACzB,IAAI;QACF,OAAO,IAAI,CAAC,QAAQ,CAAC,IAAI,CAAC;IAC5B,CAAC;IAEO,YAAY;QAClB,MAAM,GAAG,GAAG,IAAI,CAAC,GAAG,EAAE,CAAC;QACvB,KAAK,MAAM,CAAC,EAAE,EAAE,CAAC,CAAC,IAAI,IAAI,CAAC,QAAQ,EAAE,CAAC;YACpC,IAAI,GAAG,GAAG,CAAC,CAAC,SAAS,GAAG,0BAA0B,EAAE,CAAC;gBACnD,IAAI,CAAC,QAAQ,CAAC,MAAM,CAAC,EAAE,CAAC,CAAC;YAC3B,CAAC;QACH,CAAC;IACH,CAAC;IAEO,WAAW;QACjB,IAAI,QAAQ,GAAkB,IAAI,CAAC;QACnC,IAAI,eAAe,GAAG,QAAQ,CAAC;QAC/B,KAAK,MAAM,CAAC,EAAE,EAAE,CAAC,CAAC,IAAI,IAAI,CAAC,QAAQ,EAAE,CAAC;YACpC,IAAI,CAAC,CAAC,SAAS,GAAG,eAAe,EAAE,CAAC;gBAClC,eAAe,GAAG,CAAC,CAAC,SAAS,CAAC;gBAC9B,QAAQ,GAAG,EAAE,CAAC;YAChB,CAAC;QACH,CAAC;QACD,IAAI,QAAQ,KAAK,IAAI,EAAE,CAAC;YACtB,IAAI,CAAC,QAAQ,CAAC,MAAM,CAAC,QAAQ,CAAC,CAAC;QACjC,CAAC;IACH,CAAC;CACF;AArHD,wDAqHC;AAED,+CAA+C;AAClC,QAAA,sBAAsB,GAAG,IAAI,sBAAsB,EAAE,CAAC"}

package/dist/public-chat/system-prompt.d.ts

@@ -17,6 +17,6 @@ export interface SystemPromptBlock {
         type: 'ephemeral';
     };
 }
-export declare function buildPublicChatSystem(): SystemPromptBlock[];
+export declare function buildPublicChatSystem(guideMode?: boolean): SystemPromptBlock[];
 export declare const KNOWLEDGE_BYTES: number;
 //# sourceMappingURL=system-prompt.d.ts.map

package/dist/public-chat/system-prompt.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"system-prompt.d.ts","sourceRoot":"","sources":["../../src/public-chat/system-prompt.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;GAWG;AAIH,MAAM,WAAW,iBAAiB;IAChC,IAAI,EAAE,MAAM,CAAC;IACb,IAAI,EAAE,MAAM,CAAC;IACb,aAAa,CAAC,EAAE;QAAE,IAAI,EAAE,WAAW,CAAA;KAAE,CAAC;CACvC;AAopBD,wBAAgB,qBAAqB,IAAI,iBAAiB,EAAE,CAE3D;AAED,eAAO,MAAM,eAAe,QAAyB,CAAC"}
+{"version":3,"file":"system-prompt.d.ts","sourceRoot":"","sources":["../../src/public-chat/system-prompt.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;GAWG;AAIH,MAAM,WAAW,iBAAiB;IAChC,IAAI,EAAE,MAAM,CAAC;IACb,IAAI,EAAE,MAAM,CAAC;IACb,aAAa,CAAC,EAAE;QAAE,IAAI,EAAE,WAAW,CAAA;KAAE,CAAC;CACvC;AAmuBD,wBAAgB,qBAAqB,CAAC,SAAS,UAAQ,GAAG,iBAAiB,EAAE,CAE5E;AAED,eAAO,MAAM,eAAe,QAAyB,CAAC"}

package/dist/public-chat/system-prompt.js

@@ -58,7 +58,7 @@ Reframe features as relief, not capability lists. Examples of the right shape:
 
 CLOSE LADDER — never skip a rung: watch → see → try → start.
   watch = open the overview deck
-  see   = navigate to the view that maps to their case (kanban, table, discussions…)
+  see   = navigate to the relevant info page (discussions, feed, calendar, marketplace…)
   try   = surface a marketplace template / app for their specific need
   start = "Continue in Hailer" (free workspace + this chat carries over)
 
@@ -85,18 +85,73 @@ Confidence with humility. "I think this would help because X" — never "you nee
 Every reply:
 - 1-3 sentences (the answer)
 - 2-3 numbered options (what to do next)
-- Options are written FROM THE VISITOR'S perspective — as if the visitor is saying it. "I want to see pricing", "Show me sales templates", "I need a project tracker" — NOT "Tell me what you need" or "I'll find templates for you" (that's the bot talking, not the visitor).
+- Options are written FROM THE VISITOR'S perspective — "Tell me about pricing", "Explain the marketplace", "I need a project tracker". Use "Tell me about" / "Explain" instead of "Show me" — we explain things in text, not navigate to pages.
+- Numbered options MUST be the VERY LAST thing in your message. No text after them — no "If your option isn't here", no "Type freely", no extra sentences. The frontend turns the last numbered lines into clickable buttons, and any text after them breaks this.
 
-EVERY reply — including the very first one — MUST end with 2-3 numbered options. No exceptions.
+EVERY reply — including the very first one — MUST end with 2-3 numbered options. No exceptions (except CONVERSION — see below).
 
 If the visitor says something generic like "hi", "hello", "hey" — respond with a short welcome and options:
 "Welcome! Hailer is a workspace where your team manages processes, communication, and data in one place. What would you like to do?
 
 1. Tell me more about Hailer
-2. I already know what I need
-3. Show me the marketplace"
+2. I'm looking for something specific
+3. Guide me — help me figure out what I need"
 
-═══ CONVERSATION FLOW ═══
+═══ TWO MODES ═══
+
+You are always in one of two modes:
+
+1) FREE CHAT (default): the visitor asks anything. Answer briefly and honestly from what you know about Hailer. After answering, include numbered options as usual.
+
+2) GUIDE ME (entered when the visitor says "Guide me", "help me figure out what I need", "interview me", or similar): You lead. You interview the visitor to learn what they actually need. The rules below override FREE CHAT rules while in this mode.
+
+═══ GUIDE ME MODE ═══
+
+When Guide-me is active, the "NEVER ask questions" and "40 word limit" rules are SUSPENDED. Instead you lead a SHORT guided interview: THREE questions, then a proposal. Never more than three questions before proposing.
+
+How to ask:
+- ONE question per message, one short line.
+- Every question comes WITH 3-4 numbered options as example answers (written as the visitor would say them) — tapping beats typing. Free text is always welcome; the options are shortcuts, not a locked menu.
+- Ask about their world in their words — nouns and annoyances. Never ask about "software", "solutions", "requirements" or any abstraction they'd have to translate their work into.
+- Mirror back in one short clause before the next question ("Construction — got it.") so they feel heard. A clause, not a paragraph.
+
+PERSONA CHECK (silent — never announce it, never add extra questions):
+- BUILDER: picked "I'm technical — I build software" in question 1, or uses words like API, schema, database, stack, code, "I built". Same three questions, about the system THEY want to build; peer-to-peer tone, skip beginner reassurance. In the proposal, replace the "no code" line with: "Studio builds it as config-as-code — inspect it, change it, drop to the SDK anytime."
+- SHOPPER: asks about price, templates, install, or "does it work for my industry". Same three questions, but lead the proposal with the ready-made route: "People in your industry already built this — install it, then reshape it if you want", with build-from-scratch as the second option.
+- SCOUT: no business of their own in play — asks "what is Hailer", "who's behind this", investor/press/student vibes. Guide-me is the wrong tool: give the one-line whole picture ("your data in one Core, apps on top, a marketplace of ready solutions") and switch back to FREE CHAT with the usual options.
+- Everyone else is the default flow exactly as written. Guessed wrong? Switch registers instantly, without ceremony.
+
+The three questions, in order — each fills one slot of the build brief:
+
+1. WHO: "What kind of business are you in?"
+   Options: a few common industries (e.g. construction / field work, agency / consulting, sales-driven company) plus one persona catch: "I'm technical — I build software". One tap should be enough for most visitors.
+
+2. WHAT: "Which part of the work do you want under control first?"
+   Options MUST be generated from their answer to question 1, named as THEIR processes — actual work, not features. Construction → jobs from quote to invoice, crew scheduling, equipment & materials. Law firm → case management, billing, document tracking.
+
+3. PAIN: "What's the most annoying part of how that runs today?"
+   Options: info scattered across tools / retyping the same things / no overview of where things stand / things slip through the cracks.
+   Their pick becomes the promise your proposal makes.
+
+THE PROPOSAL (right after question 3 — never a fourth question):
+- Propose a concrete setup in their language: the workflow, its phases, what's attached to each record, and the pain it kills. Weave in ONE reassurance line — no code, they describe and it gets built. Shape:
+  "Here's what I'd set up: a Jobs workflow running quote → in progress → invoiced, customers and files attached to each job, one view of where everything stands — so nothing slips. No code — you describe it, it gets built. Sound right?"
+- People are bad at specifying and good at correcting — the proposal is where the real discovery happens. If they correct it, adjust and re-propose in one line. Don't restart the interview.
+- End with these options:
+1. Yes — let's build it
+2. Change something
+3. Show me a ready-made template instead
+
+Routing from the proposal:
+- "Yes — let's build it" → suggest signup with the recap: "Let's get you a free account — this plan carries over, and I start turning it into real software on the other side."
+- "Show me a ready-made template instead" → follow the marketplace flow with their category.
+- Do NOT design further or build anything yourself. You gather the brief; the bot inside Hailer builds.
+
+If the visitor isn't ready, don't push. Offer to keep answering questions.
+
+The visitor can leave Guide-me at any time by asking a different question or clicking a button — switch back to FREE CHAT mode.
+
+═══ FREE CHAT FLOW ═══
 
 Your goal: introduce Hailer, walk the visitor through key features, discover what they need, match them to marketplace solutions, and lead toward signup. The entire chat transfers to their workspace after registration.
 
@@ -107,26 +162,26 @@ When the visitor says "Tell me more about Hailer" or similar ("what is Hailer",
 - Give a 3-5 sentence overview covering the key ideas: Hailer replaces scattered tools (CRM, project tracker, chat, spreadsheets) with one workspace. Workflows model your processes with phases and fields. Every record has its own discussion thread so context stays with the work. There's a marketplace with ready-made templates you can install and customize. Apps and AI agents extend the platform.
 - ALWAYS end with this exact sentence before the options: "Want to see it in action? Click 'Take a tour' in the top left corner — it walks you through the main features step by step."
 - Offer numbered options:
-1. I already know what I need
-2. Show me the marketplace
+1. I'm looking for something specific
+2. Tell me about the marketplace
 
 Do NOT navigate anywhere. Do NOT launch a tour yourself. The tour button in the UI handles it.
 
-SHOW ME THE MARKETPLACE:
-When the visitor says "Show me the marketplace" or similar:
-- Navigate to apps page: <bot-action type="navigate" target="apps" />
-- In your reply text, tell them they can browse what's there OR describe what they need and you'll search for matching templates.
-- Offer concrete category options — NOT generic "I'm looking for a specific solution":
+TELL ME ABOUT THE MARKETPLACE:
+When the visitor asks about the marketplace or templates:
+- Explain that Hailer has ready-made templates and apps for different use cases that they can install and customize after signing up.
+- Offer concrete category options:
 1. Sales pipeline
 2. Project tracker
 3. HR & onboarding
 4. Customer support
-- The message text already invites them to type freely, so no need for a catch-all option.
+
+IMPORTANT: Numbered options must be the LAST thing in your message. Do NOT add any text after the numbered list — no "If your option isn't here...", no "Type freely", nothing. The options must be at the very end so they render as clickable buttons.
 
 SHORTCUT — DIRECT BUSINESS NEED:
-If the visitor says "I already know what I need" or mentions their business, industry, or specific need at ANY point (e.g. "I run a construction company", "we need a sales pipeline", "I'm looking for project management", "HR tool for my team"), respond with a short question and concrete options.
+If the visitor says "I'm looking for something specific" (or the older phrasing "I already know what I need") or mentions their business, industry, or specific need at ANY point (e.g. "I run a construction company", "we need a sales pipeline", "I'm looking for project management", "HR tool for my team"), respond with a short question and concrete options.
 
-When the visitor says "I already know what I need" (without specifying what):
+When the visitor says "I'm looking for something specific" (without specifying what):
 - Ask "What are you looking to build or track?" in your message text
 - End the message with: "If your option isn't here, just type it in the chat."
 - Offer these numbered options:
@@ -154,7 +209,7 @@ When they pick a specific option → do marketplace-search with TOOL keywords (n
 
 ` +
     // Scripted tour STEP 1-6 moved to frontend tour state machine to save output tokens.
-    // AI engages only on divergence (Tell me more, free text, "I already know what I need").
+    // AI engages only on divergence (Tell me more, free text, "I'm looking for something specific").
     // Original kept in /* */ for reference and easy restore.
     /*
     STEP 1 — WELCOME (when you receive "start"):
@@ -164,7 +219,7 @@ When they pick a specific option → do marketplace-search with TOOL keywords (n
     "Hailer is a workspace platform where teams manage structured work, communication, and data in one place. Instead of jumping between a CRM, a project tracker, and a chat app — everything lives here, connected. Ask me anything or use the buttons below.
     
     1. Give me the tour
-    2. I already know what I need"
+    2. I'm looking for something specific"
     
     STEP 2 — DISCUSSIONS (visitor chose "Give me the tour"):
     Navigate to discussions. Explain what makes Hailer discussions special — they're not just chat, they're attached to work. Every activity, every event has its own thread. When a deal moves forward, the conversation history is right there. 2-3 sentences.
@@ -174,7 +229,7 @@ When they pick a specific option → do marketplace-search with TOOL keywords (n
     Options:
     1. Tell me more about discussions
     2. Next: Data Core — how work is structured →
-    3. I already know what I need
+    3. I'm looking for something specific
     
     If they pick "Tell me more" — expand: group chats, private messages, file sharing, searchable history, how discussions replace email threads and Slack channels for work context. Then offer the same Next option again.
     
@@ -186,7 +241,7 @@ When they pick a specific option → do marketplace-search with TOOL keywords (n
     Options:
     1. Tell me more about workflows
     2. Next: Feed — team updates and news →
-    3. I already know what I need
+    3. I'm looking for something specific
     
     If they pick "Tell me more" — expand: custom fields (text, dates, numbers, dropdowns, linked activities), phases with permissions, kanban vs table view, how activities connect to discussions and files. Then offer the same Next option again.
     
@@ -198,7 +253,7 @@ When they pick a specific option → do marketplace-search with TOOL keywords (n
     Options:
     1. Tell me more about the feed
     2. Next: Apps — extend Hailer with custom tools →
-    3. I already know what I need
+    3. I'm looking for something specific
     
     If they pick "Tell me more" — expand: anyone can post, like, comment. Workflow milestones auto-post. Tags help organize content. It replaces mass emails and "FYI" Slack messages. Then offer the same Next option again.
     
@@ -210,7 +265,7 @@ When they pick a specific option → do marketplace-search with TOOL keywords (n
     Options:
     1. Tell me more about apps
     2. Next: Marketplace — find ready-made solutions →
-    3. I already know what I need
+    3. I'm looking for something specific
     
     If they pick "Tell me more" — expand: AI Hub for managing bots, Document Templates for generating PDFs from data, Email Builder, Custom Dashboards. The SDK lets developers build anything — the app lives in the sidebar and has full access to workspace data. Then offer Browse solutions or I know what I need.
     
@@ -230,7 +285,7 @@ When they pick a specific option → do marketplace-search with TOOL keywords (n
     */
     '' + `
 
-DISCOVERY — when visitor picks "I already know what I need" or "Find a solution" at any step:
+DISCOVERY — when visitor picks "I'm looking for something specific" or "Find a solution" at any step:
 Ask what they need and offer specific categories. End with a note that they can type freely.
 
 "What are you looking to build or track? If your option isn't here, just type it in the chat.
@@ -261,14 +316,13 @@ A bakery doesn't need a "bakery template". They need:
 Your job: translate "I'm a [business type]" into 2-3 concrete tool needs, then search for THOSE.
 
 Use multiple marketplace-search tags if needed — one per tool category. Use their language, not Hailer jargon.
-ALWAYS include <bot-action type="navigate" target="apps" /> to show the marketplace page. NEVER navigate to workflow-list, kanban, or Data Core when searching for templates.
+Do NOT include <bot-action type="navigate" target="apps" /> — the marketplace-search buttons handle navigation automatically when clicked. Just include the marketplace-search tags.
 
 Example for "I'm a plumber":
 "For a plumbing business, you'd want job tracking to manage service calls, a client list to keep customer history, and invoicing to bill when the job's done.
-<bot-action type="marketplace-search" target="project tracking" category="template" label="Job tracking templates →" />
-<bot-action type="marketplace-search" target="CRM" category="template" label="Client management →" />
-<bot-action type="marketplace-search" target="invoicing" category="template" label="Invoicing tools →" />
-<bot-action type="navigate" target="apps" />
+<bot-action type="marketplace-search" target="project tracking" label="Job tracking solutions →" />
+<bot-action type="marketplace-search" target="CRM" label="Client management →" />
+<bot-action type="marketplace-search" target="invoicing" label="Invoicing tools →" />
 
 1. Tell me more about how job tracking works
 2. Nothing matched — let me describe what I need
@@ -283,20 +337,15 @@ When you see a message like 'Install the template [name: Product Name] by Publis
 3. Do NOT describe the template. Do NOT mention sales/HR/projects/etc. Do NOT add context from earlier in the conversation. Just name + signup.
 4. No numbered options. Two sentences max.
 
-CONVERSION (visitor chose "try this" / "try it for real" / "sign up" / "I want to try on my own data"):
-Give them a reason to sign up tied to what they just saw. Not "click the button" — explain what they GET:
-- This conversation carries over, so the workspace bot already knows what they need
-- The bot can install templates, build workflows, configure fields — all from what you discussed
-- It's free, no credit card
+CONVERSION (visitor chose "try this" / "try it for real" / "sign up" / "Continue in Hailer" / "I want to try on my own data" / "I'm ready"):
+One sentence pointing to the "Sign up, it's free!" button at the bottom. That's it. No numbered options. No "I'm ready" button. No "What happens next?" button. The visitor already agreed — don't add more steps.
 
-Example: "Click 'Continue in Hailer' below — it creates a free workspace and the bot inside already knows we talked about [their use case]. It'll set everything up for you."
+Example: "Click 'Sign up, it's free!' below — your free workspace will be ready with everything we discussed."
 
-One sentence max. Then options to continue exploring or ask more questions. Don't repeat signup push if they don't click.
+Do NOT add any numbered options or buttons after this message. The signup button is right there — let them click it.
 
 PRICING — whenever the visitor asks about pricing, cost, plans, payment, how much, free tier, subscription, or anything related to money:
-Always navigate to the pricing page and answer from this data:
-
-<bot-action type="navigate" target="pricing" />
+Answer from this data (do NOT navigate to a different page):
 
 Hailer pricing:
 - Flexible: €0/month — pay-as-you-go, no commitment. Standard token rate (1x). Unlimited people.
@@ -313,44 +362,22 @@ Keep the answer short — 2-3 sentences highlighting the free start and token ef
 
 ═══ THE DEMO PAGE ═══
 
-You live on a demo page. LEFT: sidebar navigation. CENTER: interactive demo content. RIGHT: this chat.
-You control the center area with navigate tags. Use them to SHOW what you're talking about.
-
-DEMO VIEWS — what's on each page and when to show it:
-
-workflow-list — DEPRECATED, DO NOT USE. This page shows a static placeholder, not real content. To explain workflows, use kanban view instead or just describe in text.
-
-kanban — A "Sales Pipeline" board with columns (New, Qualified, Proposal, Won). Cards represent deals/activities. Use when explaining how work moves through phases, or when visitor mentions sales/pipeline/tracking.
-
-table — Same data as kanban but in a spreadsheet-like table with sortable columns. Use when visitor asks about data, reporting, bulk views, or Excel-like features.
+You live on a demo page with a chat panel on the right side.
 
-activity-detail — Right panel showing a single activity with fields, tabs (detail, discussion, files, location, linked). Use when explaining what an activity contains or how fields work.
+═══ NAVIGATION — HARD RULES ═══
 
-discussions — List of chat threads. Shows team conversations. Use when explaining communication, chat, or collaboration features.
+You can include <bot-action type="navigate" target="about" /> in your FIRST reply only.
+After that, do NOT use any navigate tags. The marketplace-search buttons handle their own navigation when clicked.
 
-discussion-detail — Inside a specific chat thread with messages. Use when showing how conversations work.
+That's it. ONE case only:
+1. First reply → navigate to about
 
-feed — Company-wide activity feed with posts, likes, comments. Use when explaining announcements, updates, or company-wide visibility.
-
-calendar — Month view with events. Use when explaining scheduling, events, or time-based features.
-
-apps — Marketplace page with real product cards (templates, apps, integrations, AI agents). Use when visitor wants to browse solutions, or after identifying their use case. This page shows REAL products from the database.
-
-SIDEBAR SECTIONS:
-- Core Apps: Discussions, Calendar, Feed — everyday tools
-- Data Core: Where workflows live — the heart of Hailer
-- Studio: Build custom apps
-- Marketplace: Browse and install templates, apps, integrations
-- Learn section: How it works, Pricing, Contact, Help, Terms, Privacy
-- Developers: API, SDK, MCP documentation
-
-When explaining a concept, ALWAYS navigate to the relevant view so the visitor sees it live. Don't just describe — show.
+NEVER navigate to discussions, feed, calendar, kanban, table, activity-detail, workflow-list, discussion-detail, or any other target. Not even if the visitor asks about those features. Just explain in text — do not switch pages.
 
 ═══ WHAT YOU CAN DO ═══
 
-- Navigate demo views
-- Navigate to different demo views
-- Search marketplace with filters (marketplace-search tag)
+- Answer questions about Hailer in text
+- Search marketplace with filters (marketplace-search tag) + navigate to apps
 - You CANNOT create real data or workspaces — that happens after signup
 
 ═══ MARKETPLACE-SEARCH ═══
@@ -358,13 +385,14 @@ When explaining a concept, ALWAYS navigate to the relevant view so the visitor s
 When the visitor mentions a specific need, ALWAYS include this tag:
 <bot-action type="marketplace-search" target="{search keywords}" category="{category}" label="{button text}" />
 
-Categories: template, app, integration, ai-agent, support. Omit category to search all.
+Categories: template, app, integration, ai-agent, support.
+DEFAULT: OMIT category — an all-category search also surfaces apps and AI agents the visitor wouldn't think to ask for. Only set a category when the visitor explicitly asks for that kind ("a template", "an app for...", "an AI agent").
 The tag renders as a clickable button in the chat. The visitor sees the label, not the tag.
 
 Examples:
-<bot-action type="marketplace-search" target="sales pipeline" category="template" label="Browse sales templates →" />
+<bot-action type="marketplace-search" target="sales pipeline" label="Browse sales solutions →" />
 <bot-action type="marketplace-search" target="HR onboarding" label="Browse HR solutions →" />
-<bot-action type="marketplace-search" target="project management" category="template" label="See project templates →" />
+Visitor explicitly asked for a template: <bot-action type="marketplace-search" target="project management" category="template" label="See project templates →" />
 
 ═══ GRADUATION ═══
 
@@ -388,19 +416,15 @@ Write tags as plain text in your reply: <bot-action type="..." target="..." />
 Do NOT wrap in function_calls or invoke. Do NOT use underscores in "bot-action".
 
 Available tags:
-- Navigate: <bot-action type="navigate" target="{view}" />
-- Marketplace search (renders as a clickable button):
+- Navigate (FIRST MESSAGE ONLY): <bot-action type="navigate" target="about" />
+- Marketplace search (renders as a clickable button — handles navigation to marketplace automatically when clicked):
   <bot-action type="marketplace-search" target="{query}" category="{category}" label="{button text}" />
-  Categories: template, app, integration, ai-agent, support. Omit category to search all.
+  Categories: template, app, integration, ai-agent, support. OMIT category by default (searches all); set one only when the visitor explicitly asks for that kind.
 
-Navigate targets: kanban, table, activity-detail, discussions, discussion-detail, feed, calendar, apps
-NOTE: workflow-list is DEPRECATED — do not use it. Use kanban instead to show workflows.
 Rules:
-- Use one or two tags per reply, max — except for guided tours (see below). More than that is noise.
-- ONLY use highlight when the user is asking where something is or how to do something specific. Don't sprinkle them on regular Q&A.
-- ONLY use navigate when the user asks to be taken somewhere or you're answering "show me how X looks". Don't auto-navigate after every message.
+- Navigate ONLY in the first reply, ONLY to "about". No other navigate tags ever.
+- marketplace-search buttons navigate to the marketplace page automatically — do NOT add a separate navigate tag.
 - Tags are stripped from the visible text — write your real answer normally alongside any tag.
-- Never invent target names. If the right target isn't in the list above, just answer in words.
 
 The Hailer overview presentation — when to use the 'presentation' action:
 - The demo page has a separate spatial slide deck (15 slides) that introduces Hailer's
@@ -657,7 +681,47 @@ const KNOWLEDGE_HEADER = `Below is the knowledge base you may draw on. Treat it
  * Both blocks carry cache_control: ephemeral so they hit Anthropic's prompt
  * cache across requests inside the 5-minute TTL window.
  */
-const SYSTEM_BLOCKS = [
+const GUIDE_ME_OVERRIDE = `
+YOU ARE NOW IN GUIDE-ME MODE. The free-chat rules (40-word limit, "never ask questions", numbered options) are SUSPENDED.
+
+Your job is to interview the visitor to learn what they need. Ask ONE question at a time. Keep each question short and plain. MAXIMUM 5 questions total + 1 optional clarification. After that, recap and suggest signup. Do NOT keep asking more questions.
+
+Follow this order:
+1. What kind of work or business are they in? (industry / role)
+2. What's the thing they wish worked better — the job they'd hand to software?
+3. How do they handle it today? (tools, spreadsheets, the manual pain)
+4. Have they tried building software before? (never built / tried building / don't want to build)
+5. What would "great" look like — the one or two must-haves?
+
+After question 5, you may ask ONE clarification if the answer was too vague. Then STOP interviewing and give the recap + signup suggestion. Do NOT ask about stages, fields, specific workflows — the bot inside Hailer will figure that out.
+
+BRIEF TAGS — after each visitor answer, include a hidden tag capturing the fact. The visitor won't see it (stripped by frontend). Format uses square brackets:
+- After Q1: [brief:industry=bookstore]
+- After Q2: [brief:job=track sales and orders]
+- After Q3: [brief:today=Excel and phone calls]
+- After Q4: [brief:door=never_built]  (values: never_built, tried_building, wont_build)
+- After Q5: [brief:must_haves=order ID, payment confirmation]
+
+Place the tag BEFORE the numbered options, not after them. One tag per message. Use the visitor's own words in the value — don't rephrase or summarize. Do NOT use "pending" as a value — only tag after you have the visitor's actual answer.
+
+Rules:
+- Mirror back what you hear in one line so they feel understood.
+- Adapt to their answer about building:
+  • Never built → "No code, no developers needed — you just describe what you want."
+  • Tried building → "The prototype was easy, the system was hard — that hard part is handled here."
+  • Don't want to build → "People in your industry already built solutions you can install and use."
+- ONE question per message. After the reassurance line, STOP. Do NOT add another question in the same message. Wait for their reply, then ask the next question.
+- After each question, offer 3-4 numbered options as example answers + one "Something else — I'll type it in" option. This helps the visitor answer quickly. They can also type freely.
+- Do NOT try to design or build anything. You gather info; the bot inside Hailer builds.
+- NEVER repeat the same question twice. If the visitor gives a vague answer ("hi", "hello", "ok", etc.), don't re-ask — instead rephrase or give an example: "For example, do you run a shop, a service company, a team inside a bigger org...?" Move the conversation forward, never loop.
+- If the visitor clearly doesn't want to answer a question, skip it and move to the next one. Not every question needs an answer — get what you can and move on.
+- When you have enough (industry, job-to-be-done, must-haves), give a one-line recap and suggest signup:
+  "Got it — [recap]. Let's get you an account and I'll start turning this into real software. Same me on the other side, with the tools to build it."
+- If the visitor isn't ready, don't push. Offer to keep answering questions.
+- If the visitor says "Exit guide mode" — acknowledge it briefly: "No problem! Feel free to ask me anything about Hailer or browse around." Then switch back to normal free-chat behavior with numbered options.
+`;
+/** Free-chat system blocks — built once, reused across requests (prompt-cacheable). */
+const FREE_CHAT_BLOCKS = [
     {
         type: 'text',
         text: PERSONA_AND_RULES + '\n' + BOT_ACTION_PROTOCOL,
@@ -669,8 +733,21 @@ const SYSTEM_BLOCKS = [
         cache_control: { type: 'ephemeral' },
     },
 ];
-function buildPublicChatSystem() {
-    return SYSTEM_BLOCKS;
+/** Guide-me system blocks — interview prompt prepended, rest stays cached. */
+const GUIDE_ME_BLOCKS = [
+    {
+        type: 'text',
+        text: PERSONA_AND_RULES + '\n' + BOT_ACTION_PROTOCOL + '\n\n' + GUIDE_ME_OVERRIDE,
+        cache_control: { type: 'ephemeral' },
+    },
+    {
+        type: 'text',
+        text: KNOWLEDGE_HEADER + knowledge_1.HAILER_KNOWLEDGE_CORPUS,
+        cache_control: { type: 'ephemeral' },
+    },
+];
+function buildPublicChatSystem(guideMode = false) {
+    return guideMode ? GUIDE_ME_BLOCKS : FREE_CHAT_BLOCKS;
 }
 exports.KNOWLEDGE_BYTES = knowledge_1.HAILER_KNOWLEDGE_BYTES;
 //# sourceMappingURL=system-prompt.js.map

package/dist/public-chat/system-prompt.js.map

@@ -1 +1 @@
-{"version":3,"file":"system-prompt.js","sourceRoot":"","sources":["../../src/public-chat/system-prompt.ts"],"names":[],"mappings":";AAAA;;;;;;;;;;;GAWG;;;AA4pBH,sDAEC;AA5pBD,2CAA8E;AAQ9E,MAAM,iBAAiB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAyIzB;IACD,qFAAqF;IACrF,yFAAyF;IACzF,yDAAyD;IACzD;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;MAuEE;IACF,EAAE,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAyJJ,CAAC;AAEF,MAAM,mBAAmB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAqF3B;IACD,oFAAoF;IACpF,iGAAiG;IACjG,yDAAyD;IACzD;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;MA6KE;IACF,EAAE,CAAC;AAEH,MAAM,gBAAgB,GAAG;;CAExB,CAAC;AAEF;;;;;;;GAOG;AACH,MAAM,aAAa,GAAwB;IACzC;QACE,IAAI,EAAE,MAAM;QACZ,IAAI,EAAE,iBAAiB,GAAG,IAAI,GAAG,mBAAmB;QACpD,aAAa,EAAE,EAAE,IAAI,EAAE,WAAW,EAAE;KACrC;IACD;QACE,IAAI,EAAE,MAAM;QACZ,IAAI,EAAE,gBAAgB,GAAG,mCAAuB;QAChD,aAAa,EAAE,EAAE,IAAI,EAAE,WAAW,EAAE;KACrC;CACF,CAAC;AAEF,SAAgB,qBAAqB;IACnC,OAAO,aAAa,CAAC;AACvB,CAAC;AAEY,QAAA,eAAe,GAAG,kCAAsB,CAAC"}
+{"version":3,"file":"system-prompt.js","sourceRoot":"","sources":["../../src/public-chat/system-prompt.ts"],"names":[],"mappings":";AAAA;;;;;;;;;;;GAWG;;;AA2uBH,sDAEC;AA3uBD,2CAA8E;AAQ9E,MAAM,iBAAiB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAgMzB;IACD,qFAAqF;IACrF,iGAAiG;IACjG,yDAAyD;IACzD;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;MAuEE;IACF,EAAE,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CA8HJ,CAAC;AAEF,MAAM,mBAAmB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAiF3B;IACD,oFAAoF;IACpF,iGAAiG;IACjG,yDAAyD;IACzD;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;MA6KE;IACF,EAAE,CAAC;AAEH,MAAM,gBAAgB,GAAG;;CAExB,CAAC;AAEF;;;;;;;GAOG;AACH,MAAM,iBAAiB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAsCzB,CAAC;AAEF,uFAAuF;AACvF,MAAM,gBAAgB,GAAwB;IAC5C;QACE,IAAI,EAAE,MAAM;QACZ,IAAI,EAAE,iBAAiB,GAAG,IAAI,GAAG,mBAAmB;QACpD,aAAa,EAAE,EAAE,IAAI,EAAE,WAAW,EAAE;KACrC;IACD;QACE,IAAI,EAAE,MAAM;QACZ,IAAI,EAAE,gBAAgB,GAAG,mCAAuB;QAChD,aAAa,EAAE,EAAE,IAAI,EAAE,WAAW,EAAE;KACrC;CACF,CAAC;AAEF,8EAA8E;AAC9E,MAAM,eAAe,GAAwB;IAC3C;QACE,IAAI,EAAE,MAAM;QACZ,IAAI,EAAE,iBAAiB,GAAG,IAAI,GAAG,mBAAmB,GAAG,MAAM,GAAG,iBAAiB;QACjF,aAAa,EAAE,EAAE,IAAI,EAAE,WAAW,EAAE;KACrC;IACD;QACE,IAAI,EAAE,MAAM;QACZ,IAAI,EAAE,gBAAgB,GAAG,mCAAuB;QAChD,aAAa,EAAE,EAAE,IAAI,EAAE,WAAW,EAAE;KACrC;CACF,CAAC;AAEF,SAAgB,qBAAqB,CAAC,SAAS,GAAG,KAAK;IACrD,OAAO,SAAS,CAAC,CAAC,CAAC,eAAe,CAAC,CAAC,CAAC,gBAAgB,CAAC;AACxD,CAAC;AAEY,QAAA,eAAe,GAAG,kCAAsB,CAAC"}