Working with it

LampMaster

The reviewer: a look across all your sessions at once, for the links none of them can see, off until you switch it on.

Every session sees only itself. One is stuck on an error another fixed yesterday; two are editing the same file; a third finished an hour ago and is still open, holding a window. Nothing in any one transcript says so. LampMaster, the reviewer, reads them together and says it, in at most three suggestions.

Its place is a star at the end of the bar above the rows: dim with nothing to say, lit with a number when it has suggestions. A click opens its view beside the list. In compact mode, which has no bar, it keeps a line of its own.

Off until you say so

Let LampMaster suggest, in Settings › LampMaster, and the sentence next to it, which is there before you press it rather than after: a round reads this Mac's Claude Code sessions — the last prompts and answers, the files written, what failed and what was saved — and asks Claude for its suggestions with your own Claude Code sign-in. That sends pieces of your conversations to Anthropic and uses your plan: about 7,000 tokens a round, never more than 200,000 a day. Nothing goes anywhere until the switch is on.

The round runs claude itself, with no tools, no hooks and no session left behind: it cannot do anything, and it does not show up as a session of its own.

When it looks

Once an hour, or every 30, 90 or 120 minutes if you choose. A round whose sessions say nothing new since the last one is skipped, for free.

At once, when a session starts repeating a failure or stops moving. Those are the two moments when an hour is too long: a session failing the same way three times is spending your time and your usage now, and the session that already fixed that error is worth knowing about now. These quick rounds come ten minutes apart at the least, six a day at most, inside the same daily ceiling, and they run Sonnet whatever the hourly round uses: measured, Haiku took up to a minute to answer the same question.

A suggestion

Each suggestion says what LampMaster saw and quotes the line it saw it in, under Evidence. A suggestion whose quote is not really in your sessions is thrown away before you see it.

Under it, the one action it proposes — Open, Copy question and open, End session…, Remove row — and three answers for when it is wrong or not wanted: Ignore, Don't suggest this kind again, Wrong: this is not true. Nothing is done without your click.

Talking to LampMaster

In the Hub, LampMaster's row has Talk to LampMaster. It starts LampMaster as a Claude Code session of its own, in tmux, in its own folder (~/.lampboard/lampmaster), and shows its terminal there: you talk to it as to any session. Cards beside it shows its hourly suggestions.

The first time, Claude Code asks whether to trust LampMaster's folder, with the arrow on «No, exit»: press ↓, then Enter, for Yes, I trust this folder. The header reminds you until you have.

It reads your sessions on its own: which ones there are, where they run, what they last said. It also searches your past conversations, on this Mac and on your other machines: ask where did we talk about the billing rewrite? and it answers with the folder and the machine. When you ask, it acts on them:

• writes a message into one, marked as coming from LampMaster;
• stops one that is working;
• starts one in a project, or takes up a past conversation: in tmux, or in the Hub ending when closed, and in the permission mode you name (open it in tmux with bypass);
• opens one in the Hub.

Claude Code asks you before each of these. LampMaster itself always starts in the mode that asks, whatever Settings choose for other sessions. It writes only into a session in tmux that is at rest with an empty prompt: if something is typed there, it says so and leaves it alone. A session in VS Code or in the Claude app is only read.

To start over, use the ↺ button in its header or New conversation with LampMaster… in its row's menu: the running conversation ends, and its cards stay.

LampMaster is Claude Code with your own setup, so your MCP servers and plugins are there too. To give it your own instructions, write them in CLAUDE.local.md in its folder; LampBoard never touches that file.

Asking it from the panel

? and a question in the bar, or the box on Today in LampMaster's own view, asks it about all your sessions at once: "which conversation renamed slots?". The box keeps a conversation, so a follow-up is read against the last answers, until New conversation. Today lists who asked what today, sessions and you. It runs under the same switch, hourly limits and daily ceiling as everything else LampMaster does.

Asking it from a session

A second switch, Let sessions ask LampMaster, adds a lampmaster server to Claude Code for all your projects (lampboard mcp install does the same from a terminal). A session's model can then ask who else is on these files, who worked on a topic, who hit the same error — answered from this Mac, at no cost — and put a question to LampMaster, which runs a model as a round does, at most twenty times an hour.

With the helper there is also a command you type yourself:

/lampmaster who renamed the slots endpoint?

The answer is printed for you and not handed to the session's model. It is made of other sessions' work, and whether this one should act on it is your call.