Migrate OpenComputer integration to v2 SDK
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- terraform, typescript
- Domain
- cloud, infrastructure
Research direction
Start by locating the image builder, provider adapter, and lifecycle/checkpoint integration that use the OpenComputer SDK. Review the v2 API migration requirements, then run the provider-backed create, checkpoint, restore, and shutdown coverage. Done means the managed snapshot builds, production Terraform apply succeeds, and the shutdown-snapshot canary preserves and restores sentinels.
Written by the indexing model from the issue text.
Description
Context
Production OpenComputer enablement failed during the managed base-snapshot build because @opencomputer/sdk ^0.9.1 calls the retired v1 API. The provider returns 410 v1_retired before snapshot creation.
Scope
- Upgrade the OpenComputer SDK to v2 and adapt the image builder, provider adapter, and lifecycle/checkpoint integration to the v2 API.
- Rebuild and validate the managed OpenComputer base snapshot.
- Add or update provider-backed coverage for create, checkpoint, restore, and shutdown behavior.
- Run a production Terraform apply and OpenComputer shutdown-snapshot canary before switching the default provider.
Acceptance criteria
- A production OpenComputer apply completes without a v1-retired response.
- A new OpenComputer session starts from the managed template.
- The shutdown-snapshot canary preserves sentinels and restores successfully.
- Dominant language
- TypeScript
- Stars
- 3.3k
- Forks
- 477
- Avg merge
- 18h 32m
- Merged PRs (30d)
- 313
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from ColeMurray/background-agents
-
Known-actor email claim race drops the subject_email_collision warningPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
ColeMurray/background-agents#2334 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
ColeMurray/background-agents#806 ·
Maintainers usually reply within 1 day
-
Support Opencode v2Open
Difficulty 5/5 Over a week Newbie friendliness 25/100
ColeMurray/background-agents#2428 ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 8/100
ColeMurray/background-agents#2427 ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 8/100
ColeMurray/background-agents#2426 ·
Maintainers usually reply within 1 day
All issues in ColeMurray/background-agents
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
TomerAberbach/profiler-md#733 ·
Maintainers usually reply within 1 day
-
bug priority: medium
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
brentspine/brents-toasts#143 ·
-
🐛 bug 🗺️ DB Models & Ops
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
LibreChat-AI/LibreChat#17214 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
Wavvon/Wavvon-clients#136 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
umami-software/umami#4637 ·
Maintainers usually reply within 3 days