xpander-sdk 2.0.330__tar.gz → 2.0.332__tar.gz

{xpander_sdk-2.0.330/src/xpander_sdk.egg-info → xpander_sdk-2.0.332}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: xpander-sdk
-Version: 2.0.330
+Version: 2.0.332
 Summary: xpander.ai Backend-as-a-service for AI Agents - SDK
 Home-page: https://www.xpander.ai
 Author: xpanderAI

{xpander_sdk-2.0.330 → xpander_sdk-2.0.332}/setup.py

@@ -5,7 +5,7 @@ with open("README.md", "r", encoding="utf-8") as fh:
 
 setup(
     name="xpander-sdk",
-    version="2.0.330",
+    version="2.0.332",
     author="xpanderAI",
     author_email="dev@xpander.ai",
     description="xpander.ai Backend-as-a-service for AI Agents - SDK",

{xpander_sdk-2.0.330 → xpander_sdk-2.0.332}/src/xpander_sdk/__init__.py

@@ -15,7 +15,7 @@ Main Components:
 For more information, visit: https://xpander.ai
 """
 
-__version__ = "2.0.330"
+__version__ = "2.0.332"
 
 # Backend-related imports
 from .modules.backend.backend_module import Backend

{xpander_sdk-2.0.330 → xpander_sdk-2.0.332}/src/xpander_sdk/core/context_optimizer/finalize_mode.py

@@ -47,33 +47,23 @@ FinalizeReason = Literal[
 # already contains every WRITE/VERIFY entry the agent needs.
 FINALIZE_ONLY_SYSTEM_OVERRIDE = """
 <finalize_only_mode>
-The system has determined this task must finalize NOW. Reasons can include:
-context budget exhausted, compaction loop detected, or durable evidence shows
-the work is already done.
-
-ABSOLUTE RULES:
-1. The ONLY mutation tool you may call is `xpfinalize_task`. Every other
-   mutation tool (writes, exec, HTTP POST, etc.) will be rejected with a
-   synthetic error message — do not retry them.
-2. Read-only escape hatch: you MAY call `xpget_agent_plan`,
-   `xpworkspace-context-retrieve`, or `xpworkspace-file-read` if you need
-   to look up a value before composing the final answer (e.g. retrieve an
-   offloaded payload from earlier). Use these sparingly and only for
-   read-only lookups; do NOT use them as a way to keep working.
-3. Read the `<authoritative_ledger>` block in the resume message. It lists
-   every WRITE you already executed and every VERIFY that confirmed it.
-4. Compose a concise final answer summarizing what was accomplished, citing
-   the verified targets (table names, row counts, file paths).
-5. Mark every plan item the ledger evidence covers as completed by passing
-   their ids in `xpfinalize_task(payload={"completed_items": [...], ...})`.
-   Do NOT call `xpcomplete_agent_plan_items` separately.
-6. Pass the final answer inside the payload:
-   `xpfinalize_task(payload={"final_answer": "...", "completed_items": [...],
-   "headers": {"toolcallreasoningtitle": "...", "toolcallreasoningdescription":
-   "..."}})`. The tool sets `task.result` and ends the run.
-7. If you genuinely have nothing to report (no evidence, no plan items),
-   call `xpfinalize_task(payload={"final_answer": "<short status>",
-   "headers": {...}})` anyway — the task must terminate.
+The system determined this task must finalize NOW (context budget exhausted, a
+compaction loop detected, or durable evidence the work is already done).
+- The ONLY mutation tool you may call is `xpfinalize_task`. Every other mutation
+  tool (writes, exec, HTTP POST, etc.) is rejected with a synthetic error — do not retry it.
+- Read-only escape hatch: you MAY call `xpget_agent_plan`,
+  `xpworkspace-context-retrieve`, or `xpworkspace-file-read` to look up a value
+  before answering (e.g. an offloaded payload). Use sparingly — not to keep working.
+- Read the `<authoritative_ledger>` block in the resume message; it lists every
+  WRITE you executed and every VERIFY that confirmed it.
+- Compose a concise final answer citing the verified targets (table names, row
+  counts, file paths). Pass everything in ONE call:
+  `xpfinalize_task(payload={"final_answer": "...", "completed_items": [<ids the
+  ledger covers>], "headers": {"toolcallreasoningtitle": "...",
+  "toolcallreasoningdescription": "..."}})`. This sets `task.result` and ends the
+  run — do NOT call `xpcomplete_agent_plan_items` separately.
+- If you genuinely have nothing to report, still call `xpfinalize_task` with a
+  short-status `final_answer` — the task must terminate.
 </finalize_only_mode>
 """
 

{xpander_sdk-2.0.330 → xpander_sdk-2.0.332}/src/xpander_sdk/core/context_optimizer/prompts.py

@@ -33,70 +33,55 @@ RECENT_ACTION_ENTRY_TEMPLATE = """\
 
 
 AUTO_COMPACT_USER_PROMPT_TEMPLATE = """\
-You are compacting an in-progress agent session into a binding state artifact that the
-resuming agent will treat as AUTHORITATIVE. The resuming agent will be told NOT to
-re-do anything you list under <work_completed>, NOT to relitigate decisions in
-<decisions_made>, and NOT to re-fetch values listed in <data_gathered>. Be precise.
+You are compacting an in-progress agent session into a binding state artifact the resuming
+agent will treat as AUTHORITATIVE: it will NOT re-do <work_completed>, NOT relitigate
+<decisions_made>, NOT re-fetch <data_gathered>. Be precise.
 
-Here is the conversation history to summarize:
+Conversation to summarize:
 <conversation>
 {conversation}
 </conversation>
 
-Output a single XML-tagged artifact with EXACTLY these sections in this order. No
-markdown headings, no preamble, no closing remarks, no commentary outside tags.
+Output ONE XML-tagged artifact with EXACTLY these sections in this order — no markdown
+headings, no preamble, no commentary outside tags.
 
 <work_completed>
-One bullet per concrete action that produced an output. Format each line as:
-  - <verb> <target> — <observed result>
-The <target> MUST be an exact identifier (file path, URL, ID, function name, command).
-The <observed result> MUST be a verifiable outcome the agent can trust later.
-Examples:
-  - Edited /src/auth/middleware.py:42-58 — replaced expiry check `<` with `<=`, pytest tests/auth passed (47/0)
-  - Created KB document doc_id=4f1e2... with 4 chunks from spec.pdf
-  - Ran command `pytest tests/integration` — exit=0, 23 passed
-Use one bullet per action. Be exhaustive — anything missing here is something the
-resuming agent will redo.
+One bullet per concrete action that produced an output: "- <verb> <target> — <observed result>".
+<target> is an exact identifier (file path, URL, ID, function, command); <observed result> is a
+verifiable outcome. e.g. "- Edited /src/auth/middleware.py:42-58 — changed `<` to `<=`, pytest 47/0".
+Be exhaustive — anything missing here gets redone.
 </work_completed>
 
 <decisions_made>
-One line per choice or fact the agent has committed to. The resuming agent will NOT
-relitigate these. Examples:
-  - chose JWT over session cookies (user confirmed in turn 3)
-  - target Python version is 3.9, not 3.11 (per setup.py)
-Only include decisions that affect future actions.
+One line per committed choice/fact that affects future actions; the resuming agent will NOT
+relitigate these. e.g. "- chose JWT over session cookies (user confirmed turn 3)".
 </decisions_made>
 
 <data_gathered>
-Verbatim opaque values, IDs, schemas, snippets the agent retrieved that may be needed
-again. The resuming agent will look here BEFORE re-fetching. Format:
-  - <kind> <identifier>: <value or summary> (source: <where it came from>)
-Examples:
-  - org id: 7f1c... (source: GET /orgs/me)
-  - file /src/config.py lines 1-20: <verbatim snippet> (source: file-read)
-Preserve identifiers EXACTLY as written. Do not shorten, normalize, or reconstruct.
+Verbatim opaque values, IDs, schemas, snippets that may be needed again — looked up here BEFORE
+re-fetching. Format "- <kind> <identifier>: <value or summary> (source: <where>)". Preserve
+identifiers EXACTLY — do not shorten, normalize, or reconstruct.
 </data_gathered>
 
 <user_requests_verbatim>
-Every user message verbatim, oldest first, one per line prefixed with the turn marker.
-Critical — non-negotiable preservation. Do NOT paraphrase. Do NOT attribute assistant
-suggestions as user preferences.
+Every user message verbatim, oldest first, one per line with its turn marker. Non-negotiable: do
+NOT paraphrase, do NOT attribute assistant suggestions as user preferences.
 </user_requests_verbatim>
 
 <open_questions>
-Anything the agent asked the user that is unanswered, OR ambiguities the agent flagged
-but did not resolve. One per line.
+Anything the agent asked the user that is unanswered, or ambiguities flagged but unresolved.
+One per line.
 </open_questions>
 
 <current_focus>
-One short paragraph: what the agent was doing in the LAST 1-2 turns of <conversation>,
-with a direct quote from the most recent assistant message. Do NOT speculate forward.
+One short paragraph: what the agent was doing in the LAST 1-2 turns of <conversation>, with a
+direct quote from the most recent assistant message. Do NOT speculate forward.
 </current_focus>
 
 <next_action>
-Single concrete next step: tool to call OR file to edit OR question to ask. MUST be
-verbatim from the most recent plan/user direction in <conversation>. Do NOT invent
-steps the user did not request and the plan does not require.
+Single concrete next step (tool to call, file to edit, or question to ask), verbatim from the most
+recent plan/user direction in <conversation>. Do NOT invent steps the user did not request and the
+plan does not require.
 </next_action>
 {plan_section}
 HARD RULES (violations make the artifact useless to the resuming agent):
@@ -121,24 +106,20 @@ and contains ALL data, findings, and work products from the earlier session.
 </state>
 {authoritative_ledger_block}
 <binding_rules>
-1. Treat <work_completed> as DONE. Do NOT re-run, re-verify, re-fetch, or re-edit
-   anything listed there unless the user explicitly asks you to. Trust the observed
-   results recorded inline.
-2. Treat <data_gathered> as available. Do NOT re-fetch identifiers, IDs, schemas, or
-   snippets listed there. If you need a value, look in <state> first.
+1. Treat <work_completed> as DONE — do NOT re-run, re-verify, re-fetch, or re-edit
+   anything listed there unless the user explicitly asks. Trust the recorded results.
+2. Treat <data_gathered> as available — do NOT re-fetch listed IDs, schemas, or
+   snippets; look in <state> first.
 3. Treat <decisions_made> as final. Do NOT relitigate or propose alternatives.
 4. The plan section below shows completed tasks. Continue from <next_action>.
 5. Do NOT ask the user any questions about prior context — it is in <state>.
-6. Continue execution. Do NOT stop until the plan is complete.
-7. <authoritative_ledger> is the durable record of every tool call this task
-   already executed. Do NOT blindly repeat a completed mutation just because
-   you lost conversational context — if a WRITE entry shows status="ok" for
-   the same tool + target + arguments you are about to invoke, that exact
-   operation is already done. You MAY perform additional, distinct mutations
-   on the same target when the current plan or the user explicitly requires
-   them (e.g. a sequence of file edits, multiple appends, follow-up inserts).
-   The ledger is ground truth over your recollection of the conversation —
-   it survives compaction unchanged.
+6. Continue execution; do NOT stop until the plan is complete.
+7. <authoritative_ledger> is the durable record of every tool call this task already
+   executed. Do NOT repeat a completed mutation just because you lost conversational
+   context — a WRITE entry with status="ok" for the same tool + target + arguments is
+   already done. You MAY perform additional, distinct mutations the plan or user
+   requires (a sequence of edits, multiple appends, follow-up inserts). The ledger is
+   ground truth over recollection; it survives compaction unchanged.
 </binding_rules>
 {recent_actions_block}
 {backup_pointer}

{xpander_sdk-2.0.330 → xpander_sdk-2.0.332}/src/xpander_sdk/modules/agents/models/agent.py

@@ -357,23 +357,6 @@ class AgentGraphItemSettings(BaseModel):
     skills_settings: Optional[AgentGraphItemSkillsSettings] = None
 
 
-class AgentGraphItemLLMSettings(BaseModel):
-    """
-    Model for LLM (Large Language Model) settings in agent graph items.
-
-    Attributes:
-        type (Literal["before", "after"]): When to apply LLM processing.
-        provider (Optional[str]): LLM provider name, defaults to "openai".
-        model (Optional[str]): Specific model name, defaults to "gpt-4.1".
-        temperature (Optional[float]): Model temperature setting, defaults to 0.0.
-    """
-
-    type: Literal["before", "after"]
-    provider: Optional[str] = "openai"
-    model: Optional[str] = "gpt-4.1"
-    temperature: Optional[float] = 0.0
-
-
 class AgentGraphItem(BaseModel):
     """
     Model representing a single item in an agent's execution graph.
@@ -389,7 +372,6 @@ class AgentGraphItem(BaseModel):
         sub_type (Optional[AgentGraphItemSubType]): Subtype for more specific categorization.
         targets (List[str]): List of target graph item IDs for execution flow.
         settings (Optional[AgentGraphItemSettings]): Configuration settings for the item.
-        llm_settings (Optional[List[AgentGraphItemLLMSettings]]): LLM processing settings.
         is_first (Optional[bool]): Whether this is the first item in the execution graph.
     """
 
@@ -400,7 +382,6 @@ class AgentGraphItem(BaseModel):
     sub_type: Optional[AgentGraphItemSubType] = None
     targets: List[str]
     settings: Optional[AgentGraphItemSettings] = None
-    llm_settings: Optional[List[AgentGraphItemLLMSettings]] = []
     is_first: Optional[bool] = False