← Back to context

Comment by rahimnathwani

1 day ago

I tried this three times. Twice a few days ago and once just now.

First time: it opened a MacOS VM and started to do stuff, but it got ahead of itself and starting typing things in the wrong place. So now that VM has a Finder window open, with a recent file that's called

  plt.ylabel('Price(USD)').sh

The second and third times, it launched the VM but failed to do anything, showing these errors:

  INFO:cua:VM run response: None
  INFO:cua:Waiting for VM to be ready...
  INFO:cua:Waiting for VM macos-sequoia-cua_latest to be ready (timeout: 600s)...
  INFO:cua:VM status changed to: stopped (after 0.0s)
  DEBUG:cua:Waiting for VM IP address... Current IP: None, Status: stopped
  DEBUG:cua:Waiting for VM IP address... Current IP: None, Status: stopped
  DEBUG:cua:Waiting for VM IP address... Current IP: None, Status: stopped
  INFO:cua:VM status changed to: running (after 12.4s)
  INFO:cua:VM macos-sequoia-cua_latest got IP address: 192.168.64.2 (after 12.4s)
  INFO:cua:VM is ready with IP: 192.168.64.2
  INFO:cua:Initializing interface for macos at 192.168.64.2
  INFO:cua.interface:Logger set to INFO level
  INFO:cua.interface.macos:Logger set to INFO level
  INFO:cua:Connecting to WebSocket interface...
  INFO:cua.interface.macos:Waiting for Computer API Server to be ready (timeout: 60s)...
  INFO:cua.interface.macos:Attempting WebSocket connection to ws://192.168.64.2:8000/ws
  WARNING:cua.interface.macos:Computer API Server connection lost. Will retry automatically.
  INFO:cua.interface.macos:Still waiting for Computer API Server... (elapsed: 10.0s, attempts: 11)
  INFO:cua.interface.macos:Still waiting for Computer API Server... (elapsed: 20.0s, attempts: 21)
  INFO:cua.interface.macos:Still waiting for Computer API Server... (elapsed: 30.0s, attempts: 31)
  WARNING:cua.interface.macos:Computer API Server connection lost. Will retry automatically.
  INFO:cua.interface.macos:Still waiting for Computer API Server... (elapsed: 40.0s, attempts: 41)
  INFO:cua.interface.macos:Still waiting for Computer API Server... (elapsed: 50.1s, attempts: 51)
  ERROR:cua.interface.macos:Could not connect to 192.168.64.2 after 60 seconds
  ERROR:cua:Failed to connect to WebSocket interface
  DEBUG:cua:Computer initialization took 76856.09ms
  ERROR:agent.core.agent:Error in agent run method: Could not connect to WebSocket interface at 192.168.64.2:8000/ws: Could not connect to 192.168.64.2 after 
  60 seconds
  WARNING:cua.interface.macos:Computer API Server connection lost. Will retry automatically.

This was using the gradio interface, with the agent loop provider as OMNI and the model as gemma3:4b-it-q4_K_M

These versions:

  cua-agent==0.1.29
  cua-computer==0.1.23
  cua-core==0.1.5
  cua-som==0.1.3

3 comments

rahimnathwani

Reply
frabonacci  1 day ago

Thanks for trying out c/ua! We still recommend pairing the Omni loop configuration with a more capable VLM, such as Qwen2.5-VL 32B, or using a cloud LLM provider like Sonnet 3.7 or OpenAI GPT-4.1. While we believe that in the coming months we'll see better-performing quantized models that require less memory for local inference, truth is we're not quite there yet.

Stay tuned - we're also releasing support for UI-Tars-1.5 7B this week! It offers excellent speed and accuracy, and best of all, it doesn't require bounding box detection (Omni) since it's a pixel-native model.