Terminal

The workspace's panes belong to a local server, not to the window you look at. That is why closing the workspace never stops an agent.

uze workspace          # attach the workspace, starting its server when needed
uze workspace stop     # stop this workspace's server and every process in it

Running uze workspace inside one of the workspace's own panes does not nest a second workspace: it opens a space for that directory in the one already running.

Resuming after a reboot

The server does not survive a reboot, but your work does. The next uze workspace brings back the spaces, tabs and agents, each relaunched in its checkout and resuming the conversation it was in.

That resume is done by the shim uze setup creates for each agent in ~/.uze/shims/. The workspace launches agents through it, and puts ~/.uze/shims first on PATH in every pane, so an agent you type into a pane goes through it too. Your own shell is never edited: an agent you start in any other terminal is the agent's own binary, exactly as it would be without uze.

Besides the resume, the shim carries what some agents do not read on their own: the project's .agents/skills and .agents/agents for Claude Code, and the project's agents for Codex. Those reach them inside the workspace only; the plugins you install reach every agent everywhere. Whether each agent supports the resume is the Session column in Harnesses.

If a pane's shell puts another copy of an agent ahead of the shims (a version manager such as mise, asdf or nvm can), the workspace says so the first time that agent runs there: its conversation will not resume after a restart, and the project's own skills may not reach it.

Prompt history

What you send to an agent is recorded per space. The agent context drawer, opened from the mark at the end of the tab strip, lists it under what the agent runs on: that agent's own prompts, or with tab the whole space's, to read. It is a convenience, not a transcript: uze forwards keystrokes without interpreting them, so entries can be missing. The file is readable only by you, and x twice in the drawer clears the space's.

Notifications

uze config notification takes three states:

It is your terminal's own bell, rung after an agent has stayed finished for about ten seconds; agents finishing together ring once.

Logs

The workspace and its server keep a journal without being asked, in ~/.uze/cache/logs/, rolled daily and kept for a week. For a trace of a single command, set UZE_LOG=info.