neuron-explorer
Steering-first neuron explorer for Qwen3.5-4B: push every MLP neuron, keep every rollout, browse the results
Clawdline shows every Claude and Codex Session already running on your Macs, moves work between them, and keeps multi-Session delivery understandable.
Developer toolsGo · TypeScriptGitHub @sainteyeOnlineOwner unconfirmed
Have you tried it? One tap is enough. No sign-in needed.
Watch and drive every Claude Code and Codex session on your Mac as one live tree — including the ones you started by hand and the child agents your sessions dispatch. See which is working, done, or waiting; answer any of them from your phone. No hooks, no MCP, no wrapper. iTerm2 or tmux.
Taken from the repository README
Loading the full README. The saved excerpt is shown below.
A local control plane for Claude Code and Codex. See every session, know which one needs you,
and let agents hand work to each other without losing the delivery record.
Clawdline is a Go daemon with a React console. It watches the Claude Code and Codex sessions you
already run in tmux (and iTerm2 on a Mac) — no wrapper, no hooks — and lets you read, answer, start
and stop them from a browser or your phone. Your agents and code stay on your machine; the optional
Clawdline Cloud connection is only an end-to-end encrypted path to it from another device.Read the full README ↗🌐 Clawdline website — See how Clawdline brings Claude Code and Codex Sessions together, download the app, and explore setup guides and security details.
With Clawdline Cloud, see Claude Code and Codex Sessions across your machines in one phone list, then open one to reply or leave a to-do.
clawdline playbook list|create|edit|delete. Playbook API and CLI guide · clawdline guide projectClawdline runs the daemon and console on your machine and works with Claude Code and Codex Sessions you already use. Cloud is optional; its relay carries encrypted data. How it works
Let Codex on your Mac work with Claude Code on Linux. After reciprocal pairing, Agents can discover remote Projects and Sessions, dispatch work to a chosen Project, message an existing Session, and resume when results return. You do not have to copy instructions and replies between machines.
Both machines must be online and authorize the connection. Work runs on the target machine; code and content keys stay on your hardware. Pairing is revocable, and task completion does not mean changes have landed. Available in dev builds today; the release installer does not yet include the new discovery and Session wake-up features. Usage and authority boundaries
For a paired phone, Clawdline first tries to open a direct WebRTC data channel to your Mac or Linux machine for live Terminal and Session reads. This removes the relay hop from those reads and can make the Terminal feel more responsive. Cloud still carries connection signalling and other commands; if ICE cannot connect directly, the end-to-end encrypted relay carries the reads instead.
The machine can turn direct connections off in Settings → Remote or with clawdline cloud direct off. An AWS Linux host can bind ICE to one UDP port; see the Cloud guide and the full Linux procedure. Fixed-port setup is currently in development builds.
Clawdline reads your Claude Code and Codex conversations, terminals and project files on your own machine. Local use needs no account, and Cloud stays off until you turn it on.
With Cloud on, content is encrypted on your machine before it leaves. Cloud relays ciphertext without the keys to decrypt it; only your machine and the browsers you pair can read it. Cloud still sees account, device and traffic metadata.
A paired browser can send instructions and use your terminal, so pair only devices you trust. Claude Code and Codex still send requests to their AI providers under those providers' policies.
How it works, with diagrams and source links · AI security review comparison
Apple Silicon · macOS 13+ · Install guide
For the command-line installer on macOS 13+ or Linux, install Claude Code or Codex, trusted Python 3, and OpenSSL 3 or newer. The macOS bundled LibreSSL is not sufficient; see verification prerequisites. Then run:
curl -fsSL https://clawdline.com/install.sh | sh
Before unpacking or executing downloaded code, the installer uses local OpenSSL to verify the manifest against public keys pinned in the reviewed script, then checks the archive against its signed size and SHA-256. Missing verification tools or failed checks stop the installation. You still need to trust the installer script and your local tools. The verified program then starts a per-user service and opens the console. Start a Session there or run claude or codex in tmux; the release includes tmux if needed. Install and first run · First Session
The short URL points to a reviewed verifier script and installs the latest stable release. The script revision and the installed release are separate; the signed release manifest names the program source revision. The entry point can change as reviewed installers are promoted. Review and pin an installation keeps the fixed-script, fixed-version alternative and explains the first-install trust boundary.
User guide · Agent guide · Build from source · Troubleshooting · Developer docs · Graphify experiment · UI motion catalog · Static HTML reports