You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The daemon uses about a third less CPU on a home with thousands of sessions.
With 2,000 sessions and one of them working, it settles at about 1.7% of a core, inside its 2% budget, where it used 2.5–3%.
A session's reply still reaches the map within about 1.6 seconds, and a hook still changes its building at once.
Scripted runs are no longer drawn as buildings.
A session a program started, such as claude -p or the Agent SDK, used to stand as a building like one someone works in, so a machine that runs Claude from scripts filled with them.
They are off the map and out of the finder by default, and their tokens and spend still count in the power plant, the strip and the statistics.
The settings panel's scripted runs row, or scripted_runs = "shown", brings them back at once.
Fixed
The package builds for anyone who has changed a setting.
0.3.1 failed to build from source, the AUR package included, when the person building it had set district_type or any of several other keys in their own config or environment, because a test read them.
The tests now never read the builder's config, and every test run checks that against a config that changes every setting.
A statistics store the daemon cannot open no longer turns statistics off without a word.
The daemon logs why, naming the file, and botropolis doctor has a statistics row that warns with the reason.
The city shows a notice once per launch with what to do: update Botropolis for a store written by a newer release, or move a damaged one aside and restart the daemon.
A damaged store is refused and left exactly as it was, never repaired or reset.
The city behind a notice or a dimmed panel no longer reacts to the pointer.
Resting the pointer on a notice, the board, the settings or any other panel that dims the map used to raise the card of whatever stood behind it.
While the map is dimmed, nothing on it is hovered.
A session whose transcript Claude Code deleted leaves the map.
On a machine with a long history, every such session used to stay drawn, however old, and each could be a district of its own.
Its statistics are kept, so the power plant, the strip and the statistics panel read as before.
The settings panel's deleted transcripts row, or gone_sessions = true, brings them back at once.
Sessions started one after another no longer chain into groups of hundreds.
Starting within a minute of another session no longer joins it to a group on its own; it is suggested instead.
Timing still counts alongside other evidence, such as shared files or a branch, but it never links one session to the next down a stream of runs.
A group holds at most 40 sessions, and the daemon logs any it leaves out.
A ticket, team, branch or file shared by more than 40 sessions no longer groups any of them, and the daemon logs it; on a long history this also takes most of the work out of the first load.
New session now says perhaps rather than likely when its only reason is that you were in one of the group's sessions a minute ago.
A city with hundreds of districts opens and stays usable.
On a long history the map used to freeze, and quitting with q then y could fail while it was busy.
A city of 900 districts and 2,400 sessions now draws a frame in about 40 ms where it took 120, and in about 17 ms zoomed in, and lays itself out in under a second where it took 3.4 seconds.
The quit prompt now waits for your answer however busy the city is.
Sessions in temporary directories share one district, Temporary.
A session started under /tmp, /var/tmp, $TMPDIR or macOS's temporary folders used to be a district of its own, so a machine with a long history could fill with hundreds of one-building districts.
They now stand together in one district named Temporary.
A directory that only has tmp in its name, such as ~/tmp-project, is still its own district.