Sessions
Every running agent operates inside a tmux session. Sessions let you observe, interact with, and manage agent processes in real time.
How Sessions Work
When you start work on a ticket, Proletariat creates a tmux session for the assigned agent. The session runs the AI coding tool (e.g., Claude Code) with the ticket injected as a prompt. Sessions persist even if you close your terminal — agents keep working in the background.
Listing Sessions
$ prlt session list bezos TKT-001 active 2h 15m musk TKT-003 active 45m gates TKT-007 idle —
Attaching to a Session
Attach to see exactly what an agent is doing in real time. You'll drop into the tmux session and can watch the agent code, run tests, and commit.
# Attach to an agent's session $ prlt session attach bezos # Detach when done (standard tmux shortcut) # Press Ctrl+B then D
Note
Attaching is read-write — you can type in the session to help the agent, but be careful not to interfere with its work.
Peeking at Output
Peek gives you a read-only snapshot of an agent's recent output without attaching to the session:
# View recent output from an agent $ prlt session peek bezos
Poking an Agent
Send a message to a running agent without attaching. This is useful for giving hints or redirecting work:
# Send a message to a running agent $ prlt session poke bezos "Skip the UI tests, focus on the API" $ prlt session poke musk "The build is failing because of a missing env var"
Session Health
Check the health of all running sessions to detect stuck or crashed agents:
$ prlt session health bezos healthy responding musk healthy responding gates unhealthy no output for 30m
Creating & Managing Sessions
# Create a session manually $ prlt session create --agent bezos # Detach a session $ prlt session detach bezos