Conversation
@trymeka/ai-provider-vercel
@trymeka/computer-provider-anchor-browser
@trymeka/computer-provider-core
@trymeka/computer-provider-e2b
@trymeka/computer-provider-scrapybara
@trymeka/core
commit: |
There was a problem hiding this comment.
Greptile Summary
This PR introduces an experimental todo list tool to the Meka Agent system, enabling AI agents to break down complex tasks into manageable subtasks with progress tracking. The implementation follows the existing tool architecture pattern used by the memory and computer tools.
The core changes include:
-
New Todo List Tool: A complete implementation in
packages/core/src/tools/todo-list.tswith Zod schema validation supporting three actions (add, update, list) and task status tracking (pending, in-progress, completed, cancelled) -
Session-based Storage: The
SessionToDoListStoreclass provides in-memory task persistence within a single agent session using a Map-based approach with auto-generated task IDs -
Agent Integration: The todo list tool is integrated into the core agent system (
packages/core/src/ai/agent.ts) alongside existing tools, with automatic context injection that prepends current task list state to conversation messages -
System Prompt Documentation: Updated the AI system prompt to inform the agent about the todo list tool's capabilities and when to use it for complex task planning
-
Example Modification: The anchor-browser example was updated to test the new functionality by removing structured output requirements and changing the task to analyze commonalities among Hacker News posts
The tool integrates seamlessly with the existing architecture, using the same session-scoped pattern as the memory tool and following established conventions for tool creation, logging, and context injection. This enhancement addresses a key limitation where agents could lose track of progress in multi-step workflows.
Confidence score: 4/5
- This PR appears safe to merge with the experimental todo list functionality working as intended
- The implementation follows established patterns and integrates well with existing architecture, though it's marked experimental
- The anchor-browser example changes need attention as they comment out functionality rather than properly removing it
Context used:
Rule - Try to find real bugs instead of nit picking on small style issues. We are moving fast and trying to make sure things work. (link)
5 files reviewed, no comments
No description provided.