Move state mutating tools to actions - #312
Conversation
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## refactor/actions-core #312 +/- ##
=========================================================
+ Coverage 88.86% 91.15% +2.28%
=========================================================
Files 26 25 -1
Lines 2344 2600 +256
=========================================================
+ Hits 2083 2370 +287
+ Misses 261 230 -31 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
Partly addresses #148.
This PR is stacked on #311.
Summary
This PR migrates the existing state-changing built-ins from tools to actions.
move_one_step,teleport_to_location, andspeak_tonow execute through the action path, and examples are updated to configure and call committed behavior withactions=/act(...).Motive
State-changing simulation behavior should not depend on provider tool calls. With the action core in place, movement and messaging can be validated and executed locally as actions, while tool factories remain reserved for read-only deliberation helpers.
Implementation
move_one_step,teleport_to_location, andspeak_tointomesa_llm.actions.default_actions()returns onlywait,spatial_actions()returns movement actions, andsocial_actions()returnsspeak_to.legacy_tools()as a forward migration path; read-only tool factories currently return empty tuples.actions.py,actions=,act(...), andaact(...).Usage Examples