Troubleshooting¶
Checks for the failures the OpenCode listing and its published getting-started
page call out. The image notes are /opt/sushi/docs/README.md.
opencode --version is not found¶
Cause: the shell is not the ubuntu account the package prepares, or
first boot has not finished.
Fix: wait for cloud-init, switch user, and check the first-boot unit:
sudo cloud-init status --wait
sudo -iu ubuntu
opencode --version
sudo systemctl status sushi-opencode-firstboot.service
The walkthrough passes and a later model call still fails¶
Cause: bash /opt/sushi/docs/demo.sh and
python3 /opt/opencode/inputs.py verify run a labelled local fixture. They
do not contact your provider and do not show that a commercial model answered.
Fix: treat a fixture pass as a file-edit check only. For Amazon Nova Lite,
confirm the instance role can invoke amazon.nova-lite-v1:0 in us-east-1,
model access is enabled, and the command sets AWS_REGION=us-east-1 and
AWS_PROFILE=default. See Use your own provider.
The assistant changed files you did not want to keep¶
Cause: the coding tools can edit the working directory. The documented Bedrock example asks for a small change to the calculator.
Fix: run it in a directory you can restore. Read the diff and run your tests before you keep the edit.
A failed task printed project data¶
Cause: provider messages and task output can include source from the workspace.
Fix: read the output on the instance. Remove secrets before you copy any of it into a ticket. Email info@softwaresushi.com with the Marketplace version and a short description of the failure.
Last updated October 27, 2026 · Suggest an improvement