Docs›By agent
OpenCode in Devalley
An OpenCode session is a resident in Devalley too. You allow or deny its permission requests in the village, and with OpenCode 2 or later you write to it from its conversation in whatever terminal it runs. It has no line on the usage card.
Its resident
Every OpenCode session you run becomes a resident of your village. The same agent in the same project is the same resident each time, with the same name and look, and a second session beside it joins as a companion. While the session works the resident is at a workplace; when a turn ends it cheers Done!; with nothing to do it rests. Click a resident for its card: its state in a word (Working, Needs you, Answer ready, Resting, Off, Error), its project and what you last asked it. Open conversation shows what it last answered.
Connect OpenCode at the village's telegraph office, or with Connect agents at the bottom right of the map. A running session moves in even before that, showing whether it is working or resting; once connected it also shows what it asks and what it answered.
Notifications
With Walking residents on, the resident strolls along the bottom of your screen with its name and project under its feet. When OpenCode asks you something it hurries to the middle of the screen and hops with a ? (or May I? for a request you can answer in the village) until you answer; when a turn is done it jumps and cheers Done!. On a Mac, At the notch shows the same beside the notch at the top of the screen. Devalley plays no sound and sends no system or phone notification.
Answering it from the village
When OpenCode asks for permission, its resident brings the request with a May I? bubble. In its conversation you read what it wants to do and answer with Allow or Deny. Nothing is allowed without your click.
With OpenCode 2 or later you can send a message and stop a turn from the conversation, in whatever terminal the session runs. Nothing needs setting up, and your own slash commands go the same way. OpenCode's built-in commands, such as /compact, are typed in its terminal.
The usage card
OpenCode has no line on the usage card: neither its limits nor its tokens are shown.
Windows and macOS
| Windows | macOS | |
|---|---|---|
| Its resident and state | Yes | Yes |
| Walking residents | Yes (above the taskbar) | Yes (beside the Dock) |
| At the notch | No | Yes |
| Allowing or denying permission requests | Yes | Yes |
| Writing to it from the conversation (OpenCode 2 or later) | Yes | Yes |
| Usage | None | None |
| Waking a session that is off, with no terminal window | No | No |
| Sessions inside WSL | Working or resting only | Not applicable |
What doesn't work
- The usage card shows nothing for OpenCode, neither limits nor tokens.
- Always allow can't be answered from the village: allow and deny only.
- A session that is off can't be woken from the village.
- OpenCode inside WSL isn't connected: it only shows as working or resting.
- With an OpenCode older than 2, writing from the conversation isn't available.
- No sound, system notification or phone notification, and nothing can be answered from a phone.
- No Linux installer yet.