-
Notifications
You must be signed in to change notification settings - Fork 290
Open
Description
The problem
The only way to build and test an ability is through the web dashboard. No local testing, no CLI, no git deploy. To test anything, you must publish it live first.
Current steps to update an ability:
- Write code
- Zip and upload the file manually
- Fill out a form
- Delete the old version
- Turn it on
- Wait — no status shown
This is slow and creates friction for developers.
What we want
Short term — CLI tool
Let developers deploy from the terminal:
openhome login— authenticate to your accountopenhome deploy ./my-ability— zip and upload directlyopenhome test ./my-ability— deploy to a staging version on your agent- Show real-time deploy status so developers know when their ability is live
Long term — Git-based workflow (similar to Vercel / Netlify)
- Connect a GitHub repo to OpenHome
- Push to a branch → ability auto-deploys to a private test version
- Merge to main → ability goes public on the marketplace
- Developers never have to publish just to test
Questions for the team
- Is the GitHub integration already planned? What will it do?
- Can abilities run locally on the Pi for testing?
- Is cloud-only a permanent decision, or just not built yet?
- How will community contributions be reviewed as the repo grows?
- Will the GitHub repo and the dashboard account ever be connected?
Suggested roadmap
- Short term — Fix the Live Editor so testing in the cloud is fast (Bug: Live Editor testing broken + security scanner false positives on string content #218)
- Medium term — CLI tool (
openhome deploy ./my-ability) - Long term — GitHub repo linking, branch deploys, PR-to-marketplace flow
Would remove a lot of friction and bring the workflow closer to what developers are used to with tools like Vercel or Netlify.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels