Preflight Checklist
What happened?
Asked Agent to create a CURRICULUM including several tasks and grouping that as list_id="CURRICULUM_1".
But during Heartbeat, the agent is not able to list any task; it only sees tasks where list_id=default.
The agent is only able to see tasks from "CURRICULUM_1" if I tell it to use it.
Expected behavior
How to make the agent use task_list.list without filtering by the list_id field? Or use *?
Steps to reproduce
- Ask agent to: Create a new task for list_id= "TEST1" subject="test one" description="test one description"
- Ask agent to: Create a new task for list_id= "TEST2" subject="test two" description="test two description"
- Ask agent to: Produce a progress report containing: Current TASK LIST from task_list.list all statuses:
pending, in_progress, completed, including all fields: id, list_id, subject, description, status, owner, blocked_by as a table.
Did this happen during a chat session?
Yes
Chat session context (if applicable)
Error messages / logs
Is this a regression?
I don't know
Last working version
No response
Moltis version
20260417.01
Component
Other
Install method
Docker
Operating system
macOS (Apple Silicon)
Additional context
No response
Preflight Checklist
What happened?
Asked Agent to create a CURRICULUM including several tasks and grouping that as list_id="CURRICULUM_1".
But during Heartbeat, the agent is not able to list any task; it only sees tasks where list_id=default.
The agent is only able to see tasks from "CURRICULUM_1" if I tell it to use it.
Expected behavior
How to make the agent use task_list.list without filtering by the list_id field? Or use
*?Steps to reproduce
pending,in_progress,completed, including all fields:id,list_id,subject,description,status,owner,blocked_byas a table.Did this happen during a chat session?
Yes
Chat session context (if applicable)
Error messages / logs
Is this a regression?
I don't know
Last working version
No response
Moltis version
20260417.01
Component
Other
Install method
Docker
Operating system
macOS (Apple Silicon)
Additional context
No response