Docs

Installing, connecting, living in the village

Docs›By agent

Claude Code in Devalley

A Claude Code session is a resident in Devalley. Its resident brings you its permission requests and questions; you answer them in the village, read its answers and send the next instruction. Claude Code is the agent Devalley does the most for.

Its resident

Every Claude Code 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.

The first time it runs, Devalley offers to connect Claude Code. Sessions already running join on their next prompt, with no restart. It needs Claude Code 2.1.139 or later; with an older one the connect panel asks you to update.

Notifications

With Walking residents on, the resident strolls along the bottom of your screen with its name and project under its feet. When Claude Code 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 Claude Code asks for permission, its resident brings the request with a May I? bubble. The bubble opens its conversation, which shows what it wants to do (the command or the file; a long command unfolds whole) with Allow, Deny, Always allow and Answer in the terminal. Its multiple-choice questions are answered there too. With several residents, Waiting for you at the top of the conversation window's list has Allow and Deny right there. Nothing is allowed without your click.

In the conversation you read its last answer, send the next instruction and stop a turn. A session that went off because its terminal closed or the computer restarted sleeps as Off, and your next message wakes it on the same conversation with no terminal window. A session the village started with no window, on a Mac or inside WSL, also takes Claude Code's own slash commands from the box, such as /usage or /model, and files sent along with a prompt.

The usage card

The usage card has a line for Claude Code: how much of its limit is used and how long until it resets. Click it for each limit's used share and reset time, and the tokens used today and over the last 7 days, by project. On a Mac the agent nearest its limit stands in the menu bar, as in "Claude 48%"; on Windows the tray's Village window > Usage only keeps a small card on screen. When Claude Code's sign-in has expired, the card shows a sign-in button.

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
Answering permission requests and questions Yes Yes
Usage The tray's "Usage only" card In the menu bar
Waking a session that is off, with no terminal window Yes Yes
Sessions inside WSL Connected too Not applicable

What doesn't work

  • Some sessions in a terminal you opened yourself can't be written to from the village. They are still residents and their answers can be read, and the conversation says it can't send. To talk to one from the village, start it with Invite a resident.
  • A Claude Code older than 2.1.139 has to be updated.
  • The usage card shows no cost in dollars.
  • No sound, system notification or phone notification, and nothing can be answered from a phone.
  • No Linux installer yet.