remdb 0.3.230__py3-none-any.whl → 0.3.258__py3-none-any.whl

rem/agentic/__init__.py

@@ -15,7 +15,13 @@ from .schema import (
     validate_agent_schema,
     create_agent_schema,
 )
-from .providers.pydantic_ai import create_agent_from_schema_file, create_agent, AgentRuntime
+from .providers.pydantic_ai import (
+    create_agent_from_schema_file,
+    create_agent,
+    AgentRuntime,
+    clear_agent_cache,
+    get_agent_cache_stats,
+)
 from .query_helper import ask_rem, REMQueryOutput
 from .llm_provider_models import (
     ModelInfo,
@@ -41,6 +47,9 @@ __all__ = [
     "create_agent_from_schema_file",
     "create_agent",
     "AgentRuntime",
+    # Agent Cache Management
+    "clear_agent_cache",
+    "get_agent_cache_stats",
     # REM Query Helpers
     "ask_rem",
     "REMQueryOutput",

rem/agentic/context.py

@@ -16,6 +16,7 @@ Headers Mapping:
     X-Agent-Schema   → context.agent_schema_uri (default: "rem")
     X-Model-Name     → context.default_model
     X-Is-Eval        → context.is_eval (marks session as evaluation)
+    X-Client-Id      → context.client_id (e.g., "web", "mobile", "cli")
 
 Key Design Pattern:
 - AgentContext is passed to agent factory, not stored in agents
@@ -222,6 +223,11 @@ class AgentContext(BaseModel):
         description="Whether this is an evaluation session (set via X-Is-Eval header)",
     )
 
+    client_id: str | None = Field(
+        default=None,
+        description="Client identifier (e.g., 'web', 'mobile', 'cli') set via X-Client-Id header",
+    )
+
     model_config = {"populate_by_name": True}
 
     def child_context(
@@ -232,7 +238,7 @@ class AgentContext(BaseModel):
         """
         Create a child context for nested agent calls.
 
-        Inherits user_id, tenant_id, session_id, is_eval from parent.
+        Inherits user_id, tenant_id, session_id, is_eval, client_id from parent.
         Allows overriding agent_schema_uri and default_model for the child.
 
         Args:
@@ -256,6 +262,7 @@ class AgentContext(BaseModel):
             default_model=model_override or self.default_model,
             agent_schema_uri=agent_schema_uri or self.agent_schema_uri,
             is_eval=self.is_eval,
+            client_id=self.client_id,
         )
 
     @staticmethod
@@ -374,6 +381,7 @@ class AgentContext(BaseModel):
             default_model=normalized.get("x-model-name") or settings.llm.default_model,
             agent_schema_uri=normalized.get("x-agent-schema"),
             is_eval=is_eval,
+            client_id=normalized.get("x-client-id"),
         )
 
     @classmethod
@@ -391,6 +399,7 @@ class AgentContext(BaseModel):
         - X-Model-Name: Model override
         - X-Agent-Schema: Agent schema URI
         - X-Is-Eval: Whether this is an evaluation session (true/false)
+        - X-Client-Id: Client identifier (e.g., "web", "mobile", "cli")
 
         Args:
             headers: Dictionary of HTTP headers (case-insensitive)
@@ -404,7 +413,8 @@ class AgentContext(BaseModel):
                 "X-Tenant-Id": "acme-corp",
                 "X-Session-Id": "sess-456",
                 "X-Model-Name": "anthropic:claude-opus-4-20250514",
-                "X-Is-Eval": "true"
+                "X-Is-Eval": "true",
+                "X-Client-Id": "web"
             }
             context = AgentContext.from_headers(headers)
         """
@@ -422,4 +432,5 @@ class AgentContext(BaseModel):
             default_model=normalized.get("x-model-name") or settings.llm.default_model,
             agent_schema_uri=normalized.get("x-agent-schema"),
             is_eval=is_eval,
+            client_id=normalized.get("x-client-id"),
         )

rem/agentic/context_builder.py

@@ -4,15 +4,12 @@ Centralized context builder for agent execution.
 Session History (ALWAYS loaded with compression):
 - Each chat request is a single message, so session history MUST be recovered
 - Uses SessionMessageStore with compression to keep context efficient
-- Long assistant responses include REM LOOKUP hints: "... [REM LOOKUP session-{id}-msg-{index}] ..."
-- Agent can retrieve full content on-demand using REM LOOKUP
 - Prevents context window bloat while maintaining conversation continuity
 
 User Context (on-demand by default):
-- System message includes REM LOOKUP hint for user profile
-- Agent decides whether to load profile based on query
-- More efficient for queries that don't need personalization
-- Example: "User: sarah@example.com. To load user profile: Use REM LOOKUP \"sarah@example.com\""
+- System message includes user email for context awareness
+- Fails silently if user not found - agent proceeds without user context
+- Example: "User: sarah@example.com"
 
 User Context (auto-inject when enabled):
 - Set CHAT__AUTO_INJECT_USER_CONTEXT=true
@@ -22,8 +19,8 @@ User Context (auto-inject when enabled):
 Design Pattern:
 1. Extract AgentContext from headers (user_id, tenant_id, session_id)
 2. If auto-inject enabled: Load User/Session from database
-3. If auto-inject disabled: Provide REM LOOKUP hints in system message
-4. Construct system message with date + context (injected or hints)
+3. If auto-inject disabled: Show user email for context (fail silently if not found)
+4. Construct system message with date + context
 5. Return complete context ready for agent execution
 
 Integration Points:
@@ -40,11 +37,10 @@ Usage (on-demand, default):
 
     # Messages list structure (on-demand):
     # [
-    #   {"role": "system", "content": "Today's date: 2025-11-22\nUser: sarah@example.com\nTo load user profile: Use REM LOOKUP \"sarah@example.com\"\nSession ID: sess-123\nTo load session history: Use REM LOOKUP messages?session_id=sess-123"},
+    #   {"role": "system", "content": "Today's date: 2025-11-22\n\nUser: sarah@example.com"},
     #   {"role": "user", "content": "What's next for the API migration?"}
     # ]
 
-    # Agent receives hints and can decide to load context if needed
     agent = await create_agent(context=context, ...)
     prompt = "\n".join(msg.content for msg in messages)
     result = await agent.run(prompt)
@@ -52,7 +48,7 @@ Usage (on-demand, default):
 Usage (auto-inject, CHAT__AUTO_INJECT_USER_CONTEXT=true):
     # Messages list structure (auto-inject):
     # [
-    #   {"role": "system", "content": "Today's date: 2025-11-22\n\nUser Context (auto-injected):\nSummary: ...\nInterests: ...\n\nSession History (auto-injected, 5 messages):"},
+    #   {"role": "system", "content": "Today's date: 2025-11-22\n\nUser Context (auto-injected):\nSummary: ...\nInterests: ..."},
     #   {"role": "user", "content": "Previous message"},
     #   {"role": "assistant", "content": "Previous response"},
     #   {"role": "user", "content": "What's next for the API migration?"}
@@ -110,13 +106,11 @@ class ContextBuilder:
 
         Session History (ALWAYS loaded with compression):
         - If session_id provided, session history is ALWAYS loaded using SessionMessageStore
-        - Compression keeps it efficient with REM LOOKUP hints for long messages
-        - Example: "... [Message truncated - REM LOOKUP session-{id}-msg-{index}] ..."
-        - Agent can retrieve full content on-demand using REM LOOKUP
+        - Compression keeps context efficient
 
         User Context (on-demand by default):
-        - System message includes REM LOOKUP hint: "User: {email}. To load user profile: Use REM LOOKUP \"{email}\""
-        - Agent decides whether to load profile based on query
+        - System message includes user email: "User: {email}"
+        - Fails silently if user not found - agent proceeds without user context
 
         User Context (auto-inject when enabled):
         - Set CHAT__AUTO_INJECT_USER_CONTEXT=true
@@ -137,9 +131,9 @@ class ContextBuilder:
 
             # messages structure:
             # [
-            #   {"role": "system", "content": "Today's date: 2025-11-22\nUser: sarah@example.com\nTo load user profile: Use REM LOOKUP \"sarah@example.com\""},
+            #   {"role": "system", "content": "Today's date: 2025-11-22\n\nUser: sarah@example.com"},
             #   {"role": "user", "content": "Previous message"},
-            #   {"role": "assistant", "content": "Start of long response... [REM LOOKUP session-123-msg-1] ...end"},
+            #   {"role": "assistant", "content": "Previous response"},
             #   {"role": "user", "content": "New message"}
             # ]
         """
@@ -158,6 +152,7 @@ class ContextBuilder:
                 default_model=context.default_model,
                 agent_schema_uri=context.agent_schema_uri,
                 is_eval=context.is_eval,
+                client_id=context.client_id,
             )
 
         # Initialize DB if not provided and needed (for user context or session history)
@@ -177,6 +172,10 @@ class ContextBuilder:
             today = datetime.now(timezone.utc).strftime("%Y-%m-%d")
             context_hint = f"Today's date: {today}."
 
+            # Add client identifier if present
+            if context.client_id:
+                context_hint += f"\nClient: {context.client_id}"
+
             # Add user context (auto-inject or on-demand hint)
             if settings.chat.auto_inject_user_context and context.user_id and db:
                 # Auto-inject: Load and include user profile
@@ -189,18 +188,18 @@ class ContextBuilder:
                     context_hint += f"\n\nUser Context (auto-injected):\n{user_context_content}"
                 else:
                     context_hint += "\n\nNo user context available (anonymous or new user)."
-            elif context.user_id:
-                # On-demand: Provide hint to use REM LOOKUP
-                # user_id is UUID5 hash of email - load user to get email for display and LOOKUP
-                user_repo = Repository(User, "users", db=db)
-                user = await user_repo.get_by_id(context.user_id, context.tenant_id)
-                if user and user.email:
-                    # Show email (more useful than UUID) and LOOKUP hint
-                    context_hint += f"\n\nUser: {user.email}"
-                    context_hint += f"\nTo load user profile: Use REM LOOKUP \"{user.email}\""
-                else:
-                    context_hint += f"\n\nUser ID: {context.user_id}"
-                    context_hint += "\nUser profile not available."
+            elif context.user_id and db:
+                # On-demand: Show user email for context (no REM LOOKUP - it requires exact user_id match)
+                # Fail silently if user lookup fails - just proceed without user context
+                try:
+                    user_repo = Repository(User, "users", db=db)
+                    user = await user_repo.get_by_id(context.user_id, context.tenant_id)
+                    if user and user.email:
+                        context_hint += f"\n\nUser: {user.email}"
+                    # If user not found, just proceed without adding user context
+                except Exception as e:
+                    # Fail silently - don't block agent execution if user lookup fails
+                    logger.debug(f"Could not load user context: {e}")
 
             # Add system context hint
             messages.append(ContextMessage(role="system", content=context_hint))
@@ -221,7 +220,12 @@ class ContextBuilder:
                 # can see previous tool results when the prompt is concatenated
                 for msg_dict in session_history:
                     role = msg_dict["role"]
-                    content = msg_dict["content"]
+                    content = msg_dict.get("content")
+
+                    # Skip messages with null/empty content (common in tool messages)
+                    if content is None or content == "":
+                        logger.debug(f"Skipping {role} message with null/empty content")
+                        continue
 
                     if role == "tool":
                         # Wrap tool results with clear markers for visibility
@@ -318,6 +322,7 @@ class ContextBuilder:
         session_id: str | None = None,
         message: str = "Hello",
         model: str | None = None,
+        client_id: str | None = None,
     ) -> tuple[AgentContext, list[ContextMessage]]:
         """
         Build context for testing (no database lookup).
@@ -325,7 +330,7 @@ class ContextBuilder:
         Creates minimal context with:
         - Test user (test@rem.ai)
         - Test tenant
-        - Context hint with date
+        - Context hint with date and client
         - Single user message
 
         Args:
@@ -334,6 +339,7 @@ class ContextBuilder:
             session_id: Optional session ID
             message: User message content
             model: Optional model override
+            client_id: Optional client identifier (e.g., "cli", "test")
 
         Returns:
             Tuple of (AgentContext, messages list)
@@ -341,7 +347,8 @@ class ContextBuilder:
         Example:
             context, messages = await ContextBuilder.build_from_test(
                 user_id="test@rem.ai",
-                message="What's the weather like?"
+                message="What's the weather like?",
+                client_id="cli"
             )
         """
         from ..settings import settings
@@ -352,11 +359,15 @@ class ContextBuilder:
             tenant_id=tenant_id,
             session_id=session_id,
             default_model=model or settings.llm.default_model,
+            client_id=client_id,
         )
 
         # Build minimal messages
         today = datetime.now(timezone.utc).strftime("%Y-%m-%d")
-        context_hint = f"Today's date: {today}.\n\nTest user context: {user_id} (test mode, no profile loaded)."
+        context_hint = f"Today's date: {today}."
+        if client_id:
+            context_hint += f"\nClient: {client_id}"
+        context_hint += f"\n\nTest user context: {user_id} (test mode, no profile loaded)."
 
         messages = [
             ContextMessage(role="system", content=context_hint),