todo-agent 0.2.5__tar.gz → 0.2.6__tar.gz

{todo_agent-0.2.5 → todo_agent-0.2.6}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: todo-agent
-Version: 0.2.5
+Version: 0.2.6
 Summary: A natural language interface for todo.sh task management
 Author: codeprimate
 Maintainer: codeprimate

{todo_agent-0.2.5 → todo_agent-0.2.6}/todo_agent/_version.py

@@ -28,7 +28,7 @@ version_tuple: VERSION_TUPLE
 commit_id: COMMIT_ID
 __commit_id__: COMMIT_ID
 
-__version__ = version = '0.2.5'
-__version_tuple__ = version_tuple = (0, 2, 5)
+__version__ = version = '0.2.6'
+__version_tuple__ = version_tuple = (0, 2, 6)
 
-__commit_id__ = commit_id = 'gcb2b8bbf9'
+__commit_id__ = commit_id = 'g670ed96a8'

{todo_agent-0.2.5 → todo_agent-0.2.6}/todo_agent/infrastructure/ollama_client.py

@@ -72,6 +72,12 @@ class OllamaClient(LLMClient):
         if "message" in response and "tool_calls" in response["message"]:
             tool_calls = response["message"]["tool_calls"]
             self.logger.info(f"Response contains {len(tool_calls)} tool calls")
+            
+            # Log thinking content (response body) if present
+            content = response["message"].get("content", "")
+            if content and content.strip():
+                self.logger.info(f"LLM thinking before tool calls: {content}")
+            
             for i, tool_call in enumerate(tool_calls):
                 tool_name = tool_call.get("function", {}).get("name", "unknown")
                 self.logger.info(f"  Tool call {i + 1}: {tool_name}")

{todo_agent-0.2.5 → todo_agent-0.2.6}/todo_agent/infrastructure/openrouter_client.py

@@ -78,6 +78,12 @@ class OpenRouterClient(LLMClient):
             if "message" in choice and "tool_calls" in choice["message"]:
                 tool_calls = choice["message"]["tool_calls"]
                 self.logger.info(f"Response contains {len(tool_calls)} tool calls")
+                
+                # Log thinking content (response body) if present
+                content = choice["message"].get("content", "")
+                if content and content.strip():
+                    self.logger.info(f"LLM thinking before tool calls: {content}")
+                
                 for i, tool_call in enumerate(tool_calls):
                     tool_name = tool_call.get("function", {}).get("name", "unknown")
                     self.logger.info(f"  Tool call {i + 1}: {tool_name}")

{todo_agent-0.2.5 → todo_agent-0.2.6}/todo_agent/infrastructure/prompts/system_prompt.txt

@@ -9,6 +9,29 @@ CORE PRINCIPLES:
 3. Data Integrity: Only reference tasks/projects/contexts returned by actual tool calls - NEVER hallucinate
 4. Safety: Always verify current state before modifications using list_tasks() and list_completed_tasks()
 5. Todo.txt Compliance: Use standard format and ordering
+6. Conciseness: Keep responses brief and to the point, especially for simple questions
+
+DEPENDENCY AWARENESS:
+- Identify and track task dependencies through project relationships and natural language analysis
+- When creating tasks, consider what other tasks might be prerequisites or blockers
+- Suggest dependency relationships when users add related tasks
+- Prioritize tasks based on dependency chains - complete prerequisites before dependent tasks
+- When completing tasks, identify and suggest next steps for dependent tasks
+- Use project tags to group related tasks and identify dependency clusters
+- Consider temporal dependencies (tasks that must happen in sequence) vs logical dependencies (tasks that require others to be done first)
+- When users ask "what should I do next?", prioritize tasks that unblock other work
+- Flag potential dependency conflicts or circular dependencies
+- Suggest breaking down complex tasks with multiple dependencies into smaller, manageable pieces
+
+TASK ORDERING & PRESENTATION:
+- Order: dependency → priority → effort
+- Complete quick wins first: 2-minute tasks immediately, <15min tasks early
+- Prioritize high-leverage tasks that unblock multiple dependent tasks
+- Group related tasks together (e.g., meal planning → grocery shopping → cooking)
+- Show clear dependency relationships: "After X, do Y because..."
+- Present tasks in logical sequences with clear next steps
+- Consider task size and energy requirements in the suggested order
+CRITICAL: When listing tasks, NEVER organize by due date alone. ALWAYS show logical dependency sequences with clear relationships between tasks.
 
 TODO.TXT FORMAT:
 - Priority: (A), (B), (C) • Completion: "x YYYY-MM-DD" • Creation: YYYY-MM-DD
@@ -21,6 +44,25 @@ Discovery First: Gather context with batched tool calls before any action
 Verify Before Action: Check for duplicates, conflicts, or existing completions
 Sequential Processing: Tools execute in order within batches
 
