Docs›By agent
Codex in Devalley
A Codex session is a resident in Devalley too. Its resident brings you its approval requests, you allow or deny them in the village, and the usage card shows Codex's limits. Sessions of the Codex CLI in a terminal and of the Codex desktop app both appear in the village.
Its resident
Every Codex 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 Codex 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. Sessions in the Codex desktop app, and Codex in your editor, move in as residents too: working while a turn runs, cheering when it ends, with a card that brings the Codex app forward.
Notifications
With Walking residents on, the resident strolls along the bottom of your screen with its name and project under its feet. When Codex 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 Codex asks for approval, 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, or send it back to its own terminal with Answer in the terminal. Nothing is allowed without your click.
In the conversation you read its last answer. To a session started from the village you can also send the next instruction. On a Mac, a message to a session that is off wakes it on the same conversation with no terminal window, and a session woken that way runs until you turn it off.
The usage card
The usage card has a line for Codex: 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 Codex'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 |
| Allowing or denying approval requests | Yes | Yes |
| Usage | The tray's "Usage only" card | In the menu bar |
| Waking a session that is off, with no terminal window | Not on Windows itself | Yes |
| Sessions inside WSL | Connected too | Not applicable |
What doesn't work
- There is no Always allow and no multiple-choice answering for Codex. Whatever else Codex asks on its own screen is answered in its terminal.
- A session that ran on Windows itself can't be woken from the village once it is off.
- A thread of the Codex app can't be turned off from the village; end it in the Codex app.
- When a session can't be written to from the village, its conversation says so.
- 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.