CEO at Ona (formerly Gitpod) here. Every ephemeral environment Ona creates can directly connect to your Desktop IDE for easy handoff. Our team goes from prompt -> iterating in conversation -> VS Code Web -> VS Code Desktop/Cursor depending on task complexity and quality of the agent output. We call this progressive engagement and have written about it here https://ona.com/docs/ona/best-practices#progressive-engageme...
Thanks, I'll give it a shot. I wish your site would show me what it actually looks like. It's a lot of words and fancy marketing images and I have no feel for the product. It leaves me unsure if I should invest my time.
I'd love to see a short animation of what it would actually look like to do the core flow. Prompt -> environment creation -> iterating -> popping open VSCode Web -> Popping open Cursor desktop.
Also, a lot of the links on that page you linked me to are broken:
* "manual edits and Ona Agents is very powerful."
* "Ona’s automations.yaml extends it with tasks and services"
* "devcontainer.json describes the tools"
I signed up and tried it with Cursor. It is very close, but still has a lot of rough edges that make it hard to switch:
* Once in Cursor I can't click on modified files or lines and have my IDE jump to it. Very hard to review changes.
* I closed the Ona tab and couldn't figure out how to get it back so I could prompt it again.
* I can't pin the Ona tab to the right like Cursor does
* Is there a way to select lines and add them to context?
* Is there a way I can pick a model?
Gitpod | Fully Remote | Multiple Open Source Senior Engineering Roles | Full Time
gitpod.io is an open-source developer platform that provisions and orchestrated developer environments in the cloud. We are backed by General Catalyst and more than 450,000 developers use the platform.
We are building both company and product in the public:
Ok that's cute, but hn guidelines say the the post title should match the published title. The flexibility is for necessary shortening or scrubbing clickbait, not for editorializing.
> Otherwise please use the original title, unless it is misleading or linkbait; don't editorialize.
Essentially, we run nightly builds at OpenVSCode Server making it as upstream to VS Code as possible. In contrast to other forks the whole scope of the project is to add a minimal set of changes (specifics about what we added https://github.com/gitpod-io/openvscode-server/blob/main/doc...)
The architecture we use powers both Gitpod and GitHub Codespaces. Several of the devs and organisations that have asked for our implementation & now have adopted OpenVSCode Server referenced the following issue at Code-Server (https://github.com/cdr/code-server/issues/3835).
github.dev is solely the VSCode frontend/editor without access to any compute. OpenVSCode Server allows you to run VS Code on a remote machine and access it with a thin client through the browser. Unlike github.dev you get full access to the underlying OS and can run tests, compilation, install dependencies etc.
Essentially, we run nightly builds at OpenVSCode Server making it as upstream to VS Code as possible. In contrast to other forks the whole scope of the project is to add a minimal set of changes (specifics about what we added https://github.com/gitpod-io/openvscode-server/blob/main/doc...)
The architecture we use powers both Gitpod and GitHub Codespaces. Several of the devs and organisations that have asked for our implementation & now have adopted OpenVSCode Server referenced the following issue at Code-Server (https://github.com/cdr/code-server/issues/3835).
Hey! Thanks for the explanation, but I don’t fully understand the two projects. Is this built with code-server, or do the server parts of Gitpod come from Microsoft? Where should I submit PRs?
Hi, Mike from Gitpod here. This project does not use code-server. It is instead a very lightweight server added to the official open source VS Code repo from Microsoft.
Gitpod is all about provisioning and orchestrating ephemeral developer environments (think about it as a resource efficient and powerful orchestration platform for your dev envs).An IDE is just one building block of a working cloud based developer environment, in addition to the operating system, databases, compilers and all the other tools you need to be productive. At Gitpod we want to support the IDE or editor you like best, and providing VS Code through the web browser is just one possibility. Alternatively, you can access your Gitpod workspaces through SSH, local VS Code and soon your favorite Jetbrains IDEs.
If you have a machine somewhere which you would like to access with VS Code through a browser, check out OpenVSCode Server. If you need control over your infrastructure and would like the orchestration capabilities that Gitpod offer you can self host Gitpod.