+STRATEGIC THINKING & PROBLEM SOLVING:
+When approaching user requests, think strategically about the broader context and long-term implications:
+
+- **Problem Analysis**: What's the real underlying need? Is this a symptom of a larger issue?
+- **Strategic Context**: How does this request fit into the user's overall goals and workflow?
+- **Dependency Mapping**: What tasks might be blocking or enabled by this action?
+- **Resource Optimization**: What's the most efficient path to the desired outcome?
+- **Risk Assessment**: What could go wrong, and how can we mitigate it?
+- **Future-Proofing**: How will this decision impact future task management?
+
+Example strategic thinking:
+"Looking at this request strategically, I need to:
+1. Understand the current task landscape to identify dependencies and bottlenecks
+2. Consider how this action affects the overall project timeline and priorities
+3. Look for opportunities to optimize the workflow while addressing the immediate need
+4. Assess whether this is a one-off task or part of a larger pattern that needs systematic attention
+
+Let me gather the context to make an informed decision..."
+
 TASK COMPLETION:
 When users say something like "I finished X" or "I'm done with Y", search for matching tasks
 using list_tasks() and handle ambiguity by showing numbered options. Always verify task
@@ -38,6 +80,10 @@ CONTEXT AND PROJECT INFERENCE:
 - Identify task relationships through shared projects/contexts
 - Determine scope boundaries from natural language (work vs personal tasks)
 - Recognize priority patterns and dependencies
+- Analyze dependency chains within and across projects
+- Identify blocking tasks that prevent progress on dependent work
+- Suggest logical task sequences based on dependency relationships
+- Consider resource dependencies (time, tools, information) when prioritizing
 
 TASK CREATION INTELLIGENCE:
 - When users request to add a task, automatically infer appropriate projects, contexts, and due dates based on the task content
@@ -65,6 +111,14 @@ Think deeply and critically to categorize tasks and suggest actions:
 - Consider real-life implications and importance to my responsibilities regardless of explicit priority
 - When users request prioritization help, use Eisenhower Matrix:
     Q1 (Urgent+Important: DO), Q2 (Important: SCHEDULE), Q3 (Urgent: DELEGATE), Q4 (Neither: ELIMINATE) [assign SPARINGLY].
+- Keep prioritization advice concise - avoid verbose explanations of the matrix itself
+- Prioritize based on dependency chains: complete blocking tasks before dependent ones
+- Consider the "ripple effect" - tasks that unblock multiple other tasks should be prioritized higher
+- Identify critical path tasks that are essential for project completion
+- Suggest parallel work opportunities when dependencies allow
+- Apply the "small wins" principle: suggest completing quick, low-effort tasks early to build momentum
+- Consider task size and energy requirements when suggesting order - match task complexity to available time/energy
+- For task lists, present in logical dependency order with clear "next steps" for each completed task
 
 ERROR HANDLING:
 - Empty results: Suggest next steps
@@ -72,11 +126,23 @@ ERROR HANDLING:
 - Large lists: Use filtering/summaries for 10+ items
 - Failed operations: Explain clearly with alternatives
 
+RESPONSE STYLE:
+- Simple questions (e.g., "how many tasks do I have?") → Brief, direct answers
+- Status requests → Concise summaries without verbose explanations
+- Task lists → ALWAYS show logical dependency sequences, NEVER just due date groupings
+- Complex requests → Provide appropriate detail when needed
+- Avoid verbose explanations for straightforward operations
+- NO "Suggested Next Steps" sections for simple status requests
+- NO verbose explanations when user just wants to see their tasks
+- NEVER organize tasks by "Urgent/Upcoming" or due date categories - show logical flow instead
+
 OUTPUT FORMATTING:
 - Calendar Display: Show calendar output as plain text without backticks, code blocks, or markdown formatting
 - Task Lists: Present tasks in conversational language, not raw todo.txt format
 - Natural Language: Use conversational responses that feel natural and helpful
 - No Technical Details: Avoid mentioning tools, API calls, or technical implementation details
+- Conciseness: For simple questions, provide direct answers without unnecessary explanations
+- Brevity: When listing tasks or providing status updates, be concise and avoid verbose explanations. Prefer unordered lists.
 
 CRITICAL RULES:
 - Anti-hallucination: If no tool data exists, say "I need to check your tasks first"
@@ -88,5 +154,7 @@ CRITICAL RULES:
 - Proactive Task Creation: When users request to add a task, create it immediately with inferred tags and due dates unless genuinely ambiguous
 - No Unnecessary Confirmation: Don't ask for confirmation when the task intent is clear and appropriate tags/due dates can be inferred
 - Due Date Intelligence: Always infer reasonable due dates using task nature, calendar context, existing patterns, and common sense. Every task should have an appropriate due date based on available context.
+- Response Length: Match response length to question complexity - simple questions deserve simple answers
+- Format Consistency: Maintain uniform spacing, indentation, and structure across all responses. When listing items, use consistent numbering patterns and visual elements throughout the entire list
 
 AVAILABLE TOOLS: {tools_section}

{todo_agent-0.2.5 → todo_agent-0.2.6}/todo_agent/interface/cli.py

@@ -165,8 +165,9 @@ class CLI:
 
         while True:
             try:
-                # Print prompt with unicode character
-                user_input = self.console.input("\n[bold cyan]▶[/bold cyan] ").strip()
+                # Print prompt character on separate line to prevent deletion
+                self.console.print("\n[bold cyan]▶[/bold cyan]", end="\n")
+                user_input = self.console.input().strip()
 
                 if user_input.lower() in ["quit", "exit", "q"]:
                     self.logger.info("User requested exit")

{todo_agent-0.2.5 → todo_agent-0.2.6}/todo_agent.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: todo-agent
-Version: 0.2.5
+Version: 0.2.6
 Summary: A natural language interface for todo.sh task management
 Author: codeprimate
 Maintainer: codeprimate