Some notes about the onboarding experience: We might want to put automations more front and center, since they’re a core feature of the canvas. An idea of how we can do this: • Move the “create a website with openhands” thing to the bottom of the final screen instead of top (or remove it entirely). • Instead ask people a few questions like “where do you store your source code, how do you communicate with your team, how do you store tickets”, allow people to pick repos that they want to work on, and suggest automations for them based on the characteristics of the repo (e.g. if they use github, slack, and linear, suggest automations that work with those tools). cc @hundreds-twilight-32833

One detail here, FWIW: every time I went through onboarding, I never finished by creating an automation. The reason is it seems ALL of them require some token, and while that’s not impossible, it’s kinda … well, I didn’t have a token at hand. So I’d have had to look for one… when I was just looking forward to finish my setup to talk to the agent.

I'd like to separate the idea of Onboarding from Setup and reduce Setup down to a single step as much as possible (github.com/OpenHands/OpenHands/issues/15423). Then onboarding could definitely include connecting to git and issues to make automations easier to run.

Yeah, I agree, it’s definitely more work to create an automation. Another option is to suggest this frequently in the front page.

@breezy-kilobyte-39430 has branch with an onboarding widget that lives on top of conversations. Looks like this and could help move onboarding past that first config flow we have now

Alternatively, if we had some automation that requires nothing, it just works, and shows the user what it can do, might be nice. I’m reminded that I had an incredible surprise with my agent, when it made idk what image (for its own avatar I think it was), and unprompted, it used a web service to upload it, so it could send me the URL. It knew a web service that required no login, no account, it just uploaded there and sent me the link 🤯

This was an idea that came in from somewhere I have saved: "Easy to enable starter automations that can be enabled without an LLM conversation to setup - One-click or minimal configuration automations so Agent Canvas becomes a developer's daily driver. Example: An automation to auto create and improve skills based on conversation data that runs once a week."

Yeah, I saw that idea, but didn’t understand why that wouldn’t need an LLM

🐾 Verified — and one correction up front: htmlpreview is not a GitHub service. It's a third-party project (

htmlpreview/htmlpreview.github.com

, by Jerzy Głowacki / "niu tech", Apache-2.0) that just happens to be hosted on

<http://github.io|github.io>

. GitHub itself doesn't offer it. What it actually is: a client-side renderer + CORS proxy. You prepend

<https://htmlpreview.github.io/>?

to the URL of an HTML file that's already on GitHub/BitBucket, and it fetches that file through a CORS proxy and renders it in your browser instead of showing raw source (GitHub serves raw files as

text/plain

, so they don't render on their own). Example:

<https://htmlpreview.github.io/?https://github.com/user/repo/blob/main/page.html>

. So on your actual question — can you upload/display an HTML page on it without a GH token? • Display: yes, with no token, if the file is already at a public URL. It's a viewer, so it reads an existing public file and renders it. No auth to view. • Upload: no — htmlpreview has no upload. It doesn't host anything; it only renders a URL you give it. To get the HTML onto GitHub in the first place you need a repo (and pushing needs auth). So it doesn't give you the "no-login, just-upload-and-get-a-link" behavior. That zero-friction upload thing you remembered your agent doing is a different kind of service — an anonymous file/paste host (something like

<http://0x0.st|0x0.st>

,

<http://tmpfiles.org|tmpfiles.org>

,

transfer.sh

, or a paste service) that accepts an anonymous

POST

and hands back a URL. htmlpreview is the opposite end: it assumes the file is already hosted and just makes it viewable. If the onboarding goal is "an automation that produces a shareable page with no token," an anon upload/paste host is the closer fit; htmlpreview only helps if the output already lives in a public repo. 🐾

Oh yea, the wording there is wrong isn't it. Maybe it got garbled when I was moving those all around. I think that was 2 different ideas. One-click no LLM, one-click easy to use automation

Cool, thanks! I do think that it’d be good to make adding automations more front and center and obvious.

Yes, I would say that is already in progress

Great, thanks!