Operations¶
This page covers day-to-day care of OpenCode Coding Assistant: access, the first-boot unit, backups, moving to another image, and support.
Security model¶
- Terminal only. You start
opencodeyourself. The image does not run a persistent web listener. - No provider key on the image. You add credentials after launch, or you attach a Bedrock role. The local fixture does not use those credentials.
- Ordinary-user execution. Run the assistant and the walkthrough as
ubuntu. - Session Manager. The listing's connection path is a Session Manager shell. Leave inbound application ports closed.
- Task output. Provider replies and the fixture output can contain project source. Keep files that hold secrets out of tickets and shared logs.
First boot¶
sushi-opencode-firstboot.service prepares the sample workspace and keeps
existing work. After a restart, check it with:
There is no long-running OpenCode service to restart. A new opencode command
is a new terminal session.
Backups¶
Before you replace the instance, back up:
- the project directory you edited
- OpenCode user data and session state
~/opencode-demoif you still need the fixture output
Restarts and reboots keep existing work. The image notes in
/opt/sushi/docs/README.md are the package reference for the session-state
location.
Updates¶
A new Marketplace version is a new instance. Back up the project, user data, and session state, launch the replacement, and restore what you need. Review the task output on the instance before you share it.
Support¶
Software Sushi provides packaging and setup guidance for this image. Email
info@softwaresushi.com with the Marketplace
version (opencode --version), the Region, and what you ran. Omit provider
keys, tokens, and raw task logs that contain project source.
Support beyond installation questions needs a separate agreement. Upstream OpenCode support is not included. Legal and refund terms are on the offer. The OpenCode documentation describes the upstream project.
Last updated October 27, 2026 · Suggest an improvement