The backend services for this research run inside a tmux session to keep the OpenHands research extension alive while automation proceeds. To restart the environment the following command was used successfully:
tmux send-keys -t uagent-backend 'source /Users/wuy/Desktop/code/UAgent/.venv/bin/activate && cd /Users/wuy/Desktop/code/UAgent && ./start_openhands_research.sh' C-m
After the backend is up, open the OpenHands UI (served on http://localhost:2999) and start a new conversation with the detailed research goal to trigger the automated workflow.
The following shell commands have already completed successfully inside the research workspace (/workspace/ml-query-routing). They should be re-run in order when reproducing the environment setup:
mkdir -p /workspace/ml-query-routing/{postgres,pg_duckdb,data,experiments,models,logs}echo "Checking available tools..." && which git && which wget && which curlgit config --global --unset http.proxy && git config --global --unset https.proxycd /workspace/ml-query-routing/postgres && wget https://ftp.postgresql.org/pub/source/v15.3/postgresql-15.3.tar.gzcd /workspace/ml-query-routing/postgres && tar -xzf postgresql-15.3.tar.gzcd /workspace/ml-query-routing/pg_duckdb && git clone https://github.com/duckdb/pg_duckdb.gitcd /workspace/ml-query-routing/postgres && rm -rf postgresql-15.3 && mkdir postgresql-15.3 && tar -xzf postgresql-15.3.tar.gz -C postgresql-15.3 --strip-components=1
Note: Additional commands (feature extraction, data collection, model training, etc.) will be appended to this list as the automated research workflow progresses.