Details


Object Hierarchy:

Object hierarchy for Details

Description:

public class Details : Base

One task in the plan. Built from task list output; updated from refinement output.

Task list (input): each list item under a task section heading has a nested list with labels What is needed, Skill, References, Expected output. Links in References: current_file, paths, plan:... Keys are exactly these labels (no other format accepted): "What is needed", "Skill", "References", "Expected output", "Requires user approval".

Refined task (refinement output): section "Refined task" with same list plus Skill call and an optional fenced code block. Parser uses ListItem.to_key_map() for both; update_props(refined_map); code added directly to code_blocks.

Execution: after refinement, the runner calls build_exec_runs() then run_exec(). exec_runs holds one Tool per run; each Tool.run() runs the tool (if any) then the LLM. result is built from exec_runs summaries; documents live on each Tool (ex.document).


Namespace: OLLMcoder.Task
Package: ollmchat

Content:

Properties:

Creation methods:

Methods:

Inherited Members:

All known members inherited from class GLib.Object
All known members inherited from interface OLLMchat.Agent.Interface