@arbidocs/client 0.3.156 → 0.3.158

package/dist/index.d.cts

@@ -2372,6 +2372,43 @@ interface paths {
         patch?: never;
         trace?: never;
     };
+    '/v1/agents/inbound-email': {
+        parameters: {
+            query?: never;
+            header?: never;
+            path?: never;
+            cookie?: never;
+        };
+        get?: never;
+        put?: never;
+        /**
+         * Inbound Email
+         * @description Wake the sender's Assistant on a forwarded inbound email.
+         *
+         *     The email gateway (a ``service_account`` user) posts a received email here; we
+         *     run the sender's own persistent agent against it natively and email the reply
+         *     back. This endpoint is the trust boundary — it wakes an arbitrary user's agent,
+         *     which the normal parent-only DM gate would otherwise forbid — so it is gated on
+         *     ``get_service_account_dependency`` (the gateway's bearer JWT).
+         *
+         *     The gateway sends ``email_body.txt`` as one file (the email text, for prompt
+         *     building) and, from an updated gateway, ``original.eml`` — the original raw
+         *     RFC822 bytes exactly as received over SMTP, every header intact — which we
+         *     archive verbatim instead of reconstructing a lossier copy from parsed fields.
+         *     Any other file is a pre-extracted attachment, forwarded by an older gateway
+         *     that doesn't send ``original.eml`` yet; process_inbound_email falls back to
+         *     using those when there's no raw copy to let the parser explode instead. We
+         *     read every file's bytes here (``UploadFile`` objects do not survive past the
+         *     response), verify the sender is known, then hand the work to a background
+         *     task (assistant -> workspace -> upload -> wake -> reply).
+         */
+        post: operations['inbound_email'];
+        delete?: never;
+        options?: never;
+        head?: never;
+        patch?: never;
+        trace?: never;
+    };
     '/v1/tasks': {
         parameters: {
             query?: never;
@@ -3262,6 +3299,14 @@ interface components {
          *     recipient's current session (identified by this X25519 public key). The workspace
          *     key is stored in that session's Redis entry and the workspaceusers row expires when
          *     the session expires. Omit for a permanent grant (default behaviour).
+         *
+         *     confirm_invite (default False): an email that isn't a registered user is never
+         *     invited on a call with this unset — it's silently left out of the response (same
+         *     as any other not-found email), so the caller can diff the response against the
+         *     emails it sent and ask the owner to confirm before anything is emailed. Only a
+         *     follow-up call with this set to true for those specific emails actually sends the
+         *     invite and deposits the pending workspace-share grant. Without this gate, sharing
+         *     would email and grant future access to a typo'd address with no chance to back out.
          */
         AddWorkspaceUsersRequest: {
             /** Emails */
@@ -3274,6 +3319,8 @@ interface components {
             workspace_ext_id?: string | null;
             /** Session Pubkey B64 */
             session_pubkey_b64?: string | null;
+            /** Confirm Invite */
+            confirm_invite?: boolean | null;
         };
         /**
          * AgentControlStateEvent
@@ -3538,7 +3585,7 @@ interface components {
             /**
              * Planning Enabled
              * @description Include the create_plan tool so the agent can generate a research plan when it deems a task complex enough. Plan approval is configured on PlanningLLM.
-             * @default false
+             * @default true
              */
             PLANNING_ENABLED: boolean;
             /**
@@ -3556,7 +3603,7 @@ interface components {
             /**
              * Suggested Queries
              * @description Generate a single suggested follow-up query after each response.
-             * @default false
+             * @default true
              */
             SUGGESTED_QUERIES: boolean;
             /**
@@ -3568,7 +3615,7 @@ interface components {
             /**
              * Image Enabled
              * @description Enable the create_image tool for generating and editing images (text→image, or editing reference images from the workspace) via a chat image model, stored as an image artifact displayed in the panel.
-             * @default false
+             * @default true
              */
             IMAGE_ENABLED: boolean;
             /**
@@ -3580,7 +3627,7 @@ interface components {
             /**
              * Conversation Search Enabled
              * @description Enable the search_conversations tool so the agent can semantically search past conversation messages in the workspace. Independent of the user-facing conversation search feature flag (show_conversation_search).
-             * @default false
+             * @default true
              */
             CONVERSATION_SEARCH_ENABLED: boolean;
             /**
@@ -3592,7 +3639,7 @@ interface components {
             /**
              * Facts Enabled
              * @description Workspace facts are readable AND writable by the agent: pinned core facts are injected into the prompt, and the agent gets the search_facts (recall) and create_fact (write) tools.
-             * @default false
+             * @default true
              */
             FACTS_ENABLED: boolean;
             /**
@@ -3758,7 +3805,7 @@ interface components {
              *     - Bold text for critical conclusions or decision points
              *
              *     TOOL CALLING:
-             *     - Your job is to gather the context the question needs, then answer. Do not give a final answer while there is relevant context you have not yet retrieved — but material already in your context counts as retrieved, and fetching it a second time is not progress.
+             *     - Your job is to gather the context the question needs, then answer. Do not give a final answer while there is relevant context you have not yet retrieved — but material already in your context counts as retrieved, and fetching it a second time is not progress. If the question touches a workspace document, always check the source — never answer from a past turn's reply alone.
              *     - Always invoke tools using the tool-calling mechanism. Say what a call is doing in its `focus` argument.
              *
              *     EFFICIENCY:
@@ -3805,7 +3852,7 @@ interface components {
             /**
              * Planning Enabled
              * @description Include the create_plan tool so the agent can generate a research plan when it deems a task complex enough. Plan approval is configured on PlanningLLM.
-             * @default false
+             * @default true
              */
             PLANNING_ENABLED: boolean;
             /**
@@ -3823,7 +3870,7 @@ interface components {
             /**
              * Suggested Queries
              * @description Generate a single suggested follow-up query after each response.
-             * @default false
+             * @default true
              */
             SUGGESTED_QUERIES: boolean;
             /**
@@ -3835,7 +3882,7 @@ interface components {
             /**
              * Image Enabled
              * @description Enable the create_image tool for generating and editing images (text→image, or editing reference images from the workspace) via a chat image model, stored as an image artifact displayed in the panel.
-             * @default false
+             * @default true
              */
             IMAGE_ENABLED: boolean;
             /**
@@ -3847,13 +3894,13 @@ interface components {
             /**
              * Conversation Search Enabled
              * @description Enable the search_conversations tool so the agent can semantically search past conversation messages in the workspace. Independent of the user-facing conversation search feature flag (show_conversation_search).
-             * @default false
+             * @default true
              */
             CONVERSATION_SEARCH_ENABLED: boolean;
             /**
              * Facts Enabled
              * @description Workspace facts are readable AND writable by the agent: pinned core facts are injected into the prompt, and the agent gets the search_facts (recall) and create_fact (write) tools.
-             * @default false
+             * @default true
              */
             FACTS_ENABLED: boolean;
             /**
@@ -3931,16 +3978,16 @@ interface components {
              *       "WEB_SEARCH_ENABLED": true,
              *       "RUN_CODE_ENABLED": true,
              *       "MCP_TOOLS": [],
-             *       "PLANNING_ENABLED": false,
+             *       "PLANNING_ENABLED": true,
              *       "DEEP_RESEARCH_ENABLED": true,
              *       "SUBAGENTS_ENABLED": true,
-             *       "SUGGESTED_QUERIES": false,
+             *       "SUGGESTED_QUERIES": true,
              *       "ARTIFACTS_ENABLED": false,
-             *       "IMAGE_ENABLED": false,
+             *       "IMAGE_ENABLED": true,
              *       "VISION_ENABLED": false,
-             *       "CONVERSATION_SEARCH_ENABLED": false,
+             *       "CONVERSATION_SEARCH_ENABLED": true,
              *       "PERSONAL_AGENT": false,
-             *       "FACTS_ENABLED": false,
+             *       "FACTS_ENABLED": true,
              *       "PERSIST_LEARNINGS": false,
              *       "SKILLS_ENABLED": false,
              *       "SKILL_CREATION": false,
@@ -3962,7 +4009,7 @@ interface components {
              *       "AGENT_MAX_RUN_TOKENS": 1500000,
              *       "AGENT_MAX_SUBAGENT_SPAWNS": 4,
              *       "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\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 lists every document with its Id, Title, Date, and Pages. The Subject field is a brief navigation label only — it does not contain enough information to answer questions about a document's content. 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\nREADING TOOL RESULTS:\nEvery retrieval result opens with a CAPTION line naming the call that produced it, what it contains, and what it does not (for example \"FULL CONTENT … complete verbatim text, all 10 pages\" or \"DIGEST … verbatim page text is NOT part of this result\"). The caption also tells you when you already retrieved that material earlier in this turn. Read it before choosing your next call — it is the record of what you already hold.\n\nDOCUMENT STRATEGY, in order:\n1. Listing or cataloguing documents: use the document index already in your prompt — no tool calls needed.\n2. Getting oriented in a document you have not read: call get_table_of_contents FIRST. It is cheap, returns the heading structure with page references, and tells you which pages actually matter. Do this before any read_document on a document longer than a few pages, rather than reading blind and then discovering the structure.\n3. Specific questions across several documents: search_inside_documents to locate the passages, then read_document on the pages it points to.\n4. Reading a document: read_document with page ranges for the sections you need, or with no ranges to load the complete text. A read with no ranges returns the WHOLE document — once you have it there is nothing further to retrieve from that document. Do not read it again, do not re-read ranges out of it, and do not ask for its outline afterwards.\n5. Prefer digest=true from the outset. It is the normal retrieval mode: findings with citations, compact context. Decide against it only when the task needs the exact words — translation, quotation, close reading of style or drafting. Choosing digest=false IS that decision, and it is final for that document: digest is a way of retrieving, not a way of processing text you already hold, so once you have loaded a document in full a digest of it is refused. Reason over the text you have.\n6. Open-ended investigative queries (\"find interesting things\", \"what's notable\", \"what stands out\", \"explore X\", \"what should I know about\", \"any findings\", \"anything unusual\", \"key insights\"): ALWAYS call search_inside_documents with multiple diverse queries covering different aspects of the documents before answering. The document index is never sufficient for investigative answers — you must retrieve actual content.\n7. 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.\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 the context the question needs, then answer. Do not give a final answer while there is relevant context you have not yet retrieved — but material already in your context counts as retrieved, and fetching it a second time is not progress.\n- Always invoke tools using the tool-calling mechanism. Say what a call is doing in its `focus` argument.\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, and never re-retrieve material you already hold — the caption on each result tells you what that is.\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\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 lists every document with its Id, Title, Date, and Pages. The Subject field is a brief navigation label only — it does not contain enough information to answer questions about a document's content. 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\nREADING TOOL RESULTS:\nEvery retrieval result opens with a CAPTION line naming the call that produced it, what it contains, and what it does not (for example \"FULL CONTENT … complete verbatim text, all 10 pages\" or \"DIGEST … verbatim page text is NOT part of this result\"). The caption also tells you when you already retrieved that material earlier in this turn. Read it before choosing your next call — it is the record of what you already hold.\n\nDOCUMENT STRATEGY, in order:\n1. Listing or cataloguing documents: use the document index already in your prompt — no tool calls needed.\n2. Getting oriented in a document you have not read: call get_table_of_contents FIRST. It is cheap, returns the heading structure with page references, and tells you which pages actually matter. Do this before any read_document on a document longer than a few pages, rather than reading blind and then discovering the structure.\n3. Specific questions across several documents: search_inside_documents to locate the passages, then read_document on the pages it points to.\n4. Reading a document: read_document with page ranges for the sections you need, or with no ranges to load the complete text. A read with no ranges returns the WHOLE document — once you have it there is nothing further to retrieve from that document. Do not read it again, do not re-read ranges out of it, and do not ask for its outline afterwards.\n5. Prefer digest=true from the outset. It is the normal retrieval mode: findings with citations, compact context. Decide against it only when the task needs the exact words — translation, quotation, close reading of style or drafting. Choosing digest=false IS that decision, and it is final for that document: digest is a way of retrieving, not a way of processing text you already hold, so once you have loaded a document in full a digest of it is refused. Reason over the text you have.\n6. Open-ended investigative queries (\"find interesting things\", \"what's notable\", \"what stands out\", \"explore X\", \"what should I know about\", \"any findings\", \"anything unusual\", \"key insights\"): ALWAYS call search_inside_documents with multiple diverse queries covering different aspects of the documents before answering. The document index is never sufficient for investigative answers — you must retrieve actual content.\n7. 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.\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 the context the question needs, then answer. Do not give a final answer while there is relevant context you have not yet retrieved — but material already in your context counts as retrieved, and fetching it a second time is not progress. If the question touches a workspace document, always check the source — never answer from a past turn's reply alone.\n- Always invoke tools using the tool-calling mechanism. Say what a call is doing in its `focus` argument.\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, and never re-retrieve material you already hold — the caption on each result tells you what that is.\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'];
@@ -4081,7 +4128,7 @@ interface components {
              *           }
              *         },
              *         {
-             *           "instruction": "What is the main subject or purpose of this document? Open with one concise phrase naming what it is and what it is about, in the form 'Email chain re the site access dispute between Acme and Byrne'. Then add one or two sentences of detail.",
+             *           "instruction": "What is the main subject or purpose of this document? Open with one concise noun phrase naming what it is and what it is about, in the form 'Email chain re the site access dispute between Acme and Byrne'. Never begin with a lead-in such as 'This document is', 'The document outlines', 'This is', or any similar sentence opener — start directly with the naming phrase. Then add one or two short sentences of key detail.",
              *           "name": "doc_subject",
              *           "tag_type": {
              *             "options": [],
@@ -6895,6 +6942,11 @@ interface components {
             tag_ext_ids: string[];
             /** Doc Ext Ids */
             doc_ext_ids: string[];
+            /**
+             * Overwrite
+             * @default false
+             */
+            overwrite: boolean;
         };
         /**
          * GenerateAnnotationsResponse
@@ -7256,6 +7308,7 @@ interface components {
             workspaces: {
                 [key: string]: unknown;
             }[];
+            pending_workspace_share?: components['schemas']['PendingWorkspaceShare'] | null;
         };
         /** LogoutResponse */
         LogoutResponse: {
@@ -8041,6 +8094,21 @@ interface components {
              */
             SKIP_DUPLICATES: boolean;
         };
+        /**
+         * PendingWorkspaceShare
+         * @description A workspace share from an invite whose Redis-deposited key expired
+         *     before this login, so the client must complete it itself by sending a
+         *     normal workspace_access_request to the inviter — the fields here are
+         *     exactly what that call needs (recipient + optional workspace lock).
+         */
+        PendingWorkspaceShare: {
+            /** Workspace Ext Id */
+            workspace_ext_id: string;
+            /** Inviter Ext Id */
+            inviter_ext_id: string;
+            /** Inviter Encryption Public Key */
+            inviter_encryption_public_key: string;
+        };
         /**
          * PersonalAgentDetail
          * @description Detail for a personal_agent tool call.
@@ -15204,6 +15272,44 @@ interface operations {
             };
         };
     };
+    inbound_email: {
+        parameters: {
+            query: {
+                /** @description The sender (a registered human user) */
+                user_email: string;
+                /** @description Email subject */
+                subject?: string;
+                /** @description Set when the gateway received mail at a workspace-scoped address (wrk-xxxxxxxx@<deployment>) — act in that specific workspace, requesting access first if the agent isn't a member yet. */
+                workspace_ext_id?: string | null;
+                /** @description The inbound email's own Message-ID header, if any */
+                message_id?: string;
+            };
+            header?: never;
+            path?: never;
+            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'];
+                };
+            };
+        };
+    };
     list_tasks: {
         parameters: {
             query?: never;

package/dist/index.d.ts

@@ -2372,6 +2372,43 @@ interface paths {
         patch?: never;
         trace?: never;
     };
+    '/v1/agents/inbound-email': {
+        parameters: {
+            query?: never;
+            header?: never;
+            path?: never;
+            cookie?: never;
+        };
+        get?: never;
+        put?: never;
+        /**
+         * Inbound Email
+         * @description Wake the sender's Assistant on a forwarded inbound email.
+         *
+         *     The email gateway (a ``service_account`` user) posts a received email here; we
+         *     run the sender's own persistent agent against it natively and email the reply
+         *     back. This endpoint is the trust boundary — it wakes an arbitrary user's agent,
+         *     which the normal parent-only DM gate would otherwise forbid — so it is gated on
+         *     ``get_service_account_dependency`` (the gateway's bearer JWT).
+         *
+         *     The gateway sends ``email_body.txt`` as one file (the email text, for prompt
+         *     building) and, from an updated gateway, ``original.eml`` — the original raw
+         *     RFC822 bytes exactly as received over SMTP, every header intact — which we
+         *     archive verbatim instead of reconstructing a lossier copy from parsed fields.
+         *     Any other file is a pre-extracted attachment, forwarded by an older gateway
+         *     that doesn't send ``original.eml`` yet; process_inbound_email falls back to
+         *     using those when there's no raw copy to let the parser explode instead. We
+         *     read every file's bytes here (``UploadFile`` objects do not survive past the
+         *     response), verify the sender is known, then hand the work to a background
+         *     task (assistant -> workspace -> upload -> wake -> reply).
+         */
+        post: operations['inbound_email'];
+        delete?: never;
+        options?: never;
+        head?: never;
+        patch?: never;
+        trace?: never;
+    };
     '/v1/tasks': {
         parameters: {
             query?: never;
@@ -3262,6 +3299,14 @@ interface components {
          *     recipient's current session (identified by this X25519 public key). The workspace
          *     key is stored in that session's Redis entry and the workspaceusers row expires when
          *     the session expires. Omit for a permanent grant (default behaviour).
+         *
+         *     confirm_invite (default False): an email that isn't a registered user is never
+         *     invited on a call with this unset — it's silently left out of the response (same
+         *     as any other not-found email), so the caller can diff the response against the
+         *     emails it sent and ask the owner to confirm before anything is emailed. Only a
+         *     follow-up call with this set to true for those specific emails actually sends the
+         *     invite and deposits the pending workspace-share grant. Without this gate, sharing
+         *     would email and grant future access to a typo'd address with no chance to back out.
          */
         AddWorkspaceUsersRequest: {
             /** Emails */
@@ -3274,6 +3319,8 @@ interface components {
             workspace_ext_id?: string | null;
             /** Session Pubkey B64 */
             session_pubkey_b64?: string | null;
+            /** Confirm Invite */
+            confirm_invite?: boolean | null;
         };
         /**
          * AgentControlStateEvent
@@ -3538,7 +3585,7 @@ interface components {
             /**
              * Planning Enabled
              * @description Include the create_plan tool so the agent can generate a research plan when it deems a task complex enough. Plan approval is configured on PlanningLLM.
-             * @default false
+             * @default true
              */
             PLANNING_ENABLED: boolean;
             /**
@@ -3556,7 +3603,7 @@ interface components {
             /**
              * Suggested Queries
              * @description Generate a single suggested follow-up query after each response.
-             * @default false
+             * @default true
              */
             SUGGESTED_QUERIES: boolean;
             /**
@@ -3568,7 +3615,7 @@ interface components {
             /**
              * Image Enabled
              * @description Enable the create_image tool for generating and editing images (text→image, or editing reference images from the workspace) via a chat image model, stored as an image artifact displayed in the panel.
-             * @default false
+             * @default true
              */
             IMAGE_ENABLED: boolean;
             /**
@@ -3580,7 +3627,7 @@ interface components {
             /**
              * Conversation Search Enabled
              * @description Enable the search_conversations tool so the agent can semantically search past conversation messages in the workspace. Independent of the user-facing conversation search feature flag (show_conversation_search).
-             * @default false
+             * @default true
              */
             CONVERSATION_SEARCH_ENABLED: boolean;
             /**
@@ -3592,7 +3639,7 @@ interface components {
             /**
              * Facts Enabled
              * @description Workspace facts are readable AND writable by the agent: pinned core facts are injected into the prompt, and the agent gets the search_facts (recall) and create_fact (write) tools.
-             * @default false
+             * @default true
              */
             FACTS_ENABLED: boolean;
             /**
@@ -3758,7 +3805,7 @@ interface components {
              *     - Bold text for critical conclusions or decision points
              *
              *     TOOL CALLING:
-             *     - Your job is to gather the context the question needs, then answer. Do not give a final answer while there is relevant context you have not yet retrieved — but material already in your context counts as retrieved, and fetching it a second time is not progress.
+             *     - Your job is to gather the context the question needs, then answer. Do not give a final answer while there is relevant context you have not yet retrieved — but material already in your context counts as retrieved, and fetching it a second time is not progress. If the question touches a workspace document, always check the source — never answer from a past turn's reply alone.
              *     - Always invoke tools using the tool-calling mechanism. Say what a call is doing in its `focus` argument.
              *
              *     EFFICIENCY:
@@ -3805,7 +3852,7 @@ interface components {
             /**
              * Planning Enabled
              * @description Include the create_plan tool so the agent can generate a research plan when it deems a task complex enough. Plan approval is configured on PlanningLLM.
-             * @default false
+             * @default true
              */
             PLANNING_ENABLED: boolean;
             /**
@@ -3823,7 +3870,7 @@ interface components {
             /**
              * Suggested Queries
              * @description Generate a single suggested follow-up query after each response.
-             * @default false
+             * @default true
              */
             SUGGESTED_QUERIES: boolean;
             /**
@@ -3835,7 +3882,7 @@ interface components {
             /**
              * Image Enabled
              * @description Enable the create_image tool for generating and editing images (text→image, or editing reference images from the workspace) via a chat image model, stored as an image artifact displayed in the panel.
-             * @default false
+             * @default true
              */
             IMAGE_ENABLED: boolean;
             /**
@@ -3847,13 +3894,13 @@ interface components {
             /**
              * Conversation Search Enabled
              * @description Enable the search_conversations tool so the agent can semantically search past conversation messages in the workspace. Independent of the user-facing conversation search feature flag (show_conversation_search).
-             * @default false
+             * @default true
              */
             CONVERSATION_SEARCH_ENABLED: boolean;
             /**
              * Facts Enabled
              * @description Workspace facts are readable AND writable by the agent: pinned core facts are injected into the prompt, and the agent gets the search_facts (recall) and create_fact (write) tools.
-             * @default false
+             * @default true
              */
             FACTS_ENABLED: boolean;
             /**
@@ -3931,16 +3978,16 @@ interface components {
              *       "WEB_SEARCH_ENABLED": true,
              *       "RUN_CODE_ENABLED": true,
              *       "MCP_TOOLS": [],
-             *       "PLANNING_ENABLED": false,
+             *       "PLANNING_ENABLED": true,
              *       "DEEP_RESEARCH_ENABLED": true,
              *       "SUBAGENTS_ENABLED": true,
-             *       "SUGGESTED_QUERIES": false,
+             *       "SUGGESTED_QUERIES": true,
              *       "ARTIFACTS_ENABLED": false,
-             *       "IMAGE_ENABLED": false,
+             *       "IMAGE_ENABLED": true,
              *       "VISION_ENABLED": false,
-             *       "CONVERSATION_SEARCH_ENABLED": false,
+             *       "CONVERSATION_SEARCH_ENABLED": true,
              *       "PERSONAL_AGENT": false,
-             *       "FACTS_ENABLED": false,
+             *       "FACTS_ENABLED": true,
              *       "PERSIST_LEARNINGS": false,
              *       "SKILLS_ENABLED": false,
              *       "SKILL_CREATION": false,
@@ -3962,7 +4009,7 @@ interface components {
              *       "AGENT_MAX_RUN_TOKENS": 1500000,
              *       "AGENT_MAX_SUBAGENT_SPAWNS": 4,
              *       "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\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 lists every document with its Id, Title, Date, and Pages. The Subject field is a brief navigation label only — it does not contain enough information to answer questions about a document's content. 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\nREADING TOOL RESULTS:\nEvery retrieval result opens with a CAPTION line naming the call that produced it, what it contains, and what it does not (for example \"FULL CONTENT … complete verbatim text, all 10 pages\" or \"DIGEST … verbatim page text is NOT part of this result\"). The caption also tells you when you already retrieved that material earlier in this turn. Read it before choosing your next call — it is the record of what you already hold.\n\nDOCUMENT STRATEGY, in order:\n1. Listing or cataloguing documents: use the document index already in your prompt — no tool calls needed.\n2. Getting oriented in a document you have not read: call get_table_of_contents FIRST. It is cheap, returns the heading structure with page references, and tells you which pages actually matter. Do this before any read_document on a document longer than a few pages, rather than reading blind and then discovering the structure.\n3. Specific questions across several documents: search_inside_documents to locate the passages, then read_document on the pages it points to.\n4. Reading a document: read_document with page ranges for the sections you need, or with no ranges to load the complete text. A read with no ranges returns the WHOLE document — once you have it there is nothing further to retrieve from that document. Do not read it again, do not re-read ranges out of it, and do not ask for its outline afterwards.\n5. Prefer digest=true from the outset. It is the normal retrieval mode: findings with citations, compact context. Decide against it only when the task needs the exact words — translation, quotation, close reading of style or drafting. Choosing digest=false IS that decision, and it is final for that document: digest is a way of retrieving, not a way of processing text you already hold, so once you have loaded a document in full a digest of it is refused. Reason over the text you have.\n6. Open-ended investigative queries (\"find interesting things\", \"what's notable\", \"what stands out\", \"explore X\", \"what should I know about\", \"any findings\", \"anything unusual\", \"key insights\"): ALWAYS call search_inside_documents with multiple diverse queries covering different aspects of the documents before answering. The document index is never sufficient for investigative answers — you must retrieve actual content.\n7. 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.\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 the context the question needs, then answer. Do not give a final answer while there is relevant context you have not yet retrieved — but material already in your context counts as retrieved, and fetching it a second time is not progress.\n- Always invoke tools using the tool-calling mechanism. Say what a call is doing in its `focus` argument.\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, and never re-retrieve material you already hold — the caption on each result tells you what that is.\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\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 lists every document with its Id, Title, Date, and Pages. The Subject field is a brief navigation label only — it does not contain enough information to answer questions about a document's content. 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\nREADING TOOL RESULTS:\nEvery retrieval result opens with a CAPTION line naming the call that produced it, what it contains, and what it does not (for example \"FULL CONTENT … complete verbatim text, all 10 pages\" or \"DIGEST … verbatim page text is NOT part of this result\"). The caption also tells you when you already retrieved that material earlier in this turn. Read it before choosing your next call — it is the record of what you already hold.\n\nDOCUMENT STRATEGY, in order:\n1. Listing or cataloguing documents: use the document index already in your prompt — no tool calls needed.\n2. Getting oriented in a document you have not read: call get_table_of_contents FIRST. It is cheap, returns the heading structure with page references, and tells you which pages actually matter. Do this before any read_document on a document longer than a few pages, rather than reading blind and then discovering the structure.\n3. Specific questions across several documents: search_inside_documents to locate the passages, then read_document on the pages it points to.\n4. Reading a document: read_document with page ranges for the sections you need, or with no ranges to load the complete text. A read with no ranges returns the WHOLE document — once you have it there is nothing further to retrieve from that document. Do not read it again, do not re-read ranges out of it, and do not ask for its outline afterwards.\n5. Prefer digest=true from the outset. It is the normal retrieval mode: findings with citations, compact context. Decide against it only when the task needs the exact words — translation, quotation, close reading of style or drafting. Choosing digest=false IS that decision, and it is final for that document: digest is a way of retrieving, not a way of processing text you already hold, so once you have loaded a document in full a digest of it is refused. Reason over the text you have.\n6. Open-ended investigative queries (\"find interesting things\", \"what's notable\", \"what stands out\", \"explore X\", \"what should I know about\", \"any findings\", \"anything unusual\", \"key insights\"): ALWAYS call search_inside_documents with multiple diverse queries covering different aspects of the documents before answering. The document index is never sufficient for investigative answers — you must retrieve actual content.\n7. 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.\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 the context the question needs, then answer. Do not give a final answer while there is relevant context you have not yet retrieved — but material already in your context counts as retrieved, and fetching it a second time is not progress. If the question touches a workspace document, always check the source — never answer from a past turn's reply alone.\n- Always invoke tools using the tool-calling mechanism. Say what a call is doing in its `focus` argument.\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, and never re-retrieve material you already hold — the caption on each result tells you what that is.\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'];
@@ -4081,7 +4128,7 @@ interface components {
              *           }
              *         },
              *         {
-             *           "instruction": "What is the main subject or purpose of this document? Open with one concise phrase naming what it is and what it is about, in the form 'Email chain re the site access dispute between Acme and Byrne'. Then add one or two sentences of detail.",
+             *           "instruction": "What is the main subject or purpose of this document? Open with one concise noun phrase naming what it is and what it is about, in the form 'Email chain re the site access dispute between Acme and Byrne'. Never begin with a lead-in such as 'This document is', 'The document outlines', 'This is', or any similar sentence opener — start directly with the naming phrase. Then add one or two short sentences of key detail.",
              *           "name": "doc_subject",
              *           "tag_type": {
              *             "options": [],
@@ -6895,6 +6942,11 @@ interface components {
             tag_ext_ids: string[];
             /** Doc Ext Ids */
             doc_ext_ids: string[];
+            /**
+             * Overwrite
+             * @default false
+             */
+            overwrite: boolean;
         };
         /**
          * GenerateAnnotationsResponse
@@ -7256,6 +7308,7 @@ interface components {
             workspaces: {
                 [key: string]: unknown;
             }[];
+            pending_workspace_share?: components['schemas']['PendingWorkspaceShare'] | null;
         };
         /** LogoutResponse */
         LogoutResponse: {
@@ -8041,6 +8094,21 @@ interface components {
              */
             SKIP_DUPLICATES: boolean;
         };
+        /**
+         * PendingWorkspaceShare
+         * @description A workspace share from an invite whose Redis-deposited key expired
+         *     before this login, so the client must complete it itself by sending a
+         *     normal workspace_access_request to the inviter — the fields here are
+         *     exactly what that call needs (recipient + optional workspace lock).
+         */
+        PendingWorkspaceShare: {
+            /** Workspace Ext Id */
+            workspace_ext_id: string;
+            /** Inviter Ext Id */
+            inviter_ext_id: string;
+            /** Inviter Encryption Public Key */
+            inviter_encryption_public_key: string;
+        };
         /**
          * PersonalAgentDetail
          * @description Detail for a personal_agent tool call.
@@ -15204,6 +15272,44 @@ interface operations {
             };
         };
     };
+    inbound_email: {
+        parameters: {
+            query: {
+                /** @description The sender (a registered human user) */
+                user_email: string;
+                /** @description Email subject */
+                subject?: string;
+                /** @description Set when the gateway received mail at a workspace-scoped address (wrk-xxxxxxxx@<deployment>) — act in that specific workspace, requesting access first if the agent isn't a member yet. */
+                workspace_ext_id?: string | null;
+                /** @description The inbound email's own Message-ID header, if any */
+                message_id?: string;
+            };
+            header?: never;
+            path?: never;
+            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'];
+                };
+            };
+        };
+    };
     list_tasks: {
         parameters: {
             query?: never;

package/package.json

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