OpenHands

<@U07TE39J96U> how close are you to getting an official install path up?

should be done ill cut a beta release today so we can test it

<@U0ASNMYHAFN> do you have the latest version of automations set for agent sdk? Do you need another pre-release for automations?

I do - there was one fix I'd like to get in there...

Yes - but I see a test error which did not appear on the branch

I can wait for the fix to be merged, any idea of eta?

(I was slowed down because of running out of credits)

(Timestamps coming back via rest there now include the fact that they are in UTC, rather than providing no details so that the frontend assumes they are local)

<@U07TE39J96U> can you post when the release is ready, and what the new install commands/instructions are? From there, we can divvy up testing with fresh installs :pray::thanks-on-a-stick:

Release is cut, docker install

```docker pull ghcr.io/openhands/agent-canvas:1.0.0-alpha.4

docker run -it --rm \
  -p 8000:8000 \
  -v ~/.openhands:/home/openhands/.openhands \
  -v ${PROJECT_PATH}:/projects \
  ghcr.io/openhands/agent-canvas:1.0.0-alpha.4```

Npm install

```npm install -g @openhands/agent-canvas

agent-canvas```


The npm install is failing at the moment because we're using a git sha for the openhands typescript client

Putting in a fix and tagging another release, will lyk when the npm install path is ready

Should it be ...
```docker run -it --rm \
  -p 8000:8000 \
  -v ~/.openhands:/home/openhands/.openhands \
  -v ${PROJECT_PATH}:/projects \
  <http://ghcr.io/openhands/agent-canvas:1.0.0-alpha.4|ghcr.io/openhands/agent-canvas:1.0.0-alpha.4>```

ah yes thanks for the catch, will edit the msg above