Know when you're needed.

One place that shows which of your Claude Code and Codex sessions need you, and takes you straight to them.

You keep working in Claude Code and Codex as you do today, in the terminal or their apps. baum doesn’t replace them. It watches your sessions and tells you when one needs you, so you don’t have to keep checking every window.

The Sessions page shows sessions that need you, sessions that are running, and sessions that ended in the last day.

Focus: jump to the session that needs you

When a session needs you, baum takes you straight to it:

See it. The session appears at the top of the Sessions page, in the tray menu and as a notification. Clicking the notification opens it in baum.
Focus it. Click Focus session, or press f. baum brings the session’s own tmux pane, terminal tab or Claude app conversation to the front, so you carry on right where the agent stopped.

Focus goes straight to the session in tmux, in kitty (with remote control turned on), in iTerm2 and Terminal on macOS, and in the Claude app. In other terminals it brings the window forward and the button reads Show window. On Linux this works with X11 or Hyprland; other Wayland desktops, such as GNOME and KDE, don’t let baum bring a window forward.

How baum sees a session

When you connect an agent during setup or in Settings → Connections → Agent hooks, baum installs its plugin in Claude Code or Codex. The plugin tells baum when a session starts, when you send a prompt, when it asks for permission and when it ends. baum then reads the session’s transcript from your disk to show its progress.

The plugin sends baum only identifiers: the session ID, its folder and the event. Your prompts and tool output stay in the agent’s own transcript on your disk. Nothing is ever sent to us.

What you can do from the Sessions page

See what needs you. Sessions waiting for a permission, an answer or your next prompt are listed first, and the tray icon and notifications tell you when there is one.
Jump to the session with Focus session, as above.
Answer quick ones in place. For a simple permission request or question, answer from baum. Claude Code still shows the same prompt in your terminal, and the first answer wins. To answer Codex approvals from baum, turn on Settings → Answering agents → Answer Codex approvals from the app.
Read the transcript, live while the session runs.

Why can’t I see a session?

Go through the steps below. Check this computer in Settings detects most of them.

The session started before you connected baum

This is the most common cause. Agents load plugins only when a session starts, so a session that was already open when you connected an agent, or updated its plugin, never reports to baum.

Codex’s hooks aren’t approved

Codex runs a plugin’s hooks only after you approve them, and again after an update changes them. Settings shows Needs approval next to Codex.

The `baum` command isn’t installed

The plugin runs the baum command. If it isn’t on your PATH, the plugin does nothing.

The session isn’t in one of your repositories

baum only shows sessions whose working folder is inside the clone of a repository you added. A session in another folder, or outside a Git repository, is not shown.

baum is stopped

Quit and stop background reviews in the tray menu stops baum’s background service, and sessions are not recorded until you open baum again. Quitting with Quit leaves the service running.

The session ended a while ago

The page shows sessions that ended in the last day. A session that has been silent for two hours is dropped unless its agent is still running.

The agent isn’t supported

baum shows Claude Code and Codex sessions. Other agents, and Claude Code or Codex older than 2.1.248 and 0.156.1, are not supported.