Repository navigation
CoreScope 0.10.0
Added
- Environment controllers (all optional in
.corescope.ymlunderenvironment:, older files
unchanged; see docs/ENVIRONMENT-CONTROLLER.md): each app of a
project's own controller is listed with the modes it can come up in (modes, one at a time), the
command that takes it down, containers to watch and its actions; mode commands do the whole
operation while CoreScope only watches (no second Docker operation, no race with
docker compose up -d, Stop runs only that app'sdown). Services checks follow the profiles,
app or status component that need them (profiles:,app:,component:), so an app that is
switched off raises no alert even when a proxy keeps its port open, with the new states
starting,externalandunknown(never up, never off). Astatuscommand's versioned JSON
is read every 30 s with a short timeout and reconciled with what CoreScope started (selection
changed in a terminal, CoreScope restarted, stale readings). One-off actions (setup, backup,
restore) have their own timeout, log, artifact, cancel and, for restores, a preview the user
confirms. MCP:environment_status,list_actions,run_action,cancel_action; each app mode
is a profileproject/app:modeforstart_profile/stop_profile.
Changed
- Profiles is grouped by project: each project's environment card shows a summary (apps
selected, expected components ready, problems) and one folded row per app, with its state in a
fixed column, a Start menu with its modes and Stop, and inside it the app's components and
actions by kind (kind:, otherwise guessed from the names); profile cards fold their commands and containers while stopped, show
the profile's own name with its state in a fixed column, and stopped profiles of a project fold
into one line when there are more than three. Components whose state the controller could not
read are summed up in one line and make the app unknown, not starting; when no container
engine answers at all (Docker switched off) the environment simply shows as off, without errors
or alerts. What is open is remembered. - Menu bar: every value has its own SF Symbol (cpu, memory chip, disk I/O arrows, network,
thermometer, internal drive for the SSD, terminal for Codex, sparkle for Claude) next to it,
also in the compact format, and the item's tooltip explains each one; the same icons are in
Settings. Settings › Menu bar is a single list (on/off, what it shows, order) instead of the
toggles followed by an unexplained copy of the same items. - Lower cost: environment status reads use
/bin/shwith the login environment read once
instead of an interactive login shell every 30 s, and slow to every 2 min with no window open;
the floating panel is released when turned off and the menu bar window stops rendering while
closed (both kept updating on every sample); freed memory is returned to macOS after the window
closes and every 5 min while closed.
Fixed
- An ejected volume leaves Storage at once instead of up to 30 s later.
- Language: System followed the language last chosen in CoreScope instead of macOS's.
Commits since v0.9.0
- feat: environment controllers, lighter Profiles and menu bar, lower cost (d1fcef8)
- chore(release): 0.10.0 (960bf1a)
- feat: environment apps with modes, menu bar icons, Docker off is not an error (117aa63)
Full diff: v0.9.0...v0.10.0
Install
- Download CoreScope-0.10.0-macos-universal.dmg below (universal: Apple Silicon and Intel, macOS 14+).
- Open the DMG and drag CoreScope to Applications.
- The app is open source and signed ad hoc, not notarized by Apple, so macOS blocks it the first time. Open it once, then go to System Settings → Privacy & Security and click Open Anyway. Alternatively, in Terminal:
xattr -dr com.apple.quarantine /Applications/CoreScope.app
The Intel slice is built and checked on every release but has not yet been run on an Intel Mac; reports are welcome.
Checksums (SHA-256)
f7200fed803d9da71454fbb8e56a23a9cadac40446c341368e44f2d837f70da4 CoreScope-0.10.0-macos-universal.dmg
63dc658d5ed919c4d4f5853beb46a11add30a9a82842a3ae1d9f92c16dd162a9 CoreScope-0.10.0-macos-universal.zip
Verify with shasum -a 256 -c SHA256SUMS.txt in the download folder.