You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
V2 terminal security boundary
The TUI runs as uid 60001; the V2 server runs as root for HAOS compatibility.
Home Assistant configuration is mounted at /homeassistant.
Use opencode status to inspect this server without starting another service.
OpenCode could not start: unrecognized migration work needs attention.
Your conversations and the unknown entry were preserved.
The add-on log identifies its bounded name and type beside 'unexpected_migration_work'.
Keep your backup and share that diagnostic in the issue; do not delete unknown work entries.
To return to 2.x, restore your pre-upgrade Home Assistant backup (app and data).
Restart the add-on after a corrected update to retry. This screen stays open.
This error screen comes from the Home Assistant add-on (v3.2.3), not from OpenCode itself. The add-on runs its own check before it starts OpenCode V2 (2.0.26 here). The screen says the details are in the add-on log, so we need that log to tell whether OpenCode or the add-on is the problem. Could you share:
The add-on log from startup, especially the lines around unexpected_migration_work, which should include the name and type of the entry it didn't recognise. Please remove any tokens or other secrets first.
Your Home Assistant OS version.
The add-on version (and OpenCode version) you upgraded from, and whether this started right after the upgrade.
If the log shows the problem is in the add-on's own checks, it's probably best to report it to the add-on's maintainers as well.
You can reply here with the details or edit the issue. If you edit it, please also leave a comment saying you've updated it, so we know you're done.
These existing issues may be related, ordered from most to least likely:
Closing this for now, since we haven't heard back. To work out whether OpenCode V2 or the Home Assistant add-on's own startup check causes the unexpected_migration_work error, we need the add-on log lines around that message (the name and type of the entry it didn't recognise) and the versions you upgraded from.
If you can still share those, please reply here or open a new issue with the log (remove any secrets first), and we'll take another look. #52376 tracks the same error after the 3.1.0 add-on update, in case you want to follow it. Thanks!
Activity
opencode-agent commentedon Oct 18, 2026
Thanks for the report, @mtfred99!
This error screen comes from the Home Assistant add-on (v3.2.3), not from OpenCode itself. The add-on runs its own check before it starts OpenCode V2 (2.0.26 here). The screen says the details are in the add-on log, so we need that log to tell whether OpenCode or the add-on is the problem. Could you share:
unexpected_migration_work, which should include the name and type of the entry it didn't recognise. Please remove any tokens or other secrets first.If the log shows the problem is in the add-on's own checks, it's probably best to report it to the add-on's maintainers as well.
You can reply here with the details or edit the issue. If you edit it, please also leave a comment saying you've updated it, so we know you're done.
These existing issues may be related, ordered from most to least likely:
unexpected_migration_workfailure after updating the add-on to 3.1.0 (OpenCode 2.0.13)no such column: pathopencode-agent commentedon Oct 21, 2026
Closing this for now, since we haven't heard back. To work out whether OpenCode V2 or the Home Assistant add-on's own startup check causes the
unexpected_migration_workerror, we need the add-on log lines around that message (the name and type of the entry it didn't recognise) and the versions you upgraded from.If you can still share those, please reply here or open a new issue with the log (remove any secrets first), and we'll take another look. #52376 tracks the same error after the 3.1.0 add-on update, in case you want to follow it. Thanks!