Browser Agent v0.4.17 - THE FIX: Results Now Returned!

🎉 Release v0.4.17 - THE FIX IS HERE!

This release fixes the root cause of missing step results. Your extracted data will now be properly returned!

🔍 Root Cause Found

The execute_step() method was returning None instead of the result dictionary:

# BEFORE (line 510-526):
async def execute_step(self, step: Dict[str, Any]) -> None:  # ← Returns None!
    result = await self._execute_step(step, step_num=0)
    if not result.get("success"):
        raise Exception(...)
    # ← Missing return statement!

# AFTER:
async def execute_step(self, step: Dict[str, Any]) -> Dict[str, Any]:  # ← Returns Dict!
    result = await self._execute_step(step, step_num=0)
    if not result.get("success"):
        raise Exception(...)
    return result  # ← THE FIX!

🐛 The Bug

WorkflowExecutor was calling execute_step() and getting None back, so it couldn't collect:

• Extracted data from vision LLM
• Screenshot URIs
• Any step results

✅ What's Fixed

• Extracted Data: Vision LLM extraction results now properly returned
• Screenshots: Screenshot S3 URIs now collected in screenshots array
• Step Results: All action results (fill, click, extract, etc.) now available
• Complete Output: step_results array now populated with full execution details

📊 Expected Output

With v0.4.17, you should see:

{
  "success": true,
  "steps_executed": 6,
  "step_results": [
    {
      "success": true,
      "action": "extract",
      "method": "vision",
      "data": {
        "fttp_avail": true,
        "sogea_avail": true,
        "soadsl_dsl_speed": 330,
        ...
      }
    },
    ...
  ],
  "screenshots": ["s3://bucket/screenshot1.png", ...]
}

🔬 Debug Logs

The debug logs will confirm the fix:

[DISPATCH] execute_step returned: type=<class 'dict'>, is_none=False
→ Collecting step result: extract, success=True
→ Extracted data collected: ['fttp_avail', 'sogea_avail', ...]
→ Workflow collected N step results

🙏 Thanks

Special thanks for the patience during the debug process. The aggressive tracing in v0.4.16 pinpointed the exact issue, making this fix possible!

🚀 Upgrade Path

Simply download and run the Windows bundle. No workflow changes needed!