@arbidocs/client 0.3.78 → 0.3.79

package/dist/index.d.cts

@@ -709,6 +709,61 @@ interface paths {
         patch?: never;
         trace?: never;
     };
+    '/v1/user/restore-account': {
+        parameters: {
+            query?: never;
+            header?: never;
+            path?: never;
+            cookie?: never;
+        };
+        get?: never;
+        put?: never;
+        /**
+         * Admin Restore Account
+         * @description Restore a soft-deleted account by clearing deleted_at and resetting token_version.
+         *
+         *     Authenticated via the support API key (header ``X-API-Key``).
+         *     After restoration the user can log in normally again.
+         */
+        post: operations['admin_restore_account'];
+        delete?: never;
+        options?: never;
+        head?: never;
+        patch?: never;
+        trace?: never;
+    };
+    '/v1/user/request-deletion': {
+        parameters: {
+            query?: never;
+            header?: never;
+            path?: never;
+            cookie?: never;
+        };
+        get?: never;
+        put?: never;
+        /**
+         * Request Deletion
+         * @description Soft-delete the calling user's account.
+         *
+         *     Immediately closes the account:
+         *     - Sets ``deleted_at = now()`` on the user row
+         *     - Increments ``token_version`` to invalidate all existing JWT tokens
+         *     - Deletes all active Redis sessions (logged out on all devices)
+         *     - Sends a best-effort confirmation email
+         *
+         *     Blockers (returns 422 if any apply):
+         *     - User has an active Stripe subscription (must cancel first)
+         *     - User is the sole admin of a workspace with other members
+         *
+         *     Recovery is admin-only; there is no self-service cancel.
+         */
+        post: operations['request_deletion'];
+        delete?: never;
+        options?: never;
+        head?: never;
+        patch?: never;
+        trace?: never;
+    };
     '/v1/user/products': {
         parameters: {
             query?: never;
@@ -2215,6 +2270,43 @@ interface components {
             /** Session Pubkey B64 */
             session_pubkey_b64?: string | null;
         };
+        /**
+         * AgentStepDeltaEvent
+         * @description Incremental narration for an in-progress agent step (event: arbi.agent_step_delta).
+         *
+         *     Streamed live as the model generates its narration for a turn, BEFORE that
+         *     turn resolves into a tool call or an answer. The frontend appends `delta` to
+         *     the `focus` of the step with the matching `index` (creating a bare step if
+         *     that index hasn't been seen yet), giving a live play-by-play inside the
+         *     steps block. This channel is narration only — the final answer is delivered
+         *     separately and authoritatively via response.output_text.delta, never here.
+         *
+         *     Example:
+         *         {"type": "arbi.agent_step_delta", "index": 2, "delta": "Searching the "}
+         */
+        AgentStepDeltaEvent: {
+            /**
+             * T
+             * @description Seconds elapsed since stream start.
+             */
+            t?: number | null;
+            /**
+             * Type
+             * @default arbi.agent_step_delta
+             * @constant
+             */
+            type: 'arbi.agent_step_delta';
+            /**
+             * Index
+             * @description Step index this narration belongs to (matches AgentStepEvent.index).
+             */
+            index: number;
+            /**
+             * Delta
+             * @description Incremental focus/narration text to append to the step.
+             */
+            delta: string;
+        };
         /**
          * AgentStepEvent
          * @description A single agent step with a sequential index.
@@ -2275,19 +2367,14 @@ interface components {
             index: number;
             /**
              * Step
-             * @description Lifecycle step (planning, answering, reviewing). Absent for tool calls.
+             * @description Lifecycle step. Absent (None) for tool-call steps, which carry `detail` instead.
              */
-            step?: string | null;
+            step?: ('goal' | 'skill' | 'planning' | 'tool_progress' | 'goal_progress' | 'answering' | 'reviewing' | 'evaluation') | null;
             /**
              * Label
              * @description Display label for the step. Backend-driven, no frontend mapping needed.
              */
             label?: string | null;
-            /**
-             * Icon
-             * @description Lucide icon name for the step (e.g. 'search'). Backend-driven, no frontend mapping needed.
-             */
-            icon?: string | null;
             /**
              * Focus
              * @description Agent's current focus (single sentence). Present on tool call steps.
@@ -2368,6 +2455,12 @@ interface components {
              * @default false
              */
             PLANNING_ENABLED: boolean;
+            /**
+             * Deep Research Enabled
+             * @description Include the deep_research tool so the agent can delegate a focused research topic to a nested retrieval sub-agent (document + web search), keeping the main context clean while citations from the sub-agent's sources flow back.
+             * @default false
+             */
+            DEEP_RESEARCH_ENABLED: boolean;
             /**
              * Suggested Queries
              * @description Generate a single suggested follow-up query after each response.
@@ -2422,18 +2515,6 @@ interface components {
              * @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.
@@ -2506,7 +2587,7 @@ interface components {
              * @description System prompt for the agent. Dynamic context is appended automatically.
              * @default 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.
              *
-             *     IMPORTANT: 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.
+             *     IMPORTANT: 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's question may be answered by workspace documents, call search_inside_documents, read_document, or get_table_of_contents — never answer from memory.
              *
              *     When 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.
              *
@@ -2531,8 +2612,8 @@ interface components {
              *
              *     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.
+             *     - Always invoke tools using the tool-calling mechanism. A short note about what you're doing is welcome and helps the user follow along — but it must accompany an actual tool call in the same turn; it is never a substitute for one. Writing "Searching for X..." or "Reading document Y..." and stopping there, with no tool call emitted, leaves the work undone.
+             *     - If you intend to search or read, issue the tool call in that same turn.
              *
              *     EFFICIENCY:
              *     1. 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.
@@ -2589,6 +2670,7 @@ interface components {
              *       },
              *       "MCP_TOOLS": [],
              *       "PLANNING_ENABLED": false,
+             *       "DEEP_RESEARCH_ENABLED": false,
              *       "SUGGESTED_QUERIES": false,
              *       "ARTIFACTS_ENABLED": false,
              *       "VISION_ENABLED": false,
@@ -2598,8 +2680,6 @@ interface components {
              *       "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.",
@@ -2611,7 +2691,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- 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."
+             *       "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's question may be answered by workspace documents, call search_inside_documents, 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. A short note about what you're doing is welcome and helps the user follow along — but it must accompany an actual tool call in the same turn; it is never a substitute for one. Writing \"Searching for X...\" or \"Reading document Y...\" and stopping there, with no tool call emitted, leaves the work undone.\n- If you intend to search or read, issue the tool call in that same turn.\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'];
@@ -2791,7 +2871,7 @@ interface components {
              * @default {
              *       "API_TYPE": "remote",
              *       "ENABLE_THINKING": true,
-             *       "MODEL_NAME": "GLM5@Fireworks",
+             *       "MODEL_NAME": "Premium",
              *       "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,
@@ -2923,6 +3003,47 @@ interface components {
              */
             last_input_tokens: number;
         };
+        /**
+         * ArbiErrorEvent
+         * @description ``arbi.error`` — a structured mid-stream error (e.g. AI-quota exceeded).
+         *
+         *     Flat payload so the client can branch on ``code`` (e.g. QUOTA_EXCEEDED →
+         *     upgrade modal) without unwrapping, instead of treating it as a retryable
+         *     ``response.failed``. Accumulated for GET-poll reconnects.
+         */
+        ArbiErrorEvent: {
+            /**
+             * Type
+             * @default arbi.error
+             * @constant
+             */
+            type: 'arbi.error';
+            /**
+             * Code
+             * @description Error code, e.g. 'QUOTA_EXCEEDED'
+             */
+            code: string;
+            /**
+             * Message
+             * @description Human-readable error message
+             */
+            message: string;
+            /**
+             * Spend
+             * @description Current spend in USD (QUOTA_EXCEEDED)
+             */
+            spend?: number | null;
+            /**
+             * Budget
+             * @description Budget cap in USD (QUOTA_EXCEEDED)
+             */
+            budget?: number | null;
+            /**
+             * Project Ext Id
+             * @description Affected project external id (QUOTA_EXCEEDED)
+             */
+            project_ext_id?: string | null;
+        };
         /**
          * ArtifactEvent
          * @description A generated artifact (document/draft) for the artifact panel.
@@ -3278,7 +3399,7 @@ interface components {
             /**
              * Model Name
              * @description Model for code generation. Should be a strong coding model.
-             * @default GLM5@Fireworks
+             * @default Premium
              */
             MODEL_NAME: string;
             /**
@@ -4471,6 +4592,33 @@ interface components {
              */
             summary?: string | null;
         };
+        /**
+         * GoalProgressDetail
+         * @description Detail for one /goal acceptance-criterion verdict (step: goal_progress).
+         */
+        GoalProgressDetail: {
+            /**
+             * Criterion
+             * @description Criterion id (e.g. 'c1')
+             */
+            criterion: string;
+            /**
+             * Text
+             * @description Criterion text
+             */
+            text: string;
+            /**
+             * Status
+             * @description Verdict for this criterion
+             * @enum {string}
+             */
+            status: 'met' | 'unmet' | 'absent_from_corpus';
+            /**
+             * Note
+             * @description Judge note / concrete gap for this criterion
+             */
+            note: string;
+        };
         /** HTTPValidationError */
         HTTPValidationError: {
             /** Detail */
@@ -5839,6 +5987,14 @@ interface components {
             /** Users */
             users: components['schemas']['RemoveWorkspaceUserItem'][];
         };
+        /**
+         * RequestDeletionResponse
+         * @description Response for POST /v1/user/request-deletion.
+         */
+        RequestDeletionResponse: {
+            /** Detail */
+            detail: string;
+        };
         /** RequestEmailChangeRequest */
         RequestEmailChangeRequest: {
             /**
@@ -6716,8 +6872,10 @@ interface components {
             response_output_item_added?: components['schemas']['ResponseOutputItemAddedEvent'] | null;
             response_content_part_added?: components['schemas']['ResponseContentPartAddedEvent'] | null;
             agent_step?: components['schemas']['AgentStepEvent'] | null;
+            agent_step_delta?: components['schemas']['AgentStepDeltaEvent'] | null;
             user_input_request?: components['schemas']['UserInputRequestEvent'] | null;
             user_message?: components['schemas']['UserMessageEvent'] | null;
+            arbi_error?: components['schemas']['ArbiErrorEvent'] | null;
             response_output_text_delta?: components['schemas']['ResponseOutputTextDeltaEvent'] | null;
             response_output_text_done?: components['schemas']['ResponseOutputTextDoneEvent'] | null;
             response_output_item_done?: components['schemas']['ResponseOutputItemDoneEvent'] | null;
@@ -6743,6 +6901,7 @@ interface components {
             detail_ask_user?: components['schemas']['AskUserDetail'] | null;
             detail_evaluation?: components['schemas']['EvaluationDetail'] | null;
             detail_tool_progress?: components['schemas']['ToolProgressDetail'] | null;
+            detail_goal_progress?: components['schemas']['GoalProgressDetail'] | null;
         };
         /**
          * SSOConfigResponse
@@ -9446,6 +9605,62 @@ interface operations {
             };
         };
     };
+    admin_restore_account: {
+        parameters: {
+            query: {
+                /** @description Email of the account to restore */
+                email: string;
+            };
+            header?: {
+                'x-api-key'?: string;
+            };
+            path?: never;
+            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'];
+                };
+            };
+        };
+    };
+    request_deletion: {
+        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']['RequestDeletionResponse'];
+                };
+            };
+        };
+    };
     get_products: {
         parameters: {
             query?: never;

package/dist/index.d.ts

@@ -709,6 +709,61 @@ interface paths {
         patch?: never;
         trace?: never;
     };
+    '/v1/user/restore-account': {
+        parameters: {
+            query?: never;
+            header?: never;
+            path?: never;
+            cookie?: never;
+        };
+        get?: never;
+        put?: never;
+        /**
+         * Admin Restore Account
+         * @description Restore a soft-deleted account by clearing deleted_at and resetting token_version.
+         *
+         *     Authenticated via the support API key (header ``X-API-Key``).
+         *     After restoration the user can log in normally again.
+         */
+        post: operations['admin_restore_account'];
+        delete?: never;
+        options?: never;
+        head?: never;
+        patch?: never;
+        trace?: never;
+    };
+    '/v1/user/request-deletion': {
+        parameters: {
+            query?: never;
+            header?: never;
+            path?: never;
+            cookie?: never;
+        };
+        get?: never;
+        put?: never;
+        /**
+         * Request Deletion
+         * @description Soft-delete the calling user's account.
+         *
+         *     Immediately closes the account:
+         *     - Sets ``deleted_at = now()`` on the user row
+         *     - Increments ``token_version`` to invalidate all existing JWT tokens
+         *     - Deletes all active Redis sessions (logged out on all devices)
+         *     - Sends a best-effort confirmation email
+         *
+         *     Blockers (returns 422 if any apply):
+         *     - User has an active Stripe subscription (must cancel first)
+         *     - User is the sole admin of a workspace with other members
+         *
+         *     Recovery is admin-only; there is no self-service cancel.
+         */
+        post: operations['request_deletion'];
+        delete?: never;
+        options?: never;
+        head?: never;
+        patch?: never;
+        trace?: never;
+    };
     '/v1/user/products': {
         parameters: {
             query?: never;
@@ -2215,6 +2270,43 @@ interface components {
             /** Session Pubkey B64 */
             session_pubkey_b64?: string | null;
         };
+        /**
+         * AgentStepDeltaEvent
+         * @description Incremental narration for an in-progress agent step (event: arbi.agent_step_delta).
+         *
+         *     Streamed live as the model generates its narration for a turn, BEFORE that
+         *     turn resolves into a tool call or an answer. The frontend appends `delta` to
+         *     the `focus` of the step with the matching `index` (creating a bare step if
+         *     that index hasn't been seen yet), giving a live play-by-play inside the
+         *     steps block. This channel is narration only — the final answer is delivered
+         *     separately and authoritatively via response.output_text.delta, never here.
+         *
+         *     Example:
+         *         {"type": "arbi.agent_step_delta", "index": 2, "delta": "Searching the "}
+         */
+        AgentStepDeltaEvent: {
+            /**
+             * T
+             * @description Seconds elapsed since stream start.
+             */
+            t?: number | null;
+            /**
+             * Type
+             * @default arbi.agent_step_delta
+             * @constant
+             */
+            type: 'arbi.agent_step_delta';
+            /**
+             * Index
+             * @description Step index this narration belongs to (matches AgentStepEvent.index).
+             */
+            index: number;
+            /**
+             * Delta
+             * @description Incremental focus/narration text to append to the step.
+             */
+            delta: string;
+        };
         /**
          * AgentStepEvent
          * @description A single agent step with a sequential index.
@@ -2275,19 +2367,14 @@ interface components {
             index: number;
             /**
              * Step
-             * @description Lifecycle step (planning, answering, reviewing). Absent for tool calls.
+             * @description Lifecycle step. Absent (None) for tool-call steps, which carry `detail` instead.
              */
-            step?: string | null;
+            step?: ('goal' | 'skill' | 'planning' | 'tool_progress' | 'goal_progress' | 'answering' | 'reviewing' | 'evaluation') | null;
             /**
              * Label
              * @description Display label for the step. Backend-driven, no frontend mapping needed.
              */
             label?: string | null;
-            /**
-             * Icon
-             * @description Lucide icon name for the step (e.g. 'search'). Backend-driven, no frontend mapping needed.
-             */
-            icon?: string | null;
             /**
              * Focus
              * @description Agent's current focus (single sentence). Present on tool call steps.
@@ -2368,6 +2455,12 @@ interface components {
              * @default false
              */
             PLANNING_ENABLED: boolean;
+            /**
+             * Deep Research Enabled
+             * @description Include the deep_research tool so the agent can delegate a focused research topic to a nested retrieval sub-agent (document + web search), keeping the main context clean while citations from the sub-agent's sources flow back.
+             * @default false
+             */
+            DEEP_RESEARCH_ENABLED: boolean;
             /**
              * Suggested Queries
              * @description Generate a single suggested follow-up query after each response.
@@ -2422,18 +2515,6 @@ interface components {
              * @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.
@@ -2506,7 +2587,7 @@ interface components {
              * @description System prompt for the agent. Dynamic context is appended automatically.
              * @default 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.
              *
-             *     IMPORTANT: 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.
+             *     IMPORTANT: 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's question may be answered by workspace documents, call search_inside_documents, read_document, or get_table_of_contents — never answer from memory.
              *
              *     When 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.
              *
@@ -2531,8 +2612,8 @@ interface components {
              *
              *     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.
+             *     - Always invoke tools using the tool-calling mechanism. A short note about what you're doing is welcome and helps the user follow along — but it must accompany an actual tool call in the same turn; it is never a substitute for one. Writing "Searching for X..." or "Reading document Y..." and stopping there, with no tool call emitted, leaves the work undone.
+             *     - If you intend to search or read, issue the tool call in that same turn.
              *
              *     EFFICIENCY:
              *     1. 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.
@@ -2589,6 +2670,7 @@ interface components {
              *       },
              *       "MCP_TOOLS": [],
              *       "PLANNING_ENABLED": false,
+             *       "DEEP_RESEARCH_ENABLED": false,
              *       "SUGGESTED_QUERIES": false,
              *       "ARTIFACTS_ENABLED": false,
              *       "VISION_ENABLED": false,
@@ -2598,8 +2680,6 @@ interface components {
              *       "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.",
@@ -2611,7 +2691,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- 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."
+             *       "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's question may be answered by workspace documents, call search_inside_documents, 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. A short note about what you're doing is welcome and helps the user follow along — but it must accompany an actual tool call in the same turn; it is never a substitute for one. Writing \"Searching for X...\" or \"Reading document Y...\" and stopping there, with no tool call emitted, leaves the work undone.\n- If you intend to search or read, issue the tool call in that same turn.\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'];
@@ -2791,7 +2871,7 @@ interface components {
              * @default {
              *       "API_TYPE": "remote",
              *       "ENABLE_THINKING": true,
-             *       "MODEL_NAME": "GLM5@Fireworks",
+             *       "MODEL_NAME": "Premium",
              *       "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,
@@ -2923,6 +3003,47 @@ interface components {
              */
             last_input_tokens: number;
         };
+        /**
+         * ArbiErrorEvent
+         * @description ``arbi.error`` — a structured mid-stream error (e.g. AI-quota exceeded).
+         *
+         *     Flat payload so the client can branch on ``code`` (e.g. QUOTA_EXCEEDED →
+         *     upgrade modal) without unwrapping, instead of treating it as a retryable
+         *     ``response.failed``. Accumulated for GET-poll reconnects.
+         */
+        ArbiErrorEvent: {
+            /**
+             * Type
+             * @default arbi.error
+             * @constant
+             */
+            type: 'arbi.error';
+            /**
+             * Code
+             * @description Error code, e.g. 'QUOTA_EXCEEDED'
+             */
+            code: string;
+            /**
+             * Message
+             * @description Human-readable error message
+             */
+            message: string;
+            /**
+             * Spend
+             * @description Current spend in USD (QUOTA_EXCEEDED)
+             */
+            spend?: number | null;
+            /**
+             * Budget
+             * @description Budget cap in USD (QUOTA_EXCEEDED)
+             */
+            budget?: number | null;
+            /**
+             * Project Ext Id
+             * @description Affected project external id (QUOTA_EXCEEDED)
+             */
+            project_ext_id?: string | null;
+        };
         /**
          * ArtifactEvent
          * @description A generated artifact (document/draft) for the artifact panel.
@@ -3278,7 +3399,7 @@ interface components {
             /**
              * Model Name
              * @description Model for code generation. Should be a strong coding model.
-             * @default GLM5@Fireworks
+             * @default Premium
              */
             MODEL_NAME: string;
             /**
@@ -4471,6 +4592,33 @@ interface components {
              */
             summary?: string | null;
         };
+        /**
+         * GoalProgressDetail
+         * @description Detail for one /goal acceptance-criterion verdict (step: goal_progress).
+         */
+        GoalProgressDetail: {
+            /**
+             * Criterion
+             * @description Criterion id (e.g. 'c1')
+             */
+            criterion: string;
+            /**
+             * Text
+             * @description Criterion text
+             */
+            text: string;
+            /**
+             * Status
+             * @description Verdict for this criterion
+             * @enum {string}
+             */
+            status: 'met' | 'unmet' | 'absent_from_corpus';
+            /**
+             * Note
+             * @description Judge note / concrete gap for this criterion
+             */
+            note: string;
+        };
         /** HTTPValidationError */
         HTTPValidationError: {
             /** Detail */
@@ -5839,6 +5987,14 @@ interface components {
             /** Users */
             users: components['schemas']['RemoveWorkspaceUserItem'][];
         };
+        /**
+         * RequestDeletionResponse
+         * @description Response for POST /v1/user/request-deletion.
+         */
+        RequestDeletionResponse: {
+            /** Detail */
+            detail: string;
+        };
         /** RequestEmailChangeRequest */
         RequestEmailChangeRequest: {
             /**
@@ -6716,8 +6872,10 @@ interface components {
             response_output_item_added?: components['schemas']['ResponseOutputItemAddedEvent'] | null;
             response_content_part_added?: components['schemas']['ResponseContentPartAddedEvent'] | null;
             agent_step?: components['schemas']['AgentStepEvent'] | null;
+            agent_step_delta?: components['schemas']['AgentStepDeltaEvent'] | null;
             user_input_request?: components['schemas']['UserInputRequestEvent'] | null;
             user_message?: components['schemas']['UserMessageEvent'] | null;
+            arbi_error?: components['schemas']['ArbiErrorEvent'] | null;
             response_output_text_delta?: components['schemas']['ResponseOutputTextDeltaEvent'] | null;
             response_output_text_done?: components['schemas']['ResponseOutputTextDoneEvent'] | null;
             response_output_item_done?: components['schemas']['ResponseOutputItemDoneEvent'] | null;
@@ -6743,6 +6901,7 @@ interface components {
             detail_ask_user?: components['schemas']['AskUserDetail'] | null;
             detail_evaluation?: components['schemas']['EvaluationDetail'] | null;
             detail_tool_progress?: components['schemas']['ToolProgressDetail'] | null;
+            detail_goal_progress?: components['schemas']['GoalProgressDetail'] | null;
         };
         /**
          * SSOConfigResponse
@@ -9446,6 +9605,62 @@ interface operations {
             };
         };
     };
+    admin_restore_account: {
+        parameters: {
+            query: {
+                /** @description Email of the account to restore */
+                email: string;
+            };
+            header?: {
+                'x-api-key'?: string;
+            };
+            path?: never;
+            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'];
+                };
+            };
+        };
+    };
+    request_deletion: {
+        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']['RequestDeletionResponse'];
+                };
+            };
+        };
+    };
     get_products: {
         parameters: {
             query?: never;

package/package.json

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