@arbidocs/client 0.3.57 → 0.3.59

package/dist/index.d.cts

@@ -1129,6 +1129,11 @@ interface paths {
          *
          *     Returns 202 Accepted immediately - processing happens in background.
          *     WebSocket notification sent when complete.
+         *
+         *     Pre-checks the project's AI budget against LiteLLM and rejects with
+         *     402 ``QUOTA_EXCEEDED`` before kicking off background work — these
+         *     docs are already indexed/completed, so we can't surface mid-flight
+         *     failures via the per-doc status path that the upload pipeline uses.
          */
         post: operations['generate_doctags'];
         delete?: never;
@@ -2081,7 +2086,7 @@ interface components {
             /**
              * Skills Enabled
              * @description Enable the skills system: /skill (create) and /<skill-name> (invoke) commands.
-             * @default false
+             * @default true
              */
             SKILLS_ENABLED: boolean;
             /**
@@ -2090,6 +2095,12 @@ interface components {
              * @default false
              */
             SKILL_CREATION: boolean;
+            /**
+             * Memory Creation
+             * @description Transient flag set by /setup command to enable the save_memory agent tool (authors the per-workspace practice-profile memory document).
+             * @default false
+             */
+            MEMORY_CREATION: boolean;
             /**
              * Review Enabled
              * @description Enable ReviewLLM to review agent draft answers against source material before sending to the user. Uses the reasoning model for higher quality.
@@ -2156,7 +2167,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.
+             *     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.
              *
              *     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.
              *
@@ -2239,8 +2250,9 @@ interface components {
              *       "VISION_ENABLED": false,
              *       "PERSONAL_AGENT": false,
              *       "MEMORY_ENABLED": false,
-             *       "SKILLS_ENABLED": false,
+             *       "SKILLS_ENABLED": true,
              *       "SKILL_CREATION": false,
+             *       "MEMORY_CREATION": false,
              *       "REVIEW_ENABLED": false,
              *       "PERSONA": "You are ARBI, an AI assistant created by ARBI CITY. Be proactive, helpful and professional.",
              *       "AGENT_MODEL_NAME": "auto",
@@ -2251,7 +2263,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.\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\nEFFICIENCY:\n1. Before each step, review the results of prior steps. Adapt your approach based on what you learned — if a call was rejected or returned poor results, adjust your strategy.\n2. Call multiple tools in parallel when a query has several aspects.\n3. NEVER repeat a tool call with the same arguments.\n4. Use targeted queries and narrow page ranges per retrieval call.\n5. Stop when you have sufficient evidence — do not over-research."
+             *       "AGENT_SYSTEM_PROMPT": "Answer any question the user asks. You have access to workspace documents — use them when relevant. When no documents are relevant, answer from your own knowledge. Always provide a helpful answer.\n\nIMPORTANT: Never say \"I don't have information in the available documents\" or refuse to answer. If documents are not relevant, just answer the question directly from your own knowledge. If the user asks about a specific workspace document, call read_document or get_table_of_contents — never answer from memory.\n\nWhen using documents, retrieve actual document content — do not rely on metadata or headings alone. Cross-check information across sources. Not all assertions in sources are factual — some are arguments by a party. Attribute claims to their source where parties disagree.\n\nDOCUMENT INDEX:\nThe \"Workspace Documents\" table in your system prompt already lists every document with its Id, Title, Date, Pages, and Subject. Use this table directly when the user asks to list, catalogue, or tabulate documents — do NOT call any tools for that. Only use tools when you need to read or search document content.\n\nDOCUMENT STRATEGY:\n- For listing/cataloguing documents: use the document index already in your prompt — no tool calls needed.\n- For overview/summary requests: use get_table_of_contents first, then read key sections with read_document.\n- For specific questions: use search_inside_documents to find relevant sections, then read those sections with read_document.\n- For translation, deep analysis, or detailed summaries of a single document: use read_document with no ranges to load the complete text.\n- For extracting structured findings from passages: use read_document with digest=true or search_inside_documents with digest=true.\n- Never search for meta-queries like \"summary\", \"overview\", or \"all documents\" — search for the actual subject matter.\n\nFORMATTING:\n- Start your answer directly with the content — never open with a description of what you searched for or read (e.g. never write \"Searching for X\", \"Reading Y\", \"I found Z documents\" as the first lines of an answer).\n- Use markdown: headings, bold, bullet points, numbered lists\n- Main conclusion first, followed by supporting points\n- Bullet points for lists of discrete items\n- Numbering for sequential steps or prioritized items\n- Bold text for critical conclusions or decision points\n\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'];
@@ -2261,7 +2273,7 @@ interface components {
              *       "ENABLE_THINKING": false,
              *       "MODEL_NAME": "Fast",
              *       "SYSTEM_INSTRUCTION": "You are ARBI, an AI assistant created by ARBI CITY. Be proactive, helpful and professional.Be concise. Use markdown where it helps readability. Cross-check information across sources before answering. Never fabricate facts. Not all assertions in the sources are factual — some are arguments by a party. Attribute claims to their source, especially where parties disagree.",
-             *       "MAX_CHAR_SIZE_TO_ANSWER": 200000,
+             *       "MAX_TOKEN_SIZE_TO_ANSWER": 200000,
              *       "TEMPERATURE": 0.1,
              *       "MAX_TOKENS": 5000
              *     }
@@ -2275,7 +2287,7 @@ interface components {
              *       "SYSTEM_INSTRUCTION": "You are reviewing a draft answer prepared by a research agent. The draft was written based on summaries, but you now have access to the full source material.\n\nYour task:\n1. Review the draft answer against the source material provided\n2. Verify claims are supported by the sources\n3. Correct any inaccuracies or unsupported statements\n4. Add any important details from the sources that were missed\n5. Maintain formal, objective tone appropriate for professional contexts\n\nIf information is not found in the sources but the draft answer is based on web search results or general knowledge, preserve it and ensure it is clearly labelled as such. Only flag missing source support for claims that purport to come from the documents.\nDo not add inline citation markers - the system handles citations automatically.",
              *       "TEMPERATURE": 0.1,
              *       "MAX_TOKENS": 5000,
-             *       "MAX_CHAR_SIZE_TO_ANSWER": 200000
+             *       "MAX_TOKEN_SIZE_TO_ANSWER": 200000
              *     }
              */
             ReviewLLM: components['schemas']['ReviewLLMConfig'];
@@ -2287,7 +2299,7 @@ interface components {
              *       "SYSTEM_INSTRUCTION": "You are a chunk evaluator. Analyze retrieved chunks to determine which are relevant to the user's query and extract key learnings from the RELEVANT chunks only. You must return your response as valid JSON matching the provided schema.",
              *       "TEMPERATURE": 0.1,
              *       "MAX_TOKENS": 20000,
-             *       "MAX_CHAR_SIZE_TO_ANSWER": 100000
+             *       "MAX_TOKEN_SIZE_TO_ANSWER": 200000
              *     }
              */
             EvaluatorLLM: components['schemas']['EvaluatorLLMConfig'];
@@ -2297,7 +2309,7 @@ interface components {
              *       "ENABLE_THINKING": false,
              *       "MODEL_NAME": "Fast",
              *       "SYSTEM_INSTRUCTION": "You are a title generator that creates concise, descriptive titles.\n\nOutput the title as plain text only. Do not use Markdown or any other formatting. Specifically:\n- Do not bold, italicize, or otherwise emphasize any part of the title.\n- Do not include asterisks (*), underscores (_), backticks (`), or other Markdown markers.\n- Do not prefix the title with bullets, dashes (-), or numbered/lettered enumeration (e.g. \"1.\", \"a)\").\n- Do not wrap the title in quotes or brackets.",
-             *       "MAX_CHAR_SIZE_TO_ANSWER": 50,
+             *       "MAX_TOKEN_SIZE_TO_ANSWER": 20,
              *       "TEMPERATURE": 0.3,
              *       "MAX_TOKENS": 20
              *     }
@@ -2311,7 +2323,7 @@ interface components {
              *       "SYSTEM_INSTRUCTION": "You are a conversation summariser. Condense the conversation history into a concise summary that preserves:\n- Key decisions and conclusions reached\n- Specific names, dates, numbers, and document references\n- Open questions and unresolved items\n- The user's goals and constraints\n\nWrite in past tense, third person. Be specific, not vague. Do not omit important details in favour of brevity.",
              *       "TEMPERATURE": 0.1,
              *       "MAX_TOKENS": 2000,
-             *       "MAX_CHAR_SIZE_TO_ANSWER": 200000,
+             *       "MAX_TOKEN_SIZE_TO_ANSWER": 200000,
              *       "COMPACTION_THRESHOLD_TOKENS": 0,
              *       "COMPACTION_KEEP_RECENT": 4
              *     }
@@ -2323,7 +2335,7 @@ interface components {
              *       "ENABLE_THINKING": false,
              *       "MODEL_NAME": "Fast",
              *       "SYSTEM_INSTRUCTION": "You are a document analysis assistant. Answer questions based strictly on document content.\n\nGuidelines:\n- Only use information explicitly stated in the document\n- Do not infer or assume information not present\n- If information is not found, respond with \"Information not found in document.\"\n- Follow format instructions exactly for each answer\n- Be concise and precise\n- Output answers as plain text only. Do not use Markdown or any other formatting:\n  - Do not bold, italicize, or otherwise emphasize any part of the answer.\n  - Do not include asterisks (*), underscores (_), backticks (`), or other Markdown markers.\n  - Do not prefix answers with bullets, dashes (-), or numbered/lettered enumeration (e.g. \"1.\", \"a)\").\n  - Write multi-point answers as flowing sentences, not as a list.",
-             *       "MAX_CHAR_CONTEXT_TO_ANSWER": 100000,
+             *       "MAX_TOKEN_CONTEXT_TO_ANSWER": 200000,
              *       "TEMPERATURE": 0.1,
              *       "MAX_TOKENS": 2000,
              *       "MAX_CONCURRENT_DOCS": 10,
@@ -2386,7 +2398,7 @@ interface components {
              *       "SYSTEM_INSTRUCTION": "You are a knowledge synthesizer. You receive the full agent scratchpad from a completed conversation and decide what, if anything, is worth saving.\n\n## Work Product Types\n- **\"memory\"**: Facts, findings, reference data — for *looking up* information.\n- **\"skill\"**: Procedures, workflows, step-by-step instructions — for *doing* something.\n\nWhen ambiguous, default to memory.\n\n## Rules\n- Return an empty work_products array if the conversation is trivial or produced nothing substantive.\n- Each work product must cover ONE coherent topic. Never combine disparate subjects into a single document — create separate documents for each distinct topic.\n- Ground everything in the provided context. Do not invent information.\n- Be concise. These are reference documents, not essays.\n\n## Output Format\nJSON with a `work_products` array. Each item has `wp_type`, `title`, and `content` (markdown).\n\nMemory content: `# Title`, date, source, key findings as bullets, source documents.\nSkill content: `# Title`, prerequisites, numbered steps, when to apply.",
              *       "TEMPERATURE": 0.3,
              *       "MAX_TOKENS": 8000,
-             *       "MAX_CHAR_CONTEXT": 100000,
+             *       "MAX_TOKEN_CONTEXT": 200000,
              *       "MAX_CONCURRENT": 5
              *     }
              */
@@ -2399,7 +2411,7 @@ interface components {
              *       "SYSTEM_INSTRUCTION": "You are a research planning assistant. Your job is to analyze a user query and produce a concise, numbered research plan.\n\nYou have access to a workspace of documents. The available tools for executing the plan are:\n- search_inside_documents: Search workspace documents for relevant passages (semantic, keyword, or hybrid). Use digest=true to extract learnings.\n- read_document: Read page ranges or entire documents. Use digest=true to extract learnings with citations.\n- get_table_of_contents: Get document headings with page references\n\nConsider:\n- What information is needed to answer the query\n- Which documents are likely relevant based on the document index\n- What search queries and document passages to examine\n- What order of operations will be most efficient\n- Whether parallel searches can be used for different aspects\n\nRespond with ONLY the plan (numbered steps). Do not execute any steps.",
              *       "TEMPERATURE": 0.3,
              *       "MAX_TOKENS": 4000,
-             *       "MAX_CHAR_SIZE_TO_ANSWER": 200000,
+             *       "MAX_TOKEN_SIZE_TO_ANSWER": 200000,
              *       "APPROVAL_TIMEOUT": 0
              *     }
              */
@@ -3633,11 +3645,11 @@ interface components {
              */
             SYSTEM_INSTRUCTION: string;
             /**
-             * Max Char Context To Answer
-             * @description Maximum characters in document for context.
-             * @default 100000
+             * Max Token Context To Answer
+             * @description Maximum input tokens in document for context.
+             * @default 200000
              */
-            MAX_CHAR_CONTEXT_TO_ANSWER: number;
+            MAX_TOKEN_CONTEXT_TO_ANSWER: number;
             /**
              * Temperature
              * @description Temperature for factual answers.
@@ -3800,11 +3812,11 @@ interface components {
              */
             MAX_TOKENS: number;
             /**
-             * Max Char Size To Answer
-             * @description Maximum character size for evaluation context.
-             * @default 100000
+             * Max Token Size To Answer
+             * @description Maximum input token size for evaluation context.
+             * @default 200000
              */
-            MAX_CHAR_SIZE_TO_ANSWER: number;
+            MAX_TOKEN_SIZE_TO_ANSWER: number;
         };
         /**
          * FileDeleteResponse
@@ -4241,11 +4253,11 @@ interface components {
              */
             MAX_TOKENS: number;
             /**
-             * Max Char Context
-             * @description Maximum characters of input context.
-             * @default 100000
+             * Max Token Context
+             * @description Maximum tokens of input context.
+             * @default 200000
              */
-            MAX_CHAR_CONTEXT: number;
+            MAX_TOKEN_CONTEXT: number;
             /**
              * Max Concurrent
              * @description Maximum concurrent synthesis operations.
@@ -4931,11 +4943,11 @@ interface components {
              */
             MAX_TOKENS: number;
             /**
-             * Max Char Size To Answer
-             * @description Maximum character size for planning context.
+             * Max Token Size To Answer
+             * @description Maximum input token size for planning context.
              * @default 200000
              */
-            MAX_CHAR_SIZE_TO_ANSWER: number;
+            MAX_TOKEN_SIZE_TO_ANSWER: number;
             /**
              * Approval Timeout
              * @description Seconds to wait for user approval after generating the plan. 0 = no approval (auto-proceed). Safe for non-interactive contexts.
@@ -5252,11 +5264,11 @@ interface components {
              */
             SYSTEM_INSTRUCTION: string;
             /**
-             * Max Char Size To Answer
-             * @description Maximum character size to answer.
+             * Max Token Size To Answer
+             * @description Maximum input token size to answer.
              * @default 200000
              */
-            MAX_CHAR_SIZE_TO_ANSWER: number;
+            MAX_TOKEN_SIZE_TO_ANSWER: number;
             /**
              * Temperature
              * @description Temperature value for randomness.
@@ -6179,11 +6191,11 @@ interface components {
              */
             MAX_TOKENS: number;
             /**
-             * Max Char Size To Answer
-             * @description Maximum character size for review context.
+             * Max Token Size To Answer
+             * @description Maximum input token size for review context.
              * @default 200000
              */
-            MAX_CHAR_SIZE_TO_ANSWER: number;
+            MAX_TOKEN_SIZE_TO_ANSWER: number;
         };
         /**
          * RunCodeConfig
@@ -6609,11 +6621,11 @@ interface components {
              */
             MAX_TOKENS: number;
             /**
-             * Max Char Size To Answer
-             * @description Maximum character size of conversation history to summarise.
+             * Max Token Size To Answer
+             * @description Maximum input token size of conversation history to summarise.
              * @default 200000
              */
-            MAX_CHAR_SIZE_TO_ANSWER: number;
+            MAX_TOKEN_SIZE_TO_ANSWER: number;
             /**
              * Compaction Threshold Tokens
              * @description Auto-compact when thread tokens exceed this threshold. 0 = disabled.
@@ -6801,11 +6813,11 @@ interface components {
              */
             SYSTEM_INSTRUCTION: string;
             /**
-             * Max Char Size To Answer
-             * @description Maximum character size to answer.
-             * @default 50
+             * Max Token Size To Answer
+             * @description Maximum input token size to answer.
+             * @default 20
              */
-            MAX_CHAR_SIZE_TO_ANSWER: number;
+            MAX_TOKEN_SIZE_TO_ANSWER: number;
             /**
              * Temperature
              * @description Temperature value for randomness.
@@ -7261,6 +7273,11 @@ interface components {
              * @default []
              */
             pinned_templates: string[];
+            /**
+             * Pinned Skills
+             * @default []
+             */
+            pinned_skills: string[];
             /**
              * Tableviews
              * @default []
@@ -7298,7 +7315,7 @@ interface components {
             show_help_page: boolean;
             /**
              * Show Templates
-             * @default true
+             * @default false
              */
             show_templates: boolean;
             /**
@@ -7344,6 +7361,8 @@ interface components {
             pinned_workspaces?: string[] | null;
             /** Pinned Templates */
             pinned_templates?: string[] | null;
+            /** Pinned Skills */
+            pinned_skills?: string[] | null;
             /** Tableviews */
             tableviews?: components['schemas']['TableView'][] | null;
             /** Show Document Navigator */

package/dist/index.d.ts

@@ -1129,6 +1129,11 @@ interface paths {
          *
          *     Returns 202 Accepted immediately - processing happens in background.
          *     WebSocket notification sent when complete.
+         *
+         *     Pre-checks the project's AI budget against LiteLLM and rejects with
+         *     402 ``QUOTA_EXCEEDED`` before kicking off background work — these
+         *     docs are already indexed/completed, so we can't surface mid-flight
+         *     failures via the per-doc status path that the upload pipeline uses.
          */
         post: operations['generate_doctags'];
         delete?: never;
@@ -2081,7 +2086,7 @@ interface components {
             /**
              * Skills Enabled
              * @description Enable the skills system: /skill (create) and /<skill-name> (invoke) commands.
-             * @default false
+             * @default true
              */
             SKILLS_ENABLED: boolean;
             /**
@@ -2090,6 +2095,12 @@ interface components {
              * @default false
              */
             SKILL_CREATION: boolean;
+            /**
+             * Memory Creation
+             * @description Transient flag set by /setup command to enable the save_memory agent tool (authors the per-workspace practice-profile memory document).
+             * @default false
+             */
+            MEMORY_CREATION: boolean;
             /**
              * Review Enabled
              * @description Enable ReviewLLM to review agent draft answers against source material before sending to the user. Uses the reasoning model for higher quality.
@@ -2156,7 +2167,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.
+             *     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.
              *
              *     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.
              *
@@ -2239,8 +2250,9 @@ interface components {
              *       "VISION_ENABLED": false,
              *       "PERSONAL_AGENT": false,
              *       "MEMORY_ENABLED": false,
-             *       "SKILLS_ENABLED": false,
+             *       "SKILLS_ENABLED": true,
              *       "SKILL_CREATION": false,
+             *       "MEMORY_CREATION": false,
              *       "REVIEW_ENABLED": false,
              *       "PERSONA": "You are ARBI, an AI assistant created by ARBI CITY. Be proactive, helpful and professional.",
              *       "AGENT_MODEL_NAME": "auto",
@@ -2251,7 +2263,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.\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\nEFFICIENCY:\n1. Before each step, review the results of prior steps. Adapt your approach based on what you learned — if a call was rejected or returned poor results, adjust your strategy.\n2. Call multiple tools in parallel when a query has several aspects.\n3. NEVER repeat a tool call with the same arguments.\n4. Use targeted queries and narrow page ranges per retrieval call.\n5. Stop when you have sufficient evidence — do not over-research."
+             *       "AGENT_SYSTEM_PROMPT": "Answer any question the user asks. You have access to workspace documents — use them when relevant. When no documents are relevant, answer from your own knowledge. Always provide a helpful answer.\n\nIMPORTANT: Never say \"I don't have information in the available documents\" or refuse to answer. If documents are not relevant, just answer the question directly from your own knowledge. If the user asks about a specific workspace document, call read_document or get_table_of_contents — never answer from memory.\n\nWhen using documents, retrieve actual document content — do not rely on metadata or headings alone. Cross-check information across sources. Not all assertions in sources are factual — some are arguments by a party. Attribute claims to their source where parties disagree.\n\nDOCUMENT INDEX:\nThe \"Workspace Documents\" table in your system prompt already lists every document with its Id, Title, Date, Pages, and Subject. Use this table directly when the user asks to list, catalogue, or tabulate documents — do NOT call any tools for that. Only use tools when you need to read or search document content.\n\nDOCUMENT STRATEGY:\n- For listing/cataloguing documents: use the document index already in your prompt — no tool calls needed.\n- For overview/summary requests: use get_table_of_contents first, then read key sections with read_document.\n- For specific questions: use search_inside_documents to find relevant sections, then read those sections with read_document.\n- For translation, deep analysis, or detailed summaries of a single document: use read_document with no ranges to load the complete text.\n- For extracting structured findings from passages: use read_document with digest=true or search_inside_documents with digest=true.\n- Never search for meta-queries like \"summary\", \"overview\", or \"all documents\" — search for the actual subject matter.\n\nFORMATTING:\n- Start your answer directly with the content — never open with a description of what you searched for or read (e.g. never write \"Searching for X\", \"Reading Y\", \"I found Z documents\" as the first lines of an answer).\n- Use markdown: headings, bold, bullet points, numbered lists\n- Main conclusion first, followed by supporting points\n- Bullet points for lists of discrete items\n- Numbering for sequential steps or prioritized items\n- Bold text for critical conclusions or decision points\n\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'];
@@ -2261,7 +2273,7 @@ interface components {
              *       "ENABLE_THINKING": false,
              *       "MODEL_NAME": "Fast",
              *       "SYSTEM_INSTRUCTION": "You are ARBI, an AI assistant created by ARBI CITY. Be proactive, helpful and professional.Be concise. Use markdown where it helps readability. Cross-check information across sources before answering. Never fabricate facts. Not all assertions in the sources are factual — some are arguments by a party. Attribute claims to their source, especially where parties disagree.",
-             *       "MAX_CHAR_SIZE_TO_ANSWER": 200000,
+             *       "MAX_TOKEN_SIZE_TO_ANSWER": 200000,
              *       "TEMPERATURE": 0.1,
              *       "MAX_TOKENS": 5000
              *     }
@@ -2275,7 +2287,7 @@ interface components {
              *       "SYSTEM_INSTRUCTION": "You are reviewing a draft answer prepared by a research agent. The draft was written based on summaries, but you now have access to the full source material.\n\nYour task:\n1. Review the draft answer against the source material provided\n2. Verify claims are supported by the sources\n3. Correct any inaccuracies or unsupported statements\n4. Add any important details from the sources that were missed\n5. Maintain formal, objective tone appropriate for professional contexts\n\nIf information is not found in the sources but the draft answer is based on web search results or general knowledge, preserve it and ensure it is clearly labelled as such. Only flag missing source support for claims that purport to come from the documents.\nDo not add inline citation markers - the system handles citations automatically.",
              *       "TEMPERATURE": 0.1,
              *       "MAX_TOKENS": 5000,
-             *       "MAX_CHAR_SIZE_TO_ANSWER": 200000
+             *       "MAX_TOKEN_SIZE_TO_ANSWER": 200000
              *     }
              */
             ReviewLLM: components['schemas']['ReviewLLMConfig'];
@@ -2287,7 +2299,7 @@ interface components {
              *       "SYSTEM_INSTRUCTION": "You are a chunk evaluator. Analyze retrieved chunks to determine which are relevant to the user's query and extract key learnings from the RELEVANT chunks only. You must return your response as valid JSON matching the provided schema.",
              *       "TEMPERATURE": 0.1,
              *       "MAX_TOKENS": 20000,
-             *       "MAX_CHAR_SIZE_TO_ANSWER": 100000
+             *       "MAX_TOKEN_SIZE_TO_ANSWER": 200000
              *     }
              */
             EvaluatorLLM: components['schemas']['EvaluatorLLMConfig'];
@@ -2297,7 +2309,7 @@ interface components {
              *       "ENABLE_THINKING": false,
              *       "MODEL_NAME": "Fast",
              *       "SYSTEM_INSTRUCTION": "You are a title generator that creates concise, descriptive titles.\n\nOutput the title as plain text only. Do not use Markdown or any other formatting. Specifically:\n- Do not bold, italicize, or otherwise emphasize any part of the title.\n- Do not include asterisks (*), underscores (_), backticks (`), or other Markdown markers.\n- Do not prefix the title with bullets, dashes (-), or numbered/lettered enumeration (e.g. \"1.\", \"a)\").\n- Do not wrap the title in quotes or brackets.",
-             *       "MAX_CHAR_SIZE_TO_ANSWER": 50,
+             *       "MAX_TOKEN_SIZE_TO_ANSWER": 20,
              *       "TEMPERATURE": 0.3,
              *       "MAX_TOKENS": 20
              *     }
@@ -2311,7 +2323,7 @@ interface components {
              *       "SYSTEM_INSTRUCTION": "You are a conversation summariser. Condense the conversation history into a concise summary that preserves:\n- Key decisions and conclusions reached\n- Specific names, dates, numbers, and document references\n- Open questions and unresolved items\n- The user's goals and constraints\n\nWrite in past tense, third person. Be specific, not vague. Do not omit important details in favour of brevity.",
              *       "TEMPERATURE": 0.1,
              *       "MAX_TOKENS": 2000,
-             *       "MAX_CHAR_SIZE_TO_ANSWER": 200000,
+             *       "MAX_TOKEN_SIZE_TO_ANSWER": 200000,
              *       "COMPACTION_THRESHOLD_TOKENS": 0,
              *       "COMPACTION_KEEP_RECENT": 4
              *     }
@@ -2323,7 +2335,7 @@ interface components {
              *       "ENABLE_THINKING": false,
              *       "MODEL_NAME": "Fast",
              *       "SYSTEM_INSTRUCTION": "You are a document analysis assistant. Answer questions based strictly on document content.\n\nGuidelines:\n- Only use information explicitly stated in the document\n- Do not infer or assume information not present\n- If information is not found, respond with \"Information not found in document.\"\n- Follow format instructions exactly for each answer\n- Be concise and precise\n- Output answers as plain text only. Do not use Markdown or any other formatting:\n  - Do not bold, italicize, or otherwise emphasize any part of the answer.\n  - Do not include asterisks (*), underscores (_), backticks (`), or other Markdown markers.\n  - Do not prefix answers with bullets, dashes (-), or numbered/lettered enumeration (e.g. \"1.\", \"a)\").\n  - Write multi-point answers as flowing sentences, not as a list.",
-             *       "MAX_CHAR_CONTEXT_TO_ANSWER": 100000,
+             *       "MAX_TOKEN_CONTEXT_TO_ANSWER": 200000,
              *       "TEMPERATURE": 0.1,
              *       "MAX_TOKENS": 2000,
              *       "MAX_CONCURRENT_DOCS": 10,
@@ -2386,7 +2398,7 @@ interface components {
              *       "SYSTEM_INSTRUCTION": "You are a knowledge synthesizer. You receive the full agent scratchpad from a completed conversation and decide what, if anything, is worth saving.\n\n## Work Product Types\n- **\"memory\"**: Facts, findings, reference data — for *looking up* information.\n- **\"skill\"**: Procedures, workflows, step-by-step instructions — for *doing* something.\n\nWhen ambiguous, default to memory.\n\n## Rules\n- Return an empty work_products array if the conversation is trivial or produced nothing substantive.\n- Each work product must cover ONE coherent topic. Never combine disparate subjects into a single document — create separate documents for each distinct topic.\n- Ground everything in the provided context. Do not invent information.\n- Be concise. These are reference documents, not essays.\n\n## Output Format\nJSON with a `work_products` array. Each item has `wp_type`, `title`, and `content` (markdown).\n\nMemory content: `# Title`, date, source, key findings as bullets, source documents.\nSkill content: `# Title`, prerequisites, numbered steps, when to apply.",
              *       "TEMPERATURE": 0.3,
              *       "MAX_TOKENS": 8000,
-             *       "MAX_CHAR_CONTEXT": 100000,
+             *       "MAX_TOKEN_CONTEXT": 200000,
              *       "MAX_CONCURRENT": 5
              *     }
              */
@@ -2399,7 +2411,7 @@ interface components {
              *       "SYSTEM_INSTRUCTION": "You are a research planning assistant. Your job is to analyze a user query and produce a concise, numbered research plan.\n\nYou have access to a workspace of documents. The available tools for executing the plan are:\n- search_inside_documents: Search workspace documents for relevant passages (semantic, keyword, or hybrid). Use digest=true to extract learnings.\n- read_document: Read page ranges or entire documents. Use digest=true to extract learnings with citations.\n- get_table_of_contents: Get document headings with page references\n\nConsider:\n- What information is needed to answer the query\n- Which documents are likely relevant based on the document index\n- What search queries and document passages to examine\n- What order of operations will be most efficient\n- Whether parallel searches can be used for different aspects\n\nRespond with ONLY the plan (numbered steps). Do not execute any steps.",
              *       "TEMPERATURE": 0.3,
              *       "MAX_TOKENS": 4000,
-             *       "MAX_CHAR_SIZE_TO_ANSWER": 200000,
+             *       "MAX_TOKEN_SIZE_TO_ANSWER": 200000,
              *       "APPROVAL_TIMEOUT": 0
              *     }
              */
@@ -3633,11 +3645,11 @@ interface components {
              */
             SYSTEM_INSTRUCTION: string;
             /**
-             * Max Char Context To Answer
-             * @description Maximum characters in document for context.
-             * @default 100000
+             * Max Token Context To Answer
+             * @description Maximum input tokens in document for context.
+             * @default 200000
              */
-            MAX_CHAR_CONTEXT_TO_ANSWER: number;
+            MAX_TOKEN_CONTEXT_TO_ANSWER: number;
             /**
              * Temperature
              * @description Temperature for factual answers.
@@ -3800,11 +3812,11 @@ interface components {
              */
             MAX_TOKENS: number;
             /**
-             * Max Char Size To Answer
-             * @description Maximum character size for evaluation context.
-             * @default 100000
+             * Max Token Size To Answer
+             * @description Maximum input token size for evaluation context.
+             * @default 200000
              */
-            MAX_CHAR_SIZE_TO_ANSWER: number;
+            MAX_TOKEN_SIZE_TO_ANSWER: number;
         };
         /**
          * FileDeleteResponse
@@ -4241,11 +4253,11 @@ interface components {
              */
             MAX_TOKENS: number;
             /**
-             * Max Char Context
-             * @description Maximum characters of input context.
-             * @default 100000
+             * Max Token Context
+             * @description Maximum tokens of input context.
+             * @default 200000
              */
-            MAX_CHAR_CONTEXT: number;
+            MAX_TOKEN_CONTEXT: number;
             /**
              * Max Concurrent
              * @description Maximum concurrent synthesis operations.
@@ -4931,11 +4943,11 @@ interface components {
              */
             MAX_TOKENS: number;
             /**
-             * Max Char Size To Answer
-             * @description Maximum character size for planning context.
+             * Max Token Size To Answer
+             * @description Maximum input token size for planning context.
              * @default 200000
              */
-            MAX_CHAR_SIZE_TO_ANSWER: number;
+            MAX_TOKEN_SIZE_TO_ANSWER: number;
             /**
              * Approval Timeout
              * @description Seconds to wait for user approval after generating the plan. 0 = no approval (auto-proceed). Safe for non-interactive contexts.
@@ -5252,11 +5264,11 @@ interface components {
              */
             SYSTEM_INSTRUCTION: string;
             /**
-             * Max Char Size To Answer
-             * @description Maximum character size to answer.
+             * Max Token Size To Answer
+             * @description Maximum input token size to answer.
              * @default 200000
              */
-            MAX_CHAR_SIZE_TO_ANSWER: number;
+            MAX_TOKEN_SIZE_TO_ANSWER: number;
             /**
              * Temperature
              * @description Temperature value for randomness.
@@ -6179,11 +6191,11 @@ interface components {
              */
             MAX_TOKENS: number;
             /**
-             * Max Char Size To Answer
-             * @description Maximum character size for review context.
+             * Max Token Size To Answer
+             * @description Maximum input token size for review context.
              * @default 200000
              */
-            MAX_CHAR_SIZE_TO_ANSWER: number;
+            MAX_TOKEN_SIZE_TO_ANSWER: number;
         };
         /**
          * RunCodeConfig
@@ -6609,11 +6621,11 @@ interface components {
              */
             MAX_TOKENS: number;
             /**
-             * Max Char Size To Answer
-             * @description Maximum character size of conversation history to summarise.
+             * Max Token Size To Answer
+             * @description Maximum input token size of conversation history to summarise.
              * @default 200000
              */
-            MAX_CHAR_SIZE_TO_ANSWER: number;
+            MAX_TOKEN_SIZE_TO_ANSWER: number;
             /**
              * Compaction Threshold Tokens
              * @description Auto-compact when thread tokens exceed this threshold. 0 = disabled.
@@ -6801,11 +6813,11 @@ interface components {
              */
             SYSTEM_INSTRUCTION: string;
             /**
-             * Max Char Size To Answer
-             * @description Maximum character size to answer.
-             * @default 50
+             * Max Token Size To Answer
+             * @description Maximum input token size to answer.
+             * @default 20
              */
-            MAX_CHAR_SIZE_TO_ANSWER: number;
+            MAX_TOKEN_SIZE_TO_ANSWER: number;
             /**
              * Temperature
              * @description Temperature value for randomness.
@@ -7261,6 +7273,11 @@ interface components {
              * @default []
              */
             pinned_templates: string[];
+            /**
+             * Pinned Skills
+             * @default []
+             */
+            pinned_skills: string[];
             /**
              * Tableviews
              * @default []
@@ -7298,7 +7315,7 @@ interface components {
             show_help_page: boolean;
             /**
              * Show Templates
-             * @default true
+             * @default false
              */
             show_templates: boolean;
             /**
@@ -7344,6 +7361,8 @@ interface components {
             pinned_workspaces?: string[] | null;
             /** Pinned Templates */
             pinned_templates?: string[] | null;
+            /** Pinned Skills */
+            pinned_skills?: string[] | null;
             /** Tableviews */
             tableviews?: components['schemas']['TableView'][] | null;
             /** Show Document Navigator */

package/package.json

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