junban 0.9.0

Added

• An agent that may be stuck turns orange. A command that never returns or a network call that hangs used to leave the tab on ●, looking like an agent still at work. After 15 minutes without a finished tool call, the ● turns orange and shows how long it has been silent (● 23m). The status line counts these agents, they come first among the working ones in the Alt+f list, and @junban-notify-cmd gets one message each time. The mark clears at the next finished tool call, or when the agent waits on you or finishes. A long build or test run gets it too, so look before you stop anything. Change the minutes or turn it off with Alt+, → Mark silent agents (@junban-quiet-minutes, 0 = off). Works with Claude Code, Codex CLI and Gemini CLI.

Fixed

• Alt+, no longer splits English choices with spaces into pieces. "every 30 min" showed up as three menu items.
• Two settings saved at the same moment both stick. A save that took more than 3 seconds could have its lock taken over, and one of the two choices was lost.

junban 0.8.4

Includes everything since 0.7.8 (0.8.0–0.8.3 were never released on their own).

0.8.4 — 2026-10-27

Fixed

• Restoring no longer starts every agent at once. Each Claude Code session, with its MCP servers, takes the better part of a gigabyte, and a dozen starting together can run a machine out of memory. Agents now start two seconds apart, at most six reopen on their own (the ones waiting on you first), and the rest stay in the menu.
• The restore message counts only the windows still left to reopen, and the menu no longer offers a window that was just reopened, so a session is never opened twice.
• The restore menu shows on a short terminal. A list taller than the screen used to draw nothing; Restore all now comes first and the list ends where the screen does.
• The restore message is no longer lost when tmux starts from a terminal that attaches a moment later.
• Window names with # come back unchanged, and a tmux server that gets the old pid after a container restart still counts as restarted.

0.8.3 — 2026-10-27

Security

• $OPENAI_API_KEY no longer goes to other servers unless you say so. With a …/v1 model URL and no @junban-namer-key, junban used to send that key to whatever server the URL named. Other servers now get a key only if you name the variable that holds it in @junban-namer-key. To keep sending your OpenAI key to another server, set @junban-namer-key to OPENAI_API_KEY. If that server needs a key, window names and recaps fall back to your prompt and the first line of the agent's reply until you do.

0.8.2 — 2026-10-27

Fixed

• The restore message no longer says "0 window(s)" or points at an empty menu. When nothing is left to restore by hand, it only says how many came back.

0.8.1 — 2026-10-27

Fixed

• Restoring no longer misses windows whose pane once ran another Claude Code session. That session's leftover record sometimes kept the window from being saved, or from being reopened after the restart.

0.8.0 — 2026-10-27

Added

• Windows come back after a restart. junban keeps a list of which window runs which Claude Code conversation. When tmux starts again, it reopens the ones worth reopening (waiting on you, working, finished and not yet looked at, or active in the last day; never ones marked z) in their old session, folder and name with claude --resume, and says how many. The rest are under Alt+, → Restore windows. @junban-restore off turns off the automatic reopening. Each tmux server keeps its own list.

junban 0.7.8

Fixed

• The "starting in a new worktree" notice is no longer hidden by the spinner. Both now share the status line while the agent starts.

junban 0.7.7

Fixed

• Alt+n's spinner can no longer land on Claude Code's "trust this folder?" prompt. It used to draw in the new pane, and a frame written just as Claude drew its prompt stayed on top of the options, so the window looked frozen. The spinner now shows on the status line and never writes into the agent's screen; it stops as soon as the agent draws anything.

junban 0.7.6

Fixed

• The stopped spinner no longer leaves "Starting claude…" above Claude Code's trust prompt. Its line is wiped when nothing of the agent's is on it.

junban 0.7.5

Fixed

• Alt+n's spinner no longer draws over Claude Code's "trust this folder?" prompt. The prompt comes before any hook and leaves the cursor on the top row, so the spinner kept going for a minute on top of it. It now stops as soon as anything else is on the screen.

junban 0.7.4

Fixed

• Alt+w asks properly with the guide rows off. With @junban-guide off the close prompt was empty.
• The installer no longer says open Claude Code sessions pick up junban by themselves. It now says to run /reload-plugins in them.
• junban's state files are written readable only by you, the version and update log included.

Changed

• The site, manual and READMEs were reviewed line by line against the code, in English and Japanese. Several descriptions were corrected: the Alt+a order, what needs Python 3 and fzf, when the VS Code window switch applies (VS Code connected remotely to Linux), what @junban-done-batch holds back, and what is logged.

junban 0.7.3

Changed

• An update says so once, where you will see it. "junban updated to X" now shows the first time the status line draws after a new version arrives, so an update that ran in the background or overnight is not missed. A first install says nothing.

junban 0.7.2

Changed

• The installed version shows in Alt+/ (next to the title) and in Alt+, (next to Update now). It used to be only in doctor.sh.

junban 0.7.1

Fixed

• Jumping to another project from VS Code no longer swaps this window's terminal. When no terminal showed that project (its window's terminal was closed), junban switched the terminal you were in, so one project's agent ended up under another project's window. It now opens that project's folder in VS Code, which brings its window forward if it is already open.