roboto.ai.core.task
Module Contents
AgentSubtask
Bases: pydantic.BaseModel
A lightweight checklist item under a top-level task.
Parameters
data AnyAttributes
AgentSubtaskStatus
Bases: roboto.compat.StrEnum
Lifecycle state of a sub-task.
Sub-tasks are never activated independently — they are implicitly active with their parent task — so they have no in_progress state.
AgentTask
Bases: pydantic.BaseModel
A top-level task the agent is tracking within a thread.
Parameters
data AnyAttributes
AgentTask.conclusion
Outcome recorded when the task was completed. None until then.
AgentTask.description
Longer description delimiting the task’s scope and intent.
AgentTask.start
Where the task most recently became in_progress. None if never started.
AgentTask.subtasks
Ordered sub-tasks. A task cannot be completed until all of these are done.
AgentTask.task_id
Thread-monotonic id, stable for the life of the thread. The model references this id to start or complete the task.
AgentTaskBoundary
Bases: pydantic.BaseModel
Position in the conversation where a top-level task’s active span begins or ends.
Identifies the assistant message and the content block within it whose tool call drove the transition, so callers can anchor a task to the part of the thread that worked on it.
Parameters
data AnyAgentTaskMinimal
Bases: pydantic.BaseModel
Minimal acknowledgement returned by the task mutation tools.
The full list reaches the model through the per-turn injected context, so the mutation tools echo only the affected task’s id and resulting status.
Parameters
data AnyAttributes
AgentTaskStatus
Bases: roboto.compat.StrEnum
Lifecycle state of a top-level agent task.
Attributes
AgentTaskStatus.IN_PROGRESS
The single active task. At most one task per thread is in this state.