@arbidocs/client 0.3.71 → 0.3.72

package/dist/index.d.cts

@@ -1959,6 +1959,128 @@ interface paths {
         patch?: never;
         trace?: never;
     };
+    '/v1/connectors': {
+        parameters: {
+            query?: never;
+            header?: never;
+            path?: never;
+            cookie?: never;
+        };
+        /**
+         * List active connector catalog entries
+         * @description Return all active connector catalog entries (no secrets).
+         */
+        get: operations['list_connectors'];
+        put?: never;
+        post?: never;
+        delete?: never;
+        options?: never;
+        head?: never;
+        patch?: never;
+        trace?: never;
+    };
+    '/v1/connectors/me': {
+        parameters: {
+            query?: never;
+            header?: never;
+            path?: never;
+            cookie?: never;
+        };
+        /**
+         * List current user's installed connectors
+         * @description Return the list of connectors the current user has installed.
+         */
+        get: operations['list_my_connectors'];
+        put?: never;
+        post?: never;
+        delete?: never;
+        options?: never;
+        head?: never;
+        patch?: never;
+        trace?: never;
+    };
+    '/v1/connectors/{vendor_key}/status': {
+        parameters: {
+            query?: never;
+            header?: never;
+            path?: never;
+            cookie?: never;
+        };
+        /**
+         * Check if user is connected to a vendor
+         * @description Return catalog info plus is_connected and vendor_user_identity for this user/vendor pair.
+         */
+        get: operations['get_connector_status'];
+        put?: never;
+        post?: never;
+        delete?: never;
+        options?: never;
+        head?: never;
+        patch?: never;
+        trace?: never;
+    };
+    '/v1/connectors/{vendor_key}/authorize': {
+        parameters: {
+            query?: never;
+            header?: never;
+            path?: never;
+            cookie?: never;
+        };
+        /**
+         * Initiate PKCE OAuth 2.1 flow (dynamic discovery)
+         * @description Discover OAuth endpoints, build PKCE state, and return the vendor authorization URL.
+         *
+         *     The frontend navigates to the returned URL to initiate the vendor OAuth consent page.
+         */
+        get: operations['authorize_connector'];
+        put?: never;
+        post?: never;
+        delete?: never;
+        options?: never;
+        head?: never;
+        patch?: never;
+        trace?: never;
+    };
+    '/v1/connectors/{vendor_key}/callback': {
+        parameters: {
+            query?: never;
+            header?: never;
+            path?: never;
+            cookie?: never;
+        };
+        /**
+         * OAuth callback — exchange code for tokens
+         * @description Handle the OAuth callback: exchange code, encrypt + store tokens, redirect.
+         */
+        get: operations['oauth_callback'];
+        put?: never;
+        post?: never;
+        delete?: never;
+        options?: never;
+        head?: never;
+        patch?: never;
+        trace?: never;
+    };
+    '/v1/connectors/{vendor_key}': {
+        parameters: {
+            query?: never;
+            header?: never;
+            path?: never;
+            cookie?: never;
+        };
+        get?: never;
+        put?: never;
+        post?: never;
+        /**
+         * Disconnect a connector
+         * @description Delete the user's tokens and UserConnector row for this vendor.
+         */
+        delete: operations['disconnect_connector'];
+        options?: never;
+        head?: never;
+        patch?: never;
+        trace?: never;
+    };
     '/v1/responses': {
         parameters: {
             query?: never;
@@ -2249,6 +2371,30 @@ interface components {
              * @default false
              */
             MEMORY_CREATION: boolean;
+            /**
+             * Goals Enabled
+             * @description Feature gate for the goal/Ralph-loop system. When False, the /goal command is unavailable (falls through to a normal query) and the router may not auto-escalate to goal mode. Mirrors SKILLS_ENABLED; set per workspace/config to expose the feature.
+             * @default false
+             */
+            GOALS_ENABLED: boolean;
+            /**
+             * Goal Loop
+             * @description Transient flag set by the /goal command (only when GOALS_ENABLED). When True, the agent runs inside a Ralph loop: PlanningLLM authors a frozen acceptance checklist, the agent works it to completion, and after each pass ReviewLLM grades every criterion. The loop stops when all criteria are met, or after GOAL_MAX_OUTER_LOOPS passes.
+             * @default false
+             */
+            GOAL_LOOP: boolean;
+            /**
+             * Goal Text
+             * @description Transient objective set by the /goal command — the goal the Ralph loop drives toward.
+             * @default
+             */
+            GOAL_TEXT: string;
+            /**
+             * Goal Max Outer Loops
+             * @description Maximum number of outer Ralph-loop passes before the loop stops and returns its best answer, even if the goal judge has not declared the goal satisfied.
+             * @default 6
+             */
+            GOAL_MAX_OUTER_LOOPS: number;
             /**
              * Review Enabled
              * @description Enable ReviewLLM to review agent draft answers against source material before sending to the user. Uses the reasoning model for higher quality.
@@ -2339,6 +2485,7 @@ interface components {
              *     - Bold text for critical conclusions or decision points
              *
              *     TOOL CALLING:
+             *     - Your job is to gather context by calling tools, then answer only once every reasonable tool call has been made. Do not give a final answer while there is still relevant context you could retrieve.
              *     - Always invoke tools using the tool-calling mechanism. NEVER write text that describes or simulates a tool call (e.g. never write "Searching for X...", "Reading document Y...", "Calling search_inside_documents" as prose — actually call the tool).
              *     - If you intend to search or read, issue the tool call immediately. Do not narrate your intent first.
              *
@@ -2405,6 +2552,10 @@ interface components {
              *       "SKILLS_ENABLED": false,
              *       "SKILL_CREATION": false,
              *       "MEMORY_CREATION": false,
+             *       "GOALS_ENABLED": false,
+             *       "GOAL_LOOP": false,
+             *       "GOAL_TEXT": "",
+             *       "GOAL_MAX_OUTER_LOOPS": 6,
              *       "REVIEW_ENABLED": false,
              *       "PERSONA": "You are ARBI, an AI assistant created by ARBI CITY. Be proactive, helpful and professional.",
              *       "AGENT_MODEL_NAME": "auto",
@@ -2415,7 +2566,7 @@ interface components {
              *       "AGENT_MAX_ITERATIONS": 20,
              *       "AGENT_MAX_PARALLEL_TOOL_CALLS": 10,
              *       "AGENT_HISTORY_CHAR_THRESHOLD": 8000,
-             *       "AGENT_SYSTEM_PROMPT": "Answer any question the user asks. You have access to workspace documents — use them when relevant. When no documents are relevant, answer from your own knowledge. Always provide a helpful answer.\n\nIMPORTANT: Never say \"I don't have information in the available documents\" or refuse to answer. If documents are not relevant, just answer the question directly from your own knowledge. If the user asks about a specific workspace document, call read_document or get_table_of_contents — never answer from memory.\n\nWhen using documents, retrieve actual document content — do not rely on metadata or headings alone. Cross-check information across sources. Not all assertions in sources are factual — some are arguments by a party. Attribute claims to their source where parties disagree.\n\nDOCUMENT INDEX:\nThe \"Workspace Documents\" table in your system prompt already lists every document with its Id, Title, Date, Pages, and Subject. Use this table directly when the user asks to list, catalogue, or tabulate documents — do NOT call any tools for that. Only use tools when you need to read or search document content.\n\nDOCUMENT STRATEGY:\n- For listing/cataloguing documents: use the document index already in your prompt — no tool calls needed.\n- For overview/summary requests: use get_table_of_contents first, then read key sections with read_document.\n- For specific questions: use search_inside_documents to find relevant sections, then read those sections with read_document.\n- For translation, deep analysis, or detailed summaries of a single document: use read_document with no ranges to load the complete text.\n- For extracting structured findings from passages: use read_document with digest=true or search_inside_documents with digest=true.\n- Never search for meta-queries like \"summary\", \"overview\", or \"all documents\" — search for the actual subject matter.\n\nFORMATTING:\n- Start your answer directly with the content — never open with a description of what you searched for or read (e.g. never write \"Searching for X\", \"Reading Y\", \"I found Z documents\" as the first lines of an answer).\n- Use markdown: headings, bold, bullet points, numbered lists\n- Main conclusion first, followed by supporting points\n- Bullet points for lists of discrete items\n- Numbering for sequential steps or prioritized items\n- Bold text for critical conclusions or decision points\n\nTOOL CALLING:\n- Always invoke tools using the tool-calling mechanism. NEVER write text that describes or simulates a tool call (e.g. never write \"Searching for X...\", \"Reading document Y...\", \"Calling search_inside_documents\" as prose — actually call the tool).\n- If you intend to search or read, issue the tool call immediately. Do not narrate your intent first.\n\nEFFICIENCY:\n1. Before each step, review the results of prior steps. Adapt your approach based on what you learned — if a call was rejected or returned poor results, adjust your strategy.\n2. Call multiple tools in parallel when a query has several aspects.\n3. NEVER repeat a tool call with the same arguments.\n4. Use targeted queries and narrow page ranges per retrieval call.\n5. Stop when you have sufficient evidence — do not over-research."
+             *       "AGENT_SYSTEM_PROMPT": "Answer any question the user asks. You have access to workspace documents — use them when relevant. When no documents are relevant, answer from your own knowledge. Always provide a helpful answer.\n\nIMPORTANT: Never say \"I don't have information in the available documents\" or refuse to answer. If documents are not relevant, just answer the question directly from your own knowledge. If the user asks about a specific workspace document, call read_document or get_table_of_contents — never answer from memory.\n\nWhen using documents, retrieve actual document content — do not rely on metadata or headings alone. Cross-check information across sources. Not all assertions in sources are factual — some are arguments by a party. Attribute claims to their source where parties disagree.\n\nDOCUMENT INDEX:\nThe \"Workspace Documents\" table in your system prompt already lists every document with its Id, Title, Date, Pages, and Subject. Use this table directly when the user asks to list, catalogue, or tabulate documents — do NOT call any tools for that. Only use tools when you need to read or search document content.\n\nDOCUMENT STRATEGY:\n- For listing/cataloguing documents: use the document index already in your prompt — no tool calls needed.\n- For overview/summary requests: use get_table_of_contents first, then read key sections with read_document.\n- For specific questions: use search_inside_documents to find relevant sections, then read those sections with read_document.\n- For translation, deep analysis, or detailed summaries of a single document: use read_document with no ranges to load the complete text.\n- For extracting structured findings from passages: use read_document with digest=true or search_inside_documents with digest=true.\n- Never search for meta-queries like \"summary\", \"overview\", or \"all documents\" — search for the actual subject matter.\n\nFORMATTING:\n- Start your answer directly with the content — never open with a description of what you searched for or read (e.g. never write \"Searching for X\", \"Reading Y\", \"I found Z documents\" as the first lines of an answer).\n- Use markdown: headings, bold, bullet points, numbered lists\n- Main conclusion first, followed by supporting points\n- Bullet points for lists of discrete items\n- Numbering for sequential steps or prioritized items\n- Bold text for critical conclusions or decision points\n\nTOOL CALLING:\n- Your job is to gather context by calling tools, then answer only once every reasonable tool call has been made. Do not give a final answer while there is still relevant context you could retrieve.\n- Always invoke tools using the tool-calling mechanism. NEVER write text that describes or simulates a tool call (e.g. never write \"Searching for X...\", \"Reading document Y...\", \"Calling search_inside_documents\" as prose — actually call the tool).\n- If you intend to search or read, issue the tool call immediately. Do not narrate your intent first.\n\nEFFICIENCY:\n1. Before each step, review the results of prior steps. Adapt your approach based on what you learned — if a call was rejected or returned poor results, adjust your strategy.\n2. Call multiple tools in parallel when a query has several aspects.\n3. NEVER repeat a tool call with the same arguments.\n4. Use targeted queries and narrow page ranges per retrieval call.\n5. Stop when you have sufficient evidence — do not over-research."
              *     }
              */
             Agents: components['schemas']['AgentsConfig'];
@@ -2595,7 +2746,7 @@ interface components {
              * @default {
              *       "API_TYPE": "remote",
              *       "ENABLE_THINKING": true,
-             *       "MODEL_NAME": "Premium",
+             *       "MODEL_NAME": "GLM5@Fireworks",
              *       "SYSTEM_INSTRUCTION": "You are a code execution agent. You write and run code to accomplish tasks.\n\nYou have access to an execute_code tool that runs code in a sandboxed Docker container.\n\nThe sandbox has:\n- Python 3.12 with numpy, pandas, matplotlib, requests, beautifulsoup4,\n  httpx, pillow, sympy, pyyaml (plus uv for installing more)\n- Node.js 22 with TypeScript (ts-node) and npm\n- Bash with git, curl, wget, jq, sqlite3, build-essential\n- Network access (can pip/npm install additional packages)\n\nInstructions:\n1. Write clean, correct code to accomplish the user's task\n2. Always call execute_code to run your code — never guess the output\n3. If execution errors, analyze the traceback, fix the code, and retry\n4. Once you have the correct output, respond with ONLY the final result\n\nKeep code simple and direct. Prefer Python unless the task specifically requires another language.",
              *       "TEMPERATURE": 0.2,
              *       "MAX_TOKENS": 8000,
@@ -3077,7 +3228,7 @@ interface components {
             /**
              * Model Name
              * @description Model for code generation. Should be a strong coding model.
-             * @default Premium
+             * @default GLM5@Fireworks
              */
             MODEL_NAME: string;
             /**
@@ -3254,6 +3405,26 @@ interface components {
             /** Message */
             message: string;
         };
+        /** ConnectorCatalogRead */
+        ConnectorCatalogRead: {
+            /**
+             * Id
+             * Format: uuid
+             */
+            id: string;
+            /** Vendor Key */
+            vendor_key: string;
+            /** Display Name */
+            display_name: string;
+            /** Description */
+            description: string;
+            /** Icon Url */
+            icon_url: string | null;
+            /** Mcp Server Alias */
+            mcp_server_alias: string;
+            /** Requires Per User Auth */
+            requires_per_user_auth: boolean;
+        };
         /**
          * ConsolidatedHealthResponse
          * @description Consolidated health response containing all system status and version information
@@ -3362,6 +3533,22 @@ interface components {
             /** Title */
             title: string;
         };
+        /**
+         * ConversationTitleUpdatedMessage
+         * @description Conversation title regenerated server-side — frontend should refresh.
+         */
+        ConversationTitleUpdatedMessage: {
+            /**
+             * Type
+             * @default conversation.title_updated
+             * @constant
+             */
+            type: 'conversation.title_updated';
+            /** Conversation Ext Id */
+            conversation_ext_id: string;
+            /** Title */
+            title: string;
+        };
         /** CopyDocumentResult */
         CopyDocumentResult: {
             /** Source Doc Ext Id */
@@ -5170,7 +5357,7 @@ interface components {
              * Status
              * @enum {string}
              */
-            status: 'online' | 'unknown';
+            status: 'online' | 'offline' | 'unknown';
             /** Timestamp */
             timestamp: string;
         };
@@ -7420,6 +7607,32 @@ interface components {
             /** Items */
             items?: components['schemas']['InitedUploadItem'][];
         };
+        /** UserConnectorRead */
+        UserConnectorRead: {
+            /**
+             * Id
+             * Format: uuid
+             */
+            id: string;
+            /** Vendor Key */
+            vendor_key: string;
+            /** Display Name */
+            display_name: string;
+            /** Icon Url */
+            icon_url: string | null;
+            /**
+             * Connected At
+             * Format: date-time
+             */
+            connected_at: string;
+            /** Vendor User Identity */
+            vendor_user_identity: string | null;
+            /**
+             * Is Connected
+             * @default true
+             */
+            is_connected: boolean;
+        };
         /**
          * UserDailyUsageResponse
          * @description Today's deployment-wide credit spend tagged with the current user.
@@ -7647,6 +7860,11 @@ interface components {
              * @default false
              */
             show_mcp_connectors: boolean;
+            /**
+             * Show Hints
+             * @default true
+             */
+            show_hints: boolean;
             /**
              * Use S3 Direct Upload
              * @default false
@@ -7704,6 +7922,8 @@ interface components {
             show_agent_sessions?: boolean | null;
             /** Show Mcp Connectors */
             show_mcp_connectors?: boolean | null;
+            /** Show Hints */
+            show_hints?: boolean | null;
             /** Use S3 Direct Upload */
             use_s3_direct_upload?: boolean | null;
             /** Hide Online Status */
@@ -7872,6 +8092,7 @@ interface components {
             task_update?: components['schemas']['TaskUpdateMessage'] | null;
             batch_complete?: components['schemas']['BatchCompleteMessage'] | null;
             response_complete?: components['schemas']['ResponseCompleteMessage'] | null;
+            conversation_title_updated?: components['schemas']['ConversationTitleUpdatedMessage'] | null;
             notification?: components['schemas']['NotificationResponse'] | null;
             auth?: components['schemas']['AuthMessage'] | null;
             send_message?: components['schemas']['SendMessageRequest'] | null;
@@ -11050,6 +11271,175 @@ interface operations {
             };
         };
     };
+    list_connectors: {
+        parameters: {
+            query?: never;
+            header?: never;
+            path?: never;
+            cookie?: never;
+        };
+        requestBody?: never;
+        responses: {
+            /** @description Successful Response */
+            200: {
+                headers: {
+                    [name: string]: unknown;
+                };
+                content: {
+                    'application/json': components['schemas']['ConnectorCatalogRead'][];
+                };
+            };
+        };
+    };
+    list_my_connectors: {
+        parameters: {
+            query?: never;
+            header?: never;
+            path?: never;
+            cookie?: never;
+        };
+        requestBody?: never;
+        responses: {
+            /** @description Successful Response */
+            200: {
+                headers: {
+                    [name: string]: unknown;
+                };
+                content: {
+                    'application/json': components['schemas']['UserConnectorRead'][];
+                };
+            };
+        };
+    };
+    get_connector_status: {
+        parameters: {
+            query?: never;
+            header?: never;
+            path: {
+                vendor_key: string;
+            };
+            cookie?: never;
+        };
+        requestBody?: never;
+        responses: {
+            /** @description Successful Response */
+            200: {
+                headers: {
+                    [name: string]: unknown;
+                };
+                content: {
+                    'application/json': {
+                        [key: string]: unknown;
+                    };
+                };
+            };
+            /** @description Validation Error */
+            422: {
+                headers: {
+                    [name: string]: unknown;
+                };
+                content: {
+                    'application/json': components['schemas']['HTTPValidationError'];
+                };
+            };
+        };
+    };
+    authorize_connector: {
+        parameters: {
+            query?: never;
+            header?: never;
+            path: {
+                vendor_key: string;
+            };
+            cookie?: never;
+        };
+        requestBody?: never;
+        responses: {
+            /** @description Successful Response */
+            200: {
+                headers: {
+                    [name: string]: unknown;
+                };
+                content: {
+                    'application/json': {
+                        [key: string]: unknown;
+                    };
+                };
+            };
+            /** @description Validation Error */
+            422: {
+                headers: {
+                    [name: string]: unknown;
+                };
+                content: {
+                    'application/json': components['schemas']['HTTPValidationError'];
+                };
+            };
+        };
+    };
+    oauth_callback: {
+        parameters: {
+            query: {
+                code: string;
+                state: string;
+            };
+            header?: never;
+            path: {
+                vendor_key: string;
+            };
+            cookie?: never;
+        };
+        requestBody?: never;
+        responses: {
+            /** @description Successful Response */
+            200: {
+                headers: {
+                    [name: string]: unknown;
+                };
+                content: {
+                    'application/json': unknown;
+                };
+            };
+            /** @description Validation Error */
+            422: {
+                headers: {
+                    [name: string]: unknown;
+                };
+                content: {
+                    'application/json': components['schemas']['HTTPValidationError'];
+                };
+            };
+        };
+    };
+    disconnect_connector: {
+        parameters: {
+            query?: never;
+            header?: never;
+            path: {
+                vendor_key: string;
+            };
+            cookie?: never;
+        };
+        requestBody?: never;
+        responses: {
+            /** @description Successful Response */
+            204: {
+                headers: {
+                    [name: string]: unknown;
+                };
+                content?: never;
+            };
+            /** @description Validation Error */
+            422: {
+                headers: {
+                    [name: string]: unknown;
+                };
+                content: {
+                    'application/json': components['schemas']['HTTPValidationError'];
+                };
+            };
+        };
+    };
     create_response: {
         parameters: {
             query?: never;

package/dist/index.d.ts

@@ -1959,6 +1959,128 @@ interface paths {
         patch?: never;
         trace?: never;
     };
+    '/v1/connectors': {
+        parameters: {
+            query?: never;
+            header?: never;
+            path?: never;
+            cookie?: never;
+        };
+        /**
+         * List active connector catalog entries
+         * @description Return all active connector catalog entries (no secrets).
+         */
+        get: operations['list_connectors'];
+        put?: never;
+        post?: never;
+        delete?: never;
+        options?: never;
+        head?: never;
+        patch?: never;
+        trace?: never;
+    };
+    '/v1/connectors/me': {
+        parameters: {
+            query?: never;
+            header?: never;
+            path?: never;
+            cookie?: never;
+        };
+        /**
+         * List current user's installed connectors
+         * @description Return the list of connectors the current user has installed.
+         */
+        get: operations['list_my_connectors'];
+        put?: never;
+        post?: never;
+        delete?: never;
+        options?: never;
+        head?: never;
+        patch?: never;
+        trace?: never;
+    };
+    '/v1/connectors/{vendor_key}/status': {
+        parameters: {
+            query?: never;
+            header?: never;
+            path?: never;
+            cookie?: never;
+        };
+        /**
+         * Check if user is connected to a vendor
+         * @description Return catalog info plus is_connected and vendor_user_identity for this user/vendor pair.
+         */
+        get: operations['get_connector_status'];
+        put?: never;
+        post?: never;
+        delete?: never;
+        options?: never;
+        head?: never;
+        patch?: never;
+        trace?: never;
+    };
+    '/v1/connectors/{vendor_key}/authorize': {
+        parameters: {
+            query?: never;
+            header?: never;
+            path?: never;
+            cookie?: never;
+        };
+        /**
+         * Initiate PKCE OAuth 2.1 flow (dynamic discovery)
+         * @description Discover OAuth endpoints, build PKCE state, and return the vendor authorization URL.
+         *
+         *     The frontend navigates to the returned URL to initiate the vendor OAuth consent page.
+         */
+        get: operations['authorize_connector'];
+        put?: never;
+        post?: never;
+        delete?: never;
+        options?: never;
+        head?: never;
+        patch?: never;
+        trace?: never;
+    };
+    '/v1/connectors/{vendor_key}/callback': {
+        parameters: {
+            query?: never;
+            header?: never;
+            path?: never;
+            cookie?: never;
+        };
+        /**
+         * OAuth callback — exchange code for tokens
+         * @description Handle the OAuth callback: exchange code, encrypt + store tokens, redirect.
+         */
+        get: operations['oauth_callback'];
+        put?: never;
+        post?: never;
+        delete?: never;
+        options?: never;
+        head?: never;
+        patch?: never;
+        trace?: never;
+    };
+    '/v1/connectors/{vendor_key}': {
+        parameters: {
+            query?: never;
+            header?: never;
+            path?: never;
+            cookie?: never;
+        };
+        get?: never;
+        put?: never;
+        post?: never;
+        /**
+         * Disconnect a connector
+         * @description Delete the user's tokens and UserConnector row for this vendor.
+         */
+        delete: operations['disconnect_connector'];
+        options?: never;
+        head?: never;
+        patch?: never;
+        trace?: never;
+    };
     '/v1/responses': {
         parameters: {
             query?: never;
@@ -2249,6 +2371,30 @@ interface components {
              * @default false
              */
             MEMORY_CREATION: boolean;
+            /**
+             * Goals Enabled
+             * @description Feature gate for the goal/Ralph-loop system. When False, the /goal command is unavailable (falls through to a normal query) and the router may not auto-escalate to goal mode. Mirrors SKILLS_ENABLED; set per workspace/config to expose the feature.
+             * @default false
+             */
+            GOALS_ENABLED: boolean;
+            /**
+             * Goal Loop
+             * @description Transient flag set by the /goal command (only when GOALS_ENABLED). When True, the agent runs inside a Ralph loop: PlanningLLM authors a frozen acceptance checklist, the agent works it to completion, and after each pass ReviewLLM grades every criterion. The loop stops when all criteria are met, or after GOAL_MAX_OUTER_LOOPS passes.
+             * @default false
+             */
+            GOAL_LOOP: boolean;
+            /**
+             * Goal Text
+             * @description Transient objective set by the /goal command — the goal the Ralph loop drives toward.
+             * @default
+             */
+            GOAL_TEXT: string;
+            /**
+             * Goal Max Outer Loops
+             * @description Maximum number of outer Ralph-loop passes before the loop stops and returns its best answer, even if the goal judge has not declared the goal satisfied.
+             * @default 6
+             */
+            GOAL_MAX_OUTER_LOOPS: number;
             /**
              * Review Enabled
              * @description Enable ReviewLLM to review agent draft answers against source material before sending to the user. Uses the reasoning model for higher quality.
@@ -2339,6 +2485,7 @@ interface components {
              *     - Bold text for critical conclusions or decision points
              *
              *     TOOL CALLING:
+             *     - Your job is to gather context by calling tools, then answer only once every reasonable tool call has been made. Do not give a final answer while there is still relevant context you could retrieve.
              *     - Always invoke tools using the tool-calling mechanism. NEVER write text that describes or simulates a tool call (e.g. never write "Searching for X...", "Reading document Y...", "Calling search_inside_documents" as prose — actually call the tool).
              *     - If you intend to search or read, issue the tool call immediately. Do not narrate your intent first.
              *
@@ -2405,6 +2552,10 @@ interface components {
              *       "SKILLS_ENABLED": false,
              *       "SKILL_CREATION": false,
              *       "MEMORY_CREATION": false,
+             *       "GOALS_ENABLED": false,
+             *       "GOAL_LOOP": false,
+             *       "GOAL_TEXT": "",
+             *       "GOAL_MAX_OUTER_LOOPS": 6,
              *       "REVIEW_ENABLED": false,
              *       "PERSONA": "You are ARBI, an AI assistant created by ARBI CITY. Be proactive, helpful and professional.",
              *       "AGENT_MODEL_NAME": "auto",
@@ -2415,7 +2566,7 @@ interface components {
              *       "AGENT_MAX_ITERATIONS": 20,
              *       "AGENT_MAX_PARALLEL_TOOL_CALLS": 10,
              *       "AGENT_HISTORY_CHAR_THRESHOLD": 8000,
-             *       "AGENT_SYSTEM_PROMPT": "Answer any question the user asks. You have access to workspace documents — use them when relevant. When no documents are relevant, answer from your own knowledge. Always provide a helpful answer.\n\nIMPORTANT: Never say \"I don't have information in the available documents\" or refuse to answer. If documents are not relevant, just answer the question directly from your own knowledge. If the user asks about a specific workspace document, call read_document or get_table_of_contents — never answer from memory.\n\nWhen using documents, retrieve actual document content — do not rely on metadata or headings alone. Cross-check information across sources. Not all assertions in sources are factual — some are arguments by a party. Attribute claims to their source where parties disagree.\n\nDOCUMENT INDEX:\nThe \"Workspace Documents\" table in your system prompt already lists every document with its Id, Title, Date, Pages, and Subject. Use this table directly when the user asks to list, catalogue, or tabulate documents — do NOT call any tools for that. Only use tools when you need to read or search document content.\n\nDOCUMENT STRATEGY:\n- For listing/cataloguing documents: use the document index already in your prompt — no tool calls needed.\n- For overview/summary requests: use get_table_of_contents first, then read key sections with read_document.\n- For specific questions: use search_inside_documents to find relevant sections, then read those sections with read_document.\n- For translation, deep analysis, or detailed summaries of a single document: use read_document with no ranges to load the complete text.\n- For extracting structured findings from passages: use read_document with digest=true or search_inside_documents with digest=true.\n- Never search for meta-queries like \"summary\", \"overview\", or \"all documents\" — search for the actual subject matter.\n\nFORMATTING:\n- Start your answer directly with the content — never open with a description of what you searched for or read (e.g. never write \"Searching for X\", \"Reading Y\", \"I found Z documents\" as the first lines of an answer).\n- Use markdown: headings, bold, bullet points, numbered lists\n- Main conclusion first, followed by supporting points\n- Bullet points for lists of discrete items\n- Numbering for sequential steps or prioritized items\n- Bold text for critical conclusions or decision points\n\nTOOL CALLING:\n- Always invoke tools using the tool-calling mechanism. NEVER write text that describes or simulates a tool call (e.g. never write \"Searching for X...\", \"Reading document Y...\", \"Calling search_inside_documents\" as prose — actually call the tool).\n- If you intend to search or read, issue the tool call immediately. Do not narrate your intent first.\n\nEFFICIENCY:\n1. Before each step, review the results of prior steps. Adapt your approach based on what you learned — if a call was rejected or returned poor results, adjust your strategy.\n2. Call multiple tools in parallel when a query has several aspects.\n3. NEVER repeat a tool call with the same arguments.\n4. Use targeted queries and narrow page ranges per retrieval call.\n5. Stop when you have sufficient evidence — do not over-research."
+             *       "AGENT_SYSTEM_PROMPT": "Answer any question the user asks. You have access to workspace documents — use them when relevant. When no documents are relevant, answer from your own knowledge. Always provide a helpful answer.\n\nIMPORTANT: Never say \"I don't have information in the available documents\" or refuse to answer. If documents are not relevant, just answer the question directly from your own knowledge. If the user asks about a specific workspace document, call read_document or get_table_of_contents — never answer from memory.\n\nWhen using documents, retrieve actual document content — do not rely on metadata or headings alone. Cross-check information across sources. Not all assertions in sources are factual — some are arguments by a party. Attribute claims to their source where parties disagree.\n\nDOCUMENT INDEX:\nThe \"Workspace Documents\" table in your system prompt already lists every document with its Id, Title, Date, Pages, and Subject. Use this table directly when the user asks to list, catalogue, or tabulate documents — do NOT call any tools for that. Only use tools when you need to read or search document content.\n\nDOCUMENT STRATEGY:\n- For listing/cataloguing documents: use the document index already in your prompt — no tool calls needed.\n- For overview/summary requests: use get_table_of_contents first, then read key sections with read_document.\n- For specific questions: use search_inside_documents to find relevant sections, then read those sections with read_document.\n- For translation, deep analysis, or detailed summaries of a single document: use read_document with no ranges to load the complete text.\n- For extracting structured findings from passages: use read_document with digest=true or search_inside_documents with digest=true.\n- Never search for meta-queries like \"summary\", \"overview\", or \"all documents\" — search for the actual subject matter.\n\nFORMATTING:\n- Start your answer directly with the content — never open with a description of what you searched for or read (e.g. never write \"Searching for X\", \"Reading Y\", \"I found Z documents\" as the first lines of an answer).\n- Use markdown: headings, bold, bullet points, numbered lists\n- Main conclusion first, followed by supporting points\n- Bullet points for lists of discrete items\n- Numbering for sequential steps or prioritized items\n- Bold text for critical conclusions or decision points\n\nTOOL CALLING:\n- Your job is to gather context by calling tools, then answer only once every reasonable tool call has been made. Do not give a final answer while there is still relevant context you could retrieve.\n- Always invoke tools using the tool-calling mechanism. NEVER write text that describes or simulates a tool call (e.g. never write \"Searching for X...\", \"Reading document Y...\", \"Calling search_inside_documents\" as prose — actually call the tool).\n- If you intend to search or read, issue the tool call immediately. Do not narrate your intent first.\n\nEFFICIENCY:\n1. Before each step, review the results of prior steps. Adapt your approach based on what you learned — if a call was rejected or returned poor results, adjust your strategy.\n2. Call multiple tools in parallel when a query has several aspects.\n3. NEVER repeat a tool call with the same arguments.\n4. Use targeted queries and narrow page ranges per retrieval call.\n5. Stop when you have sufficient evidence — do not over-research."
              *     }
              */
             Agents: components['schemas']['AgentsConfig'];
@@ -2595,7 +2746,7 @@ interface components {
              * @default {
              *       "API_TYPE": "remote",
              *       "ENABLE_THINKING": true,
-             *       "MODEL_NAME": "Premium",
+             *       "MODEL_NAME": "GLM5@Fireworks",
              *       "SYSTEM_INSTRUCTION": "You are a code execution agent. You write and run code to accomplish tasks.\n\nYou have access to an execute_code tool that runs code in a sandboxed Docker container.\n\nThe sandbox has:\n- Python 3.12 with numpy, pandas, matplotlib, requests, beautifulsoup4,\n  httpx, pillow, sympy, pyyaml (plus uv for installing more)\n- Node.js 22 with TypeScript (ts-node) and npm\n- Bash with git, curl, wget, jq, sqlite3, build-essential\n- Network access (can pip/npm install additional packages)\n\nInstructions:\n1. Write clean, correct code to accomplish the user's task\n2. Always call execute_code to run your code — never guess the output\n3. If execution errors, analyze the traceback, fix the code, and retry\n4. Once you have the correct output, respond with ONLY the final result\n\nKeep code simple and direct. Prefer Python unless the task specifically requires another language.",
              *       "TEMPERATURE": 0.2,
              *       "MAX_TOKENS": 8000,
@@ -3077,7 +3228,7 @@ interface components {
             /**
              * Model Name
              * @description Model for code generation. Should be a strong coding model.
-             * @default Premium
+             * @default GLM5@Fireworks
              */
             MODEL_NAME: string;
             /**
@@ -3254,6 +3405,26 @@ interface components {
             /** Message */
             message: string;
         };
+        /** ConnectorCatalogRead */
+        ConnectorCatalogRead: {
+            /**
+             * Id
+             * Format: uuid
+             */
+            id: string;
+            /** Vendor Key */
+            vendor_key: string;
+            /** Display Name */
+            display_name: string;
+            /** Description */
+            description: string;
+            /** Icon Url */
+            icon_url: string | null;
+            /** Mcp Server Alias */
+            mcp_server_alias: string;
+            /** Requires Per User Auth */
+            requires_per_user_auth: boolean;
+        };
         /**
          * ConsolidatedHealthResponse
          * @description Consolidated health response containing all system status and version information
@@ -3362,6 +3533,22 @@ interface components {
             /** Title */
             title: string;
         };
+        /**
+         * ConversationTitleUpdatedMessage
+         * @description Conversation title regenerated server-side — frontend should refresh.
+         */
+        ConversationTitleUpdatedMessage: {
+            /**
+             * Type
+             * @default conversation.title_updated
+             * @constant
+             */
+            type: 'conversation.title_updated';
+            /** Conversation Ext Id */
+            conversation_ext_id: string;
+            /** Title */
+            title: string;
+        };
         /** CopyDocumentResult */
         CopyDocumentResult: {
             /** Source Doc Ext Id */
@@ -5170,7 +5357,7 @@ interface components {
              * Status
              * @enum {string}
              */
-            status: 'online' | 'unknown';
+            status: 'online' | 'offline' | 'unknown';
             /** Timestamp */
             timestamp: string;
         };
@@ -7420,6 +7607,32 @@ interface components {
             /** Items */
             items?: components['schemas']['InitedUploadItem'][];
         };
+        /** UserConnectorRead */
+        UserConnectorRead: {
+            /**
+             * Id
+             * Format: uuid
+             */
+            id: string;
+            /** Vendor Key */
+            vendor_key: string;
+            /** Display Name */
+            display_name: string;
+            /** Icon Url */
+            icon_url: string | null;
+            /**
+             * Connected At
+             * Format: date-time
+             */
+            connected_at: string;
+            /** Vendor User Identity */
+            vendor_user_identity: string | null;
+            /**
+             * Is Connected
+             * @default true
+             */
+            is_connected: boolean;
+        };
         /**
          * UserDailyUsageResponse
          * @description Today's deployment-wide credit spend tagged with the current user.
@@ -7647,6 +7860,11 @@ interface components {
              * @default false
              */
             show_mcp_connectors: boolean;
+            /**
+             * Show Hints
+             * @default true
+             */
+            show_hints: boolean;
             /**
              * Use S3 Direct Upload
              * @default false
@@ -7704,6 +7922,8 @@ interface components {
             show_agent_sessions?: boolean | null;
             /** Show Mcp Connectors */
             show_mcp_connectors?: boolean | null;
+            /** Show Hints */
+            show_hints?: boolean | null;
             /** Use S3 Direct Upload */
             use_s3_direct_upload?: boolean | null;
             /** Hide Online Status */
@@ -7872,6 +8092,7 @@ interface components {
             task_update?: components['schemas']['TaskUpdateMessage'] | null;
             batch_complete?: components['schemas']['BatchCompleteMessage'] | null;
             response_complete?: components['schemas']['ResponseCompleteMessage'] | null;
+            conversation_title_updated?: components['schemas']['ConversationTitleUpdatedMessage'] | null;
             notification?: components['schemas']['NotificationResponse'] | null;
             auth?: components['schemas']['AuthMessage'] | null;
             send_message?: components['schemas']['SendMessageRequest'] | null;
@@ -11050,6 +11271,175 @@ interface operations {
             };
         };
     };
+    list_connectors: {
+        parameters: {
+            query?: never;
+            header?: never;
+            path?: never;
+            cookie?: never;
+        };
+        requestBody?: never;
+        responses: {
+            /** @description Successful Response */
+            200: {
+                headers: {
+                    [name: string]: unknown;
+                };
+                content: {
+                    'application/json': components['schemas']['ConnectorCatalogRead'][];
+                };
+            };
+        };
+    };
+    list_my_connectors: {
+        parameters: {
+            query?: never;
+            header?: never;
+            path?: never;
+            cookie?: never;
+        };
+        requestBody?: never;
+        responses: {
+            /** @description Successful Response */
+            200: {
+                headers: {
+                    [name: string]: unknown;
+                };
+                content: {
+                    'application/json': components['schemas']['UserConnectorRead'][];
+                };
+            };
+        };
+    };
+    get_connector_status: {
+        parameters: {
+            query?: never;
+            header?: never;
+            path: {
+                vendor_key: string;
+            };
+            cookie?: never;
+        };
+        requestBody?: never;
+        responses: {
+            /** @description Successful Response */
+            200: {
+                headers: {
+                    [name: string]: unknown;
+                };
+                content: {
+                    'application/json': {
+                        [key: string]: unknown;
+                    };
+                };
+            };
+            /** @description Validation Error */
+            422: {
+                headers: {
+                    [name: string]: unknown;
+                };
+                content: {
+                    'application/json': components['schemas']['HTTPValidationError'];
+                };
+            };
+        };
+    };
+    authorize_connector: {
+        parameters: {
+            query?: never;
+            header?: never;
+            path: {
+                vendor_key: string;
+            };
+            cookie?: never;
+        };
+        requestBody?: never;
+        responses: {
+            /** @description Successful Response */
+            200: {
+                headers: {
+                    [name: string]: unknown;
+                };
+                content: {
+                    'application/json': {
+                        [key: string]: unknown;
+                    };
+                };
+            };
+            /** @description Validation Error */
+            422: {
+                headers: {
+                    [name: string]: unknown;
+                };
+                content: {
+                    'application/json': components['schemas']['HTTPValidationError'];
+                };
+            };
+        };
+    };
+    oauth_callback: {
+        parameters: {
+            query: {
+                code: string;
+                state: string;
+            };
+            header?: never;
+            path: {
+                vendor_key: string;
+            };
+            cookie?: never;
+        };
+        requestBody?: never;
+        responses: {
+            /** @description Successful Response */
+            200: {
+                headers: {
+                    [name: string]: unknown;
+                };
+                content: {
+                    'application/json': unknown;
+                };
+            };
+            /** @description Validation Error */
+            422: {
+                headers: {
+                    [name: string]: unknown;
+                };
+                content: {
+                    'application/json': components['schemas']['HTTPValidationError'];
+                };
+            };
+        };
+    };
+    disconnect_connector: {
+        parameters: {
+            query?: never;
+            header?: never;
+            path: {
+                vendor_key: string;
+            };
+            cookie?: never;
+        };
+        requestBody?: never;
+        responses: {
+            /** @description Successful Response */
+            204: {
+                headers: {
+                    [name: string]: unknown;
+                };
+                content?: never;
+            };
+            /** @description Validation Error */
+            422: {
+                headers: {
+                    [name: string]: unknown;
+                };
+                content: {
+                    'application/json': components['schemas']['HTTPValidationError'];
+                };
+            };
+        };
+    };
     create_response: {
         parameters: {
             query?: never;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@arbidocs/client",
-  "version": "0.3.71",
+  "version": "0.3.72",
   "description": "TypeScript SDK for the ARBI API — zero-knowledge auth, E2E encryption, and type-safe REST client",
   "type": "module",
   "main": "dist/index.cjs",