Monitor Claude Code sessions with See Claude

Set up one view of the sessions

Luke built See Claude after losing track of multiple Claude Code terminals. The March description presents a free open-source local dashboard implemented as one Node.js file with no extra dependencies. The retained repository also advertises pixel-art workers, which are a display feature rather than evidence that a task has completed.

1. Open https://github.com/lukejbyrne/see-claude and follow the repository’s setup for the local dashboard. Identify the Claude Code sessions and project directories you expect to see before creating additional sessions.
2. Compare the dashboard entries with your actual terminals. Give the projects recognisable names or context where the interface permits, so similar sessions are not confused during a later handoff.

Inspect history before messaging a terminal

The walkthrough covers sending messages and viewing history at 1:22. A session can be idle because it is finished, waiting for input or stopped on a problem. Read its state and recent work before sending an instruction; a new message should refer to the project the terminal is actually handling.

1. Choose one known session and inspect its history against the corresponding terminal. Confirm the working directory and last requested task before preparing a follow-up.
2. Send a small, unambiguous instruction through the dashboard and verify it reaches the intended terminal. Inspect the resulting output rather than treating the dashboard’s submission as proof of execution.

Create sessions and use activity as a signal

At 2:00 Luke creates a new session with a project directory and first message, then checks active and idle status at 2:23. The dashboard centralises control; the code, files and test results remain the evidence for the underlying job.

1. Create one session for a specific project directory and a bounded first task. Check the new terminal’s location and initial response before adding more work.
2. Use the active/idle view to decide which session needs attention, then read its actual result. Verify saved changes and unresolved questions before calling the task complete or resuming an older session.

The takeaway

Use the dashboard to locate and coordinate work. Session activity helps direct attention, while the terminal history and saved results establish what happened.