Skip to content

fix: store ui_state in context store before code execution #275

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
adntgv wants to merge 1 commit into
base: main
Choose a base branch
from
Open

fix: store ui_state in context store before code execution #275

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion .gitignore
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -40,4 +40,6 @@ frontend/

reddit_python_posts.json

test/
test/
venvrun.sh
run.sh
3 changes: 3 additions & 0 deletions droidrun/agent/codeact/codeact_agent.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -343,6 +343,9 @@ async def handle_llm_input(
activity_name=phone_state.get("currentApp", "Unknown"),
)

# Store ui_state so it's available during code execution
await ctx.store.set("ui_state", a11y_tree)

# Stream formatted state for trajectory
ctx.write_event_to_stream(RecordUIStateEvent(ui_state=a11y_tree))

Expand Down
4 changes: 3 additions & 1 deletion droidrun/config/prompts/executor/system.jinja2
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -93,8 +93,10 @@ No actions have been taken yet.
Whatever the current subgoal says to do, do that EXACTLY. Do not substitute with what you think is better. Do not optimize. Do not consider screen state. Parse the subgoal text literally and execute the matching atomic action.

IMPORTANT:
1. Do NOT repeat previously failed actions multiple times. Try changing to another action.
1. Do NOT repeat previously failed actions multiple times. If an action failed, try a DIFFERENT action or approach.
2. Must do the current subgoal.
3. If you have tried the same action 2+ times and it keeps failing, try a completely different approach. If truly stuck with no viable action, use `{"action": "wait", "duration": 1.0}` as a fallback and explain why in the Description (e.g., "No actionable element found for subgoal").
4. ALWAYS output a valid action. There is no "skip" or "do nothing" option — use `wait` with duration 1.0 if uncertain.

Provide your output in the following format, which contains three parts:

Expand Down