Assistant Actions v2

[russell-rozenbaum]

Overview

Russ, Todos

Code Cleanup

• Namely, AssistantUpdate.re file and CompositionModel.re file. Do so via: Organize into Modules -> Further Separate Concerns into Submodules -> Split into Files/Folders if necessary -> Supply "Public" Modules (I find this helps with clarity on what is local/helper and what is external/publicly used)

Task Nodules and Before/After Views

• Store tool calls with each subtask. This can be done via tracking when a tool is called and which task was marked as active.
• Store a before segment and after segment. Simply, store what the segment was when the task/todo list was created, then, store what it is when it is completed. NOTE: Need to add a task completion action. Currently, only archiving a task exists.

Add Tool Calls for Agent to Test Code it Writes

• ^

Write Robust Test Cases

• Composition Action Tests
• Assistant Model/Update Tests

Improve Agent View Logic

• We might want to default to expanding the definitions of recently implemented code

General Agent Toolkit Improvements

• Rename UpdateBody to something else, leaning towards UpdateScope. The agent seems to get confused sometimes as to what exactly the body is. Understandably so tho, eg. "function bodies" could lead to some confusion, or the fact that updating the ultimate, final body of a program is just updating the last defined variable's body... oftentimes it tries to call "UpdateBody" on a variable called "root".

Cyrus, Todos

[cyrus-]

see #2048