neuron-explorer
Steering-first neuron explorer for Qwen3.5-4B: push every MLP neuron, keep every rollout, browse the results
Agents can handle it. Your memory cannot.
Translation pending
Developer toolsGo · ShellGitHub @cybagardOnlineOwner unconfirmed
Have you tried it? One tap is enough. No sign-in needed.
Owners of public repositories under a personal GitHub account can sign in to verify ownership and manage the introduction themselves. No administrator approval is needed.
Sign in, generate a verification file, and commit it to this repository’s default branch within 30 minutes. Files on other branches or forks do not count. Then check the file below to manage the project without administrator approval. Keep the file to retain your access.
If needed, you will go to sign-in. After signing in, return here and press your chosen verification button again.
Run /nomorevibe verify in your project folder to verify ownership and manage the introduction yourself.
Verify in one minuteAsk about other verification options
Memory admission control for parallel coding agents on one Mac. See what each agent costs, and gate it before it spawn more.
Taken from the repository README
Loading the full README. The saved excerpt is shown below.
Admission control for a fleet of parallel coding agents on one Mac.
Status: v0.1.0 is a pre-release. All v0.* releases are pre-releases.
headroom shows what each coding agent costs in Docker and Tart, and what LM Studio and Ollama reserve on the host. It shows one row for each Orca worktree in which agents work. headroom needs Orca to find each worktree.Read the full README ↗Admission control for a fleet of parallel coding agents on one Mac.
Status: v0.1.0 is a pre-release. All v0.* releases are pre-releases.
headroom shows what each coding agent costs in Docker and Tart, and what LM Studio and Ollama reserve on the host. It shows one row for each Orca worktree in which agents work. headroom needs Orca to find each worktree.
headroom also gates the containers and VMs that an agent in an Orca worktree starts through docker, podman or tart. Before a call starts something, headroom checks that the call fits in the memory budget. If it does not fit, headroom stops the call and tells the agent what it can reuse or stop.
headroom runs on macOS on Apple silicon. Install it with Homebrew:
brew install cybagard/tap/headroom
brew services start headroom
The service starts the daemon now and at login, and puts the shims in ~/.config/headroom/shims. In Orca, open Settings → Agents and set the command of each agent to headroom run -- <agent>, for example:
headroom run -- claude
If Orca does not find headroom, use the full path, /opt/homebrew/bin/headroom run -- <agent>.
Do not also run headroom install. To upgrade, run brew upgrade cybagard/tap/headroom, then brew services restart headroom. To uninstall, run brew services stop headroom, then brew uninstall cybagard/tap/headroom, then rm -rf ~/.config/headroom/shims.
If you do not use Homebrew, install from the release tarball:
curl -fLO https://github.com/cybagard/cyba-headroom/releases/download/vX.Y.Z/headroom-vX.Y.Z-darwin-arm64.tar.gz
curl -fLO https://github.com/cybagard/cyba-headroom/releases/download/vX.Y.Z/SHA256SUMS
shasum -a 256 -c SHA256SUMS &&
tar -xzf headroom-vX.Y.Z-darwin-arm64.tar.gz &&
./headroom install
install copies the binary to ~/.local/bin/headroom and starts the daemon as a LaunchAgent. Put ~/.local/bin on your PATH. For zsh, the default shell on macOS, run this command and then open a new terminal:
echo 'export PATH="$HOME/.local/bin:$PATH"' >> ~/.zprofile
To upgrade, run install again. headroom uninstall removes the binary, the LaunchAgent and the shims. It keeps the config, the samples and the logs.
headroom # the view, printed once
headroom --watch # redraws in place; Ctrl-C to quit
headroom --all # also worktrees with no agent and nothing running
headroom status --json # the full snapshot
headroom logs [-f] # the daemon log
The view shows the headroom figure (host memory minus reserved memory) and the memory pressure first, then one row for each worktree. It uses these marks:
⚑: the worktree holds containers or VMs while none of its agents works.⚠: the worktree holds a container or VM that did not start through the gate.?: unknown. It never means 0.brew services start headroom or headroom install puts the shims (docker, podman and tart) in ~/.config/headroom/shims. Launch each agent with the shims first on PATH. A call from outside an Orca worktree is not gated.
headroom run -- claude
In Orca, open Settings → Agents and set the command of each agent to headroom run -- <agent>. With the release tarball, use the line that install prints for each agent. An agent that already runs keeps its old PATH until you restart it.
Each gated call gets one of these verdicts:
BUDGET_WAIT=1, the call waits for room or for a macOS VM slot, when waiting can help. Waiting calls are served first come first. The default limit is 10 minutes.If the daemon is down, each call runs and shows a warning. A login shell (zsh -l) puts the real docker first on PATH, so its calls are not gated.
To check a shell, run headroom doctor in it. Each line tells you what to fix.
The config file is ~/.config/headroom/config.toml. headroom config prints each setting that is in effect. headroom suggest suggests values from the recorded samples.
min_headroom_gb, per_worktree_cap_gb and host_baseline_gb have the default 0 until the baseline run in #63 sets them. A value of 0 means no margin, no cap and no baseline. The example below uses example values, not defaults:
[policy]
min_headroom_gb = 6
per_worktree_cap_gb = 12
[budget]
host_baseline_gb = 10
To report a vulnerability, and to see what headroom contacts and stores, read SECURITY.md.
To build, test and release headroom, read CONTRIBUTING.md.